Live on Creditcoin CC3 testnet
ProofSettle is a settlement rail for off-chain AI compute. A buyer pays on Ethereum and names the exact enclave build they will accept. A contract on Creditcoin releases that payment only if the payment really happened and the answer really came from the code they named. Two independent proofs, of two different kinds, checked together or not at all.
This page is the audit tool. It exists so that somebody who was not involved, the buyer's auditor, their regulator, a competitor, or you, can check any settlement afterwards without asking permission from anyone, including me. Nothing below is read from a server I control. It is read from Creditcoin and from Google, in your browser, while you watch.
01 / Check it
The fields are prefilled with a real settlement that happened on Creditcoin CC3 testnet. Change them and check a different one. There is no backend, no API key and no account: the page calls the public Creditcoin RPC and Google's published keys directly from your browser.
02 / What it proves
It happened on Ethereum, which Creditcoin cannot see. The Attestcoin Protocol proves it, and the settlement contract records the proof as spent so the same payment cannot be settled twice.
The registry binds an enclave build to the key it signs with. The contract enforces the build the buyer named, not a list of its own, so changing what the buyer asked for changes the settlement rule with no redeploy and no admin key.
A chain cannot check a hardware certificate; it would cost more gas than any settlement is worth. So this page fetches the enclave's attestation and Google's live signing keys and checks the signature here, then confirms the image inside it is the build bound on chain.
Accepted pays the provider, rejected returns the buyer's claim, partial splits it. Whatever the verdict, the parts equal the amount locked on Ethereum and nothing is created that was not paid for.
03 / Limits
The registry does not verify hardware attestation on chain, because no contract can afford to. It records the binding, a hash of the attestation and where to fetch it, and enforces the binding. The checking happens here, in your browser, where anyone can repeat it and disagree in public.
The rail is one-directional today. Attestcoin carries attested data into Creditcoin; carrying a settlement receipt back out needs writability, which is out of scope this season, so the buyer's refund is gated on elapsed time rather than on a receipt. That is the last trusted component and it is named rather than hidden.