ProofSettle

FOR JUDGES · SUPPORTING EVIDENCE

Use the product.
Then inspect the guarantees.

The primary demo is a new purchase in the buyer workspace. This page keeps the technical evidence in one place: a completed reference run, its private answer and a separate wrong-build refusal.

FOLLOW THE EVIDENCE

Reference run: five independent checks.

Did the buyer get the work they paid for? Follow one completed purchase, then inspect a separate wrong-build refusal.

What this button does

Your browser rereads the public payment and settlement records and compares them. It checks the evidence for an already completed run; it does not run the AI again, connect a wallet or spend money.

Testnet demonstration · one completed purchase + one refusal case

Loading the published example…

INDEPENDENT READBACK

Checking the published evidence

The page fetches the manifest, then verifies transaction receipts and settlement state against the public RPCs.

Green means this check matched the public records just read. They establish the delivery and settlement of this reference purchase.Go deeper: verify the enclave and settlement →
THE FIRST USE CASE

A credit decision.
Without surrendering
the applicant’s record.

A small lender wants a model’s answer, but cannot hand borrower data to an unknown compute provider. ProofSettle seals the record to a measured enclave and makes the provider’s payment conditional on verifiable service completion.

Try the buyer workflow →
PUBLIC SYNTHETIC SAMPLE MODEL DEMONSTRATOR
History6 months
Regular inflows14 / month
Prior loansNo history
The provider sees ciphertext.

The measured model sees the record.
The buyer receives the private answer.

A deterministic logistic model illustrates the workflow. Synthetic inputs keep the example open to inspection. A computed decline still pays the provider.

PRECISE ABOUT TRUST

Know what each proof guarantees.

01

Attestcoin proves the source event.

The native Creditcoin verifier checks inclusion and continuity. The contract pins the Sepolia escrow, checks receipt success and consumes each proof once.

02

The enclave signs the exact work.

The signature binds the job, chain, contract, request, service outcome, result hash and encrypted delivery. An alternate model, input or return key does not match.

03

Enrollment has a trust boundary.

A registrar checks Google’s attestation and binds the measured image to its signing key. The browser checks the published evidence. Google, hardware and the registrar remain trusted.

04

The return leg is explicit.

Creditcoin authorizes the split. A fixed trusted relayer releases original ETH on Sepolia. This is a testnet return path, not production Attestcoin writability.

Public metadata includes addresses, payment amounts, commitments and ciphertext. Plaintext inputs and accepted answers stay encrypted. Enrollment evidence is historical. The synthetic model is not validated for lending decisions.

FOR OTHER ATTESTCOIN BUILDERS

Useful beyond this one application.

Proof consumption

AttestcoinProven verifies once and fails on false. The settlement contract demonstrates receipt and emitter checks, with tests and mutations.

Raw proofs on public RPCs

PatientBlockProvider works without eth_getBlockReceipts. A live comparison checks raw and hosted proof bytes.

Payloads inside transactions

The calldata rider carries sealed or plain payloads alongside ordinary Solidity arguments, ready for an application to bind to its proof.

OPEN SOURCE · TESTNET

Inspect it. Break a guarantee.
Watch the test fail.

65 contract tests. 15 deliberately broken guarantees caught. Real enclave and browser integration checks.