ProofSettle

Live on Creditcoin CC3 testnet

Independently verify
a Creditcoin settlement.

Check who signed the delivery, whether their build matches the buyer’s requirement, and whether the recorded payment split adds up. This is the technical detail behind the five-check walkthrough.

Start with the buyer’s story. Follow the real purchase or open its example answer. Use the checks below when you want to inspect the underlying evidence.

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. The site supplies the deployment addresses and published enrollment token; this browser checks them against Creditcoin and Google’s signing keys. These are read-only checks, with no wallet or payment.

01 / Check it

Check a settlement

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

    What those checks mean

    The payment really happened

    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 right code really ran

    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.

    Google agrees which code that was

    This prototype enrolls hardware evidence through a trusted registrar. 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.

    The money adds up

    Accepted authorizes provider payment, rejected authorizes a buyer refund, and partial splits it. The parts equal the amount locked on Sepolia. A fixed trusted return relayer separately releases the original ETH.

    03 / Limits

    What this does not do

    The registry does not verify hardware attestation on chain in this prototype. 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.

    A fixed trusted return relayer releases the original ETH on Sepolia after reading the Creditcoin split. This is not production Attestcoin writability. The source timeout is 30 days; finalized payments cannot also be refunded. Google, the confidential hardware and the enrollment registrar remain trust assumptions.