LIVEUTC GOLD · XAU/USD POLYGON BLOCK AI ATTESTATIONS PROOFS ANCHORED recompute anything · no verification, no trust
AI & agents · Kommit · proof of reasoning

The reasoning
attests itself.

AI is starting to act on the physical world — pricing carbon, grading gold, moving capital — and no one is held to what it claims. VPAY makes an AI verdict accountable: the model commits its output before the result is known, posts a slashable bond, and anyone can challenge it and recompute. Not a promise the model is right — a stake that it can be checked.

Adwene di adanseɛ — the mind bears witness.

KOMMIT · commit sealed before outcome
modelWeights0x7ea3…8e92
contextmarket state @ block
seedCommit0x4f1c…a930
outputverdict hash · pre-result
bondstaked · slashable
● committed · challengeable · recomputable
01 — the problem

Autonomous AI, acting on the world,
accountable to no one.

The hard problem isn't whether a model is correct — it's that when an agent makes a claim about a real asset, there is no record of who claimed what, no stake behind it, and no way for an outsider to challenge it. Accountability, not correctness, is the missing layer.

Who said it?

No authorship

An agent issues a verdict and the trail vanishes. Which model, which inputs, which moment — unrecorded.

Authorship ≠ truth — and both are missing
No skin

No stake

A wrong claim costs the model nothing. Without a bond, there is nothing to lose and nothing to slash.

Accountability needs a price
Trust me

No challenge

Outputs arrive as "trust me." No outsider can independently replay and dispute the claim.

Closed verdicts can't be audited
02 — proof of reasoning

Commit first. Reveal after. Recompute always.

Before it sees the outcome, the model seals a commitment: which weights, which context, which seed, which output. It posts a bond. The window opens for anyone to challenge — and the seed reveal lets them replay it independently.

V·PASS
VPAY Proof Passport · Kommit · reasoning commit
VPP
POLYGON · 137
Model weights
0x7ea3…8e92 · hermes-v2
Context
market state + signals @ block
Seed commit
0x4f1c…a930 · revealed after window
Output · bond
verdict hash · staked, slashable
Committed hashcomputing…
Recomputed here— press verify —
committed · challengeable · recomputable
P<VPAYKOMMIT<HERMES<V2<ORCHESTRATOR<<<<<<
7EA38E92<4F1CA930<BONDED<CHALLENGEABLE<<<<4

Illustrative of the live KommitBridge tuple. The contract is deployed and source-verified on Polygon Mainnet.

03 — how it works

From a model's claim to a stake anyone can test.

Four moves. The commit and the bond are live on Polygon today — the same registry the physical proofs anchor to.

COMMIT

Seal before outcome

The model hashes its weights, context, seed and output and commits the tuple on-chain — before the result is known.

BOND

Post a stake

A slashable bond is posted behind the claim. Being wrong, once challenged, has a price.

CHALLENGE

Open the window

Anyone can post a counter-bond and dispute the claim during the challenge window.

REVEAL

Replay & resolve

The seed is revealed; the output is independently recomputed. The honest side keeps the bond.

04 — where we stand · no overclaim

The contract is live.
Routine attestation is next.

Stated plainly: Kommit (KommitBridge, "Proof of Reasoning") is deployed and source-verified on Polygon Mainnet, and a VPAY agent is registered on Fetch.ai's Agentverse. It proves authorship and accountability — that a given model produced a given output under a given context and seed, challengeable by anyone — not that the output is correct. Routine, high-volume live attestation by our own engines is still being switched on. Pre-revenue; no live commercial pilots claimed. See KommitBridge on Polygonscan ↗
On the $SOV token: proving a claim is accountability, not backing. An AI verdict is an assertion — you cannot honestly mint a value-backed token against an assertion. So Kommit never mints $SOV. Only physical gold, as real hard-asset backing, does. AI accountability is a service the platform offers, not collateral for the token.
AI METRICS · ON-CHAIN SNAPSHOT ANCHOR

The AI metrics we publish are not "trust us" numbers. Each snapshot is hashed into a Merkle root and anchored to the public AnchorRegistry on Polygon — so anyone can recompute the hash and confirm the published figures are the anchored figures.

snapshot
merkle root
statuschecking…
05 — work with us

Builders of agents that act on real assets —
let's make them accountable.

If your AI makes claims that money or lives depend on, the commit → bond → challenge → recompute layer is built and live. Integrate it, or pressure-test it.

Start a conversation →