v0.1 — verification as process

Decentralized verification for submissions.

Meritum is a verification layer that helps communities evaluate submissions against explicit standards — transparently, repeatably, and without relying on blind trust.

No hype. No shortcuts. Process-first design Built for accountability

Explicit standards

Every evaluation references a public standard — no hidden criteria or reputation-only decisions.

Independent review

Validators review without coordination first, then outcomes surface agreement and disagreement.

Transparent outcomes

Results show the reasoning behind decisions. Disagreement is informative, not failure.

How it works

A simple flow: submissions are evaluated against standards by independent validators, producing transparent outcomes.

1

Submission

Work or claims are submitted for evaluation. Submissions become immutable for the review window.

2

Standard

Each submission is evaluated against an explicit standard — clear criteria that can be applied repeatedly.

3

Validation

Validators review independently and provide structured reasoning against each criterion.

4

Outcome

Outcomes show whether standards were met, where reviewers agree, and where ambiguity remains.

Governance

Meritum prioritizes legitimacy over plutocracy. Voting is designed to resist both whales and sybil attacks.

1 valid wallet = 1 vote

Voting power is capped at one vote per eligible wallet, regardless of token balance.

Eligibility requirements

Eligibility can require a minimum balance and a holding period (e.g., held ≥ N tokens for ≥ T days).

Domain-specific control

Standards governance is separated from operational decisions. Outcomes remain validator-driven.

Governance is process, not capital.

Meritum’s goal is to build durable standards—where participation requires commitment, not wealth.

Read governance model

Submissions

A public surface for verifiable work. Submissions are evaluated against explicit standards and published with outcomes.

Submission registry

Each submission has a stable ID, an immutable review window, and linked evaluations.

Standards attached

Outcomes reference the standard used so judgments are legible and comparable over time.

Outcome transparency

Evaluations are published after closure to preserve independence and reduce bias.

Bounties

Requested work with verification built in. Rewards are released only when the submission meets the bounty criteria.

Request

Communities post a bounty with explicit criteria and a defined review window.

Submit

Contributors submit work against the bounty criteria. No guessing what “good” means.

Verify & release

Validators evaluate. If the standard is met, rewards are released; otherwise feedback is recorded.

Docs

Foundational docs designed to be calm, clear, and versioned. No promises. No hype.

Meritum Protocol Whitepaper (v0.1)

Read the full thesis, system model, validator accountability design, governance approach, and roadmap phases.

Download PDF Pilot overview

Get started

Meritum begins with careful pilots. Start small, publish outcomes, refine standards.

Run a pilot

Create a standard, accept 5–10 submissions, recruit 3–5 validators, publish outcomes. Learn fast.

Become a validator

Validators are accountable through visibility and exclusion first, then economic bonding in later phases.

Contribute

Help refine standards, propose pilot domains, and improve the clarity of outcomes and reporting.