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?

Model Versatility

PreviousData DiversityNextConfigurable Reporting

Last updated 3 years ago

Was this helpful?

All reports are generated by running data from a (DP) through a model put together by a (MP).

The parameters that a model takes can be defined and configured depending on the use case. So each application can have their customized model for reputation assessment for the addresses and DIDs in their ecosystem.

MPs may also choose to make their models public, which makes them available for use publicly and accessible via Orange. They can be integrated and used by any application or system. Thus, a model constructed and used by one application can still be used by other applications.

Useful reputation models have the potential to set the foundation for reputation, since they are tools for value discovery in nascent Web3 ecosystems.

Data Provider
Model Provider