Reputable Network

• Name: Reputable Network
• URL: https://github.com/reputable-lab
• Category: reputation-model middleware / builder-reputation infrastructure / onchain scoring marketplace
• Summary: Reputable Network turns reputation models into tokenized onchain scoring products. That is the interesting part. Model design, attestation inputs, score computation, and model ownership are split out instead of being buried inside one ranking API. The rest still reads early.
• What it does:
  • Lets protocols create and deploy custom reputation models tailored to their own communities or applications
  • Uses hybrid inputs from onchain and offchain sources, with surfaced contract materials emphasizing Sign Protocol attestations as a verification input
  • Computes reputation scores through smart-contract logic rather than only opaque backend scoring
  • Represents each deployed reputation model as an ERC-721 token, making the model itself portable and ownable
  • Positions decentralized nodes as part of the data-validation and computation layer and shares protocol economics with them
  • Envisions a hub where models can be browsed, reused, and monetized rather than keeping scoring logic locked inside one product
  • Markets the system toward use cases such as grant screening, DAO governance, DeFi user segmentation, and other applications that want customizable reputation thresholds
• Key claims:
  • The protocol guide frames Reputable as infrastructure for aggregating, validating, and attesting reputation data so protocols can build custom onchain models instead of relying on one house score.
  • The smart-contract README makes the mechanism explicit: custom models are ERC-721 assets, attestations are verified onchain, and score computation happens in contract logic against model parameters.
  • The Medium post adds the actual business angle: deployment fees, labeling fees, computation-fee revenue sharing, and a market where model creators can sell or rent scoring logic.
  • Reputable is useful because it externalizes much of its trust stack. Authentication, attestations, metadata, indexing, and messaging are delegated to adjacent systems rather than hidden inside one vendor.
  • The surfaced evidence still points to early-stage builder infrastructure rather than mature production decentralization, especially with deployment references anchored to Unichain Sepolia.
• Whitepaper: No canonical standalone whitepaper surfaced in this pass. The strongest primary materials were the official GitHub organization profile, the smart-contract repository README, and the project’s official Medium post; see ../whitepapers/reputable-network-primary-sources-2026-05-11.md.
• Sources:
  • https://github.com/reputable-lab
  • https://raw.githubusercontent.com/reputable-lab/.github/main/profile/README.md
  • https://raw.githubusercontent.com/reputable-lab/reputableHub-contracts/main/README.md
  • https://medium.com/@Reputable/tokenized-reputation-building-a-web3-economy-with-custom-on-chain-models-b4f069cd12f6

Internal linkages

• Best comparison points: openrank, orange-protocol, and talent-protocol.
• Use Reputable when the question is who owns the scoring model and who gets paid for it, not who merely publishes a leaderboard.

Control surface

• Power sits in model authoring, attestation-source selection, verifier logic, hub distribution, and ERC-721 ownership of the scoring model itself.

• Read it as an onchain model-market experiment, not as a canonical reputation anchor.

• Last reviewed: 2026-06-04 UTC