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
  • OScore Model
  • Data Synchronization

Was this helpful?

  1. Case Studies

OScore

PreviousClaim Orange NFTsNextReputation NFT Based Voting Mechanism

Last updated 3 years ago

Was this helpful?

OScore is an on-chain credit score for programmable creditworthiness which is designed based on the Orange protocol. Its workflow illustrates how an MP and a DP work together in the Orange system.

OScore Model

OScore can represent one's credit standing in DeFi systems. It is calculated using many different pieces of transaction data, including:

  • Payment history

  • Liquidation history

  • Amounts owed and repaid

  • Credit mix

  • Length of credit history

It implements a customized model and quantification of on-chain behavior and interactions with existing DeFi protocols using Orange. This ensures the scoring methodology remains empirically sound and statistically valid.

Data Synchronization

Consider the following diagram illustrating OScore's transaction data synchronization flow from Ethereum, which is the DP in this context.

Geth Node

  • An Ethereum sync node

ETH Sync Service

  • Synchronization service that listens and monitors transactions via the sync node

  • Stores the relevant transaction data in a database

  • Stores block data for contract executor to fetch

Contract Executor

  • Listens to contract events via the sync node

  • Logs relevant event data in a database

Database

  • Stores transaction and event data

This data is stored in the database and fetched via an interface by the Orange system when the OScore model is invoked. Applications send invocation requests using an SDK. You can refer to the .

example here