ReaperNet
CONSENSUS

Built for many producers. One final answer.

DAG-Flow is how ReaperNet agrees on who paid whom. Blocks form a web (a DAG) instead of a single line, so many producers can work side by side — today one node produces blocks; a multi-producer DAG is on the roadmap. Once its block is confirmed in the DAG and a quorum of operators signs it with post-quantum keys, a payment is final — it can't be reversed.

BLOCK DAG · SIMPLIFIED
■ just produced■ confirming (gaining weight)■ final
~3,600 TPS
measured · one node, signatures on
2/3+
of node operators sign = final
ML-DSA-65
post-quantum signatures (FIPS 204)
5k → 100k+ TPS
roadmap target — not a measurement
HOW A PAYMENT BECOMES FINAL

Four steps. Every payment, every time.

  1. 01 · SIGN
    On your device

    The payment is signed with your ML-DSA-65 key on your phone. Nobody else can sign for you.

  2. 02 · INCLUDE
    Into a block

    A producer puts it in a block. Each block points to earlier blocks and commits to the state root before it.

  3. 03 · CONFIRM
    DAG confirmation

    New blocks build on top of it until its weight in the DAG confirms it - rewriting it would then mean rewriting everything after it.

  4. 04 · FINAL
    Operator quorum

    A quorum of operators attests the block with post-quantum signatures. Now it is final.

WHY A DAG

Built to run side by side. Today: one producer.

Multi-producer (roadmap)

In a single chain, only one block can be next. In a DAG, several producers can add blocks at the same time and the web ties them together. Today one node produces blocks; a multi-producer DAG is on the roadmap.

State-root commitment

Every block commits to the state root before it, so any node can check that balances add up — not just trust the producer.

Post-quantum from day one

Accounts, blocks and operator attestations all use ML-DSA-65, the NIST FIPS 204 standard.

Finality you can name

Apps can show “final” with confidence: final once more than two-thirds of the node operators sign, not a probability.

PRODUCERS & OPERATORS

Who keeps it honest.

Full nodes in the operator set attest blocks; today one of them produces blocks (multi-producer is on the roadmap). An operator who signs two conflicting blocks can be reported with double-sign evidence and slashed. Operator staking is built (stake RPN to join the operator set, unbonding period, slashing for double-signing) but not switched on for the public testnet yet - its operators are set at launch. No yield is promised.

Reading from the node…

  • Operator set — the full nodes that attest finality
  • Candidates — staked nodes waiting to join
  • Slashed / unbonding — removed for misbehaving, or leaving

DAG-Flow consensus with a permissioned quorum of node operators who sign every block with post-quantum ML-DSA-65 keys. Today one node produces blocks; a multi-producer DAG is on the roadmap.

MEASURED VS TARGET
Measured today~3,600 TPS
one node, signatures on · 71 % of the next target
Next target (multi-threaded ingress (Stage 1))5,000+ TPS per node
Long-term target (native hot path + parallel execution (Stage 2))100,000+ TPS

Targets are targets. A payment is final when its block is confirmed in the DAG and signed by more than two-thirds of the node operators, each with a post-quantum (ML-DSA-65) key. Until then it is shown as pending, never as final. Finality time will be published once it is measured on the public testnet.

Measured 2026-10-01: GitHub Codespace (16 cores), one node, ML-DSA-65 signatures and persistence ON, pre-signed transfers via /tx/batch. Benchmark: scripts/bench/node-tps-bench.ts (best runs 3,594 and 3,568 TPS; the lower is published).

Keep exploring

Final means final.

Create your BlockiD
Get the app