Relics proof network
The subnet
before the subnet.
Three miners. One dishonest answer. A 2-of-3 threshold.
This deterministic test shows how independent miners can reconstruct the Relics index while validators challenge exact chain state. The dapp accepts only matching proof responses.
No subnet is registered, no miners are live, no emissions are active, and this page performs no chain or wallet transaction.
Validator scorecard
One bad answer cannot become history.
The validator compares the checkpoint, finalized block, requested dataset hash, response freshness, and identity. Correctness is mandatory; latency only affects the remaining score.
Indexer mineragrees
atlas
- Score
- 98.90%
- Latency
- 110 ms
- Proof
- Exact
Indexer mineragrees
scarab
- Score
- 98.20%
- Latency
- 180 ms
- Proof
- Exact
Indexer minerrejected
obelisk
- Score
- 0.00%
- Latency
- 90 ms
- Proof
- dataset
Accepted checkpoint root
sha256:c917593f1a0c5f...61aa2e44ced0Finalized fixture block#1000
Agreed minersatlas + scarab
Dissent rejectedobelisk
Miners replay
Each indexer derives Relics from finalized Subtensor history and commits every canonical dataset to one root.
Validators challenge
A checkpoint, dataset, and unpredictable nonce bind each response so stale or substituted answers fail.
The dapp requires quorum
The gateway serves the answer only when the configured threshold agrees. Otherwise it returns no consensus.