Skip to main content
CC3 Testnetreading head…
Attestations

Verification trace

The Attestcoin precompile proves a transaction was included in a block on the confirmed source chain. It does not prove the transaction succeeded, and it does not prove which contract emitted the log inside it. This page shows what the registry asked next.

Select a proven fact

Paste an address to trace what was proven about it.

Proven facts are public. Anybody can read any address.

Nothing to hand?0x4c8e…88F9
Proof integritycritical difference

A valid proof can still be a lie

Deploy a contract emitting a byte-identical Repay naming yourself. The transaction succeeds, topic0 matches exactly, and the Merkle and continuity proofs are genuine. A consumer matching on the event signature alone credits a fabricated repayment — and nothing reverts, warns, or fails a test.

Pinned emitter

Aave V3 Pool

accepted
Lookalike emitter

identical topic0

rejected

Performed live on 2026-09-05. A lookalike contract on Sepolia emitted a byte-identicalRepay, the real Attestcoin prover proved it, and the identical bytes were accepted by a naive consumer and reverted by this registry. Not a simulation.

Guards

The three checks an integration must not skip

S1 — receipt status must be 1. A reverted transaction is still in its block and still proves.
S2 — emitter must equal the pinned source. topic0 is not chain-specific and not authorship.
S3 — replay keyed per log, including factType. One transaction can carry several qualifying logs.
Subject is read from the proven log, never from msg.sender. Submitting gains the submitter nothing.

Each is a revert, not a warning. A fact in the registry is itself the evidence that all four passed — which is why this page has no failure state to render.