Ledger · NoetenArchiveLedger
Prove the archive. Hashes only, never logs.
A team registers the keys its machines use, then anchors each finished run. Later, anyone holding one file and its archive can prove that pair was part of the run. The contract holds no funds, has no owner and accepts no ether. It records what a member said; it cannot see whether you still keep the archive.
Not deployed yet.
NoetenArchiveLedger is written and tested (unit, fuzz, invariant and Robinhood Chain fork tests) but has no address on Robinhood Chain yet. The forms below show what each transaction does; they unlock once the contract is deployed. Checking a manifest and proving a file against it already work, in this tab.
Create a team.
Your wallet becomes the team owner. The name is public; keep it generic (1–48 plain characters).
Register a worker key.
The owner adds the address a machine may anchor with. A worker can later remove itself.
Anchor a run.
A team member (the owner or an active worker) anchors one manifest. Only its sha256, the Merkle root, counts, sizes, the tool hash and the source block range go on chain.
Paid in ETH on Robinhood Chain by the sender, about 275,000 gas measured on a fork.
Prove one file.
Pick a file from the run's manifest. Its proof is computed here and checked against the manifest root, then against the run on chain.
Look up a team.
Retract a run.
The team owner or the run's poster marks a run as retracted (wrong data, lost archive). The record stays readable and the manifest cannot be anchored again.