Orange
  • Reputation in Web3
  • What Orange Does
  • Use Cases
  • Glossary
  • Characteristics
  • Data Diversity
  • Model Versatility
  • Configurable Reporting
  • Self-Sovereignty and Privacy
  • System Design
    • Architecture
    • Model Providers
    • Data Providers
  • Developers
    • Assess Reputation for Your dApp Users
    • How to Start
    • Become a Data Provider
    • Become a Model Provider
    • Issue Reputation NFTs
    • Get Campaign Info using API
  • User Guides
    • Reputation Studio Overview
    • Claim Orange NFTs
  • Case Studies
    • OScore
    • Reputation NFT Based Voting Mechanism
  • Future
    • Decentralized Collaboration Network
    • Secure Computing Paradigm
  • SUPPORT
    • FAQs
Powered by GitBook
On this page

Was this helpful?

  1. SUPPORT

FAQs

PreviousSecure Computing Paradigm

Last updated 3 years ago

Was this helpful?

What role would I play in the Orange network?

Every role contributes to further development of Web3 interoperability in their own way.

Model Providers are generally platforms that have been working on reputation assessment within their systems. If that describes your system, you can join the Orange ecosystem and make your models accessible to others.

Data Providers could be systems with data that has utility outside its native environment. Generating datasets and making them accessible via an interface to be used as input for modles is a great way to leverage the inherent cross-chain benefits of composability that blockchain brings.

dApps are the primary players who use the public modles and datasets to generate reputation for their users. If you're working on a dApp and want to implement a decentralized reputation mechanism, you can go ahead and integrate Orange to your system using .

this SDK here