Documentation
Essential information about Reward and Reward Core.
No scoring. No ranking. No interpretation.
Start here
Reward is a protocol layer that captures contribution as structured, verifiable records. Reward Core is the neutral, archival explorer that exposes this protocol truth.
What is Reward?
Reward is a protocol (the Merit Layer) that makes contribution legible. It provides a neutral foundation where work is recorded as structured, addressable records without requiring evaluation or ranking.
What is Reward Core?
Reward Core is Layer 0: a neutral, archival explorer that exposes protocol truth without evaluation or interpretation. It shows what happened, when it happened, and who was involved.
The flow
Contributors submit work with proof links. Authorised verifiers review and record outcomes. All contributions become permanent protocol history.
Core concepts
Essential terms for understanding Reward.
Contribution Object
A structured record that captures essential facts about work: title, summary, proof links, contributor address, project ID, and verification status.
Each contribution object is permanent and addressable by its unique identifier.
Proof
Evidence links that demonstrate the work happened. Acceptable proofs include code commits, documentation, design files, research reports, or other verifiable artefacts.
Proofs make contribution verifiable rather than relying on claims alone.
Verifier
An authorised address that can review contributions and record verification outcomes. Projects define verifier allowlists.
Verifiers record factual outcomes, not value judgments.
Outcome
The verification result: Verified (work happened as described), Rejected (work did not happen or proof insufficient), or Pending (awaiting review).
All outcomes are preserved as protocol history, including rejected contributions.
Anchoring
The process of recording protocol state on-chain. Currently using a local simulator for development. Anchoring is coming next.
Contribution truth is captured immediately, regardless of anchoring mode.
Verification
What verification means and what it does not.
What verification means
- •Recording that work happened as described
- •Confirming proof links support the claim
- •Creating a factual record of contribution
What verification does not mean
- •Assessing quality, value, or impact
- •Ranking or comparing contributions
- •Implying trust, competence, or reliability
- •Making value judgments about the work
Verification answers "did this happen?" not "was this good?" It is a factual check, not an evaluation.
Anchoring modes
Current and future anchoring approaches.
Local Simulator
Reward Core operates with a local simulator for development and testing. Contribution records are created and verified locally, enabling rapid iteration and testing.
Base Chain Anchoring
Chain anchoring on Base enables permanent, on-chain verification of protocol state. Contribution records are anchored to Base (mainnet or Base Sepolia testnet) for immutability and public auditability.
The protocol layer captures contribution truth immediately, regardless of anchoring mode. Records are created, verified, and preserved as structured protocol objects.
Early access
Who Reward Core is for during the early access period.
Reward Core early access is for projects and organisations that want to:
- •Test contribution submission and verification workflows
- •Explore the protocol layer and neutral explorer interface
- •Provide feedback on the protocol and Core interface
- •Build systems on top of contribution truth
Early access participants help shape Reward Core's development. We are looking for projects that understand the value of neutral, archival contribution records.