reading claim 5 from the Sepolia-sourced registry…
Attestcoin proves an event happened. Utuh bonds that nothing was left out.
An inclusion proof vouches for what is there. It cannot speak about what is not, because whoever submits the proofs chooses which to submit — and every one of them verifies. Utuh lets a claimant bond a set of source-chain events as complete, and pays half the bond to anyone who proves one in-scope event it left out.
Economic, not cryptographic: a bond makes lying expensive, not impossible. Then it underwrites undercollateralized credit on the history nobody could refute. Live on Creditcoin CC3 Testnet.
Reading both registries for a claim still inside its window…
Two claims, each broken by one proof
Both were sealed, published, and refuted from a browser during their challenge window. The second is the sentence every on-chain credit system needs — this borrower has never been liquidated — asserted over 216,000 blocks of Ethereum mainnet, and false.
Claim 5 — sealed one event short
W/P S-5 Sepolia · SettlementLedger events · the completed loopThree payments were appended and proven. A fourth, in scope and in range, was not. The sweep found it, one proof broke the claim, and half the bond went to the refuter. Open claim 5
reading claim 20 from the mainnet-sourced registry…
How it works
The audit programme, in the protocol's own words. The order is the mechanism.
-
Assert and bond
A claimant opens a claim over a source-chain block range and one event scope, appends every member through the Block Prover, posts a bond, and seals. Every member is cryptographically proven on the way in; the bond stands behind the word every.
-
Trace
During the challenge window anyone sweeps the source chain across independent endpoints and checks each in-scope event against the claim on-chain. No account, no key, no permission. The console does it in your browser;
npx utuh-mcpdoes it for an agent. -
Exception, or agreed
One proof of one omitted event refutes the claim: half the bond to the refuter, the rest burned. A claim nobody could break is finalized, and a line of credit can be drawn against the history it proves — repayment history on Ethereum, credit in CTC on Creditcoin, only proof crossing.
Who signs the working paper
Three roles meet at the same console, and none of them is a consumer.
Claimants and borrowers
Prepared byOpen a claim over a block range, append proven events, post a bond, wait out the window, and draw a credit line against the history that survived. The whole underwriting runs from the console with your own wallet.
Watchers
Traced bySweep a source chain for an in-scope event a sealed claim left out, and refute it for half the bond. Adversarial, unpaid until you win, and the only reason the central claim holds. A watcher need not be a person.
npx -y utuh-mcp
MCP server · five tools · in the official registry
Lenders and integrators
Reviewed byRead a claim's standing before extending anything, or wire the registry into your own contract. The challenge window is your diligence window; half the bond is a rebate on work you had to do, not a wage.
Legend
Every mark on this page, defined once.
- Traced. The member was verified by the Block Prover on the way into the claim; the console links each one to its source block.
- Exception. An event in scope and in range that the claim does not contain — one proof of it is a refutation.
- Footed. A total under a double rule is summed across both registries as the page draws it, from the contracts themselves.
- W/P
- Working-paper reference. S for the Sepolia-sourced registry, M for the mainnet-sourced one, then the claim id. The console opens any of them.
Check it yourself
Every figure on this page is a read anyone can repeat, with no wallet and no key. Contracts verified on Blockscout and Sourcify. Nobody has audited them; this page audits claims. Testnet software — the contracts hold testnet CTC. No users, no TVL, no partners are claimed, because there are none to claim.
Verification programme
W/P J-1 each row is one fact and the place that proves it- Registry · Sepolia-sourced
- 0x2688…347b · Sourcify full match · holds claim 5 and every claim of the completed loop
- Credit · Sepolia-sourced
- 0x0177…24b6 · Sourcify full match · opens lines against finalized Sepolia claims
- Registry · mainnet-sourced
- 0x8FA0…5Fac · Sourcify full match · holds claim 20 and the claims about real Aave history
- Credit · mainnet-sourced
- 0x89FB…0C57 · Sourcify full match · opens lines against finalized mainnet claims
- Claim 5 refuted
- reading the registry…
- Claim 20 refuted
- reading the registry…
- Every member proof
- Creditcoin's verification dashboard lists each verification the Block Prover emitted, by source height
- Refutations so far
- reading both registries…
- Sweep as an agent
-
npx -y utuh-mcp - Re-measure every number
-
npm run judgere-reads every figure above from the chain, the explorer, npm and the MCP Registry with no key, after cloning and installing