Skip to main content

How it works

Reward is a protocol layer that captures contribution as structured, verifiable records. Here is how it works.

What is Reward (Merit Layer)

Reward is a protocol that makes contribution legible. It provides a neutral foundation where work is recorded as structured, addressable records without requiring evaluation or ranking.

The Merit Layer captures what happened: who did the work, what it was, when it was submitted, and how it was verified. This creates a permanent, searchable history of contribution that systems can reference without relying on proxies.

Contribution Object

Each contribution is a structured record with specific fields that capture the essential facts about the work.

Contribution Object Anatomy

Title
A concise description of the work
Summary
Plain-language description of what was done
Proof URIs
Links to evidence of the work (code, docs, designs, etc.)
Contributor Address
The on-chain address of the person who did the work
Project ID
The project or scope this contribution belongs to
Verification Status
Pending, Verified, or Rejected, recorded by authorised verifiers

These fields create a complete, addressable record of contribution. Each contribution object is permanent and can be referenced by its unique identifier.

Proofs

Contributors provide evidence links that demonstrate their work. These proofs make contribution verifiable.

Proof URIs are links to verifiable evidence of the work. Acceptable proofs include:

Code commits
GitHub, GitLab, or other version control links
Documentation
Written guides, specifications, or technical docs
Design files
Figma, Sketch, or other design tool links
Research or analysis
Reports, studies, or analytical documents

Verification

Verification records completion, not value. It answers 'did this happen?' not 'was this good?'

Authorised verifiers review contributions and record outcomes. Verification is a factual check: did the work happen as described? Does the proof support the claim?

Verified
The work happened as described and proof supports the claim
Rejected
The work did not happen as described or proof is insufficient
Pending
Awaiting verification review

Verification is not a quality assessment or value judgment. It is a factual record: did this contribution happen, or not? All outcomes, verified, rejected, and pending, are preserved as protocol history.

Permanence

Contribution history does not change. Once recorded, it becomes part of the permanent protocol record.

Once a contribution is submitted and locked, its core fields cannot be modified. Verification outcomes are permanent. Rejected contributions remain visible in history.

This permanence ensures that contribution history is reliable and auditable. Systems built on top of Reward can reference historical records with confidence that they will not change.

The Flow

From creation to permanent history: a simple four-step process.

1

Create

Contributor submits work with title, summary, and proof links

2

Prove

Evidence links are provided and verified

3

Verify

Authorised verifier records outcome

4

History

Contribution becomes permanent protocol record

Anchoring Modes

Reward Core currently uses a local simulator. Anchoring is coming next.

Current

Local Simulator

Reward Core operates with a local simulator for development and testing. Contribution records are created and verified locally.

Next

Base Chain Anchoring

Chain anchoring on Base will enable permanent, on-chain verification of protocol state. Contribution records will be anchored to Base for immutability.

The protocol layer captures contribution truth immediately, regardless of anchoring mode. Records are created, verified, and preserved as structured protocol objects.

Ready to explore?

See Reward Core in action or request early access for your project.