A capital mandate, executed by a machine within hard limits, closed by the same mandate — and then provably terminated: authority ended, approvals zero, the signing seed retired under a falsifiable attestation. Every claim on this page carries a block number and its verification status.
The mandate file's sha3-256 fingerprint IS its identity:
vlm-001:25a991ae424a5de974135e0f7e6f7034384418841bb22164bbb9aa1c47669ec1
| Mandate (pinned before execution) | Executed (proven after) | |
|---|---|---|
| Budget: EUR 20 per leg, EUR 40 total — a pinned cap, not a market value | Funded by the sponsor to the exact wei; settled fully into the position | ✓ |
| Max WETH: 0.009635489434685834 ETH (pinned in wei) | Used: 0.009635489434685834 ETH — equal to the cap, not a wei above it | ✓ |
| Max SUPRA: 119,060.897… SUPRA (pinned in wei) | Used: 114,556.177… SUPRA — under the cap | ✓ |
| Gas: fee cap pinned; reserve ceiling 0.02 ETH | Remainder after all three transactions: 0.004941 ETH ≤ reserve | ✓ |
| Allowed actions: 1×OPEN · ≤1×COLLECT (day 7+) · 1×CLOSE · APPROVAL-RESET — nothing else has an active policy pin | Executed: OPEN and RESET. COLLECT and CLOSE: unused — still null in the lifecycle ledger | ✓ |
| Term: until 2026-09-05 | Executed 2026-08-22 — inside the term | ✓ |
| Position owner: the sponsor | LP-NFT #59 minted directly to the sponsor's wallet — the engine never held it | ✓ |
Every row: actual ≤ cap. No row asks for trust in COSMO — each is checkable at a pinned block (full values in the evidence index).
Eight stations. From the sealing of the mandate onward, every station runs under the same fingerprint — one identity governs everything below it. Each card states what it requires from the station before and what it establishes for the next.
Two brand-new wallets — one for the machine, one for the sponsor — proven empty and unused before anything else happened.
The sponsor is funded and swaps ETH for SUPRA. Total exposure at this point: EUR 44.87 — against a EUR 500 hard cap.
The complete rulebook is frozen into one file. Its fingerprint IS the mandate's identity — change one byte and it is a different mandate.
The first run was stopped by the human sponsor before a single signature existed — then deliberately re-armed. The machine cannot move capital on its own.
The sponsor sends the exact amounts — to the wei. The machine spends them in two transactions and mints the LP position directly to the sponsor. The machine never owns the position.
Two separate proofs, two different kinds. Proof one is a state read pinned at the mint block itself (25810671, part of the OPEN case evidence): allowances zero, balances zero. Proof two is a dedicated on-chain transaction — the RESET case (block 25810738) — that re-establishes the same all-zero state under its own pinned policy and receipt.
Two verifier implementations replayed the archived evidence against the sealed mandate: ACCEPT, 10 of 10 criteria — for the OPEN, the RESET and (below) the CLOSE. The standalone verifier that returns these verdicts is the one published at heros.cloud/verifier/, byte-identical to the repository build.
Six days later the sponsor asked the mandate to close the position. Same ceremony, same gates: the sponsor granted a single-token approval, a human typed ARM and BROADCAST, the engine removed the full liquidity in one transaction — and paid the proceeds directly to the sponsor. The machine wallet never held them. The sponsor then revoked the approval; a fresh authority proof read zero standing approvals.
The mandate had an expiry written into its frozen text. After it passed, a read-only termination proof was taken at a pinned terminal block on two independent RPCs, and five separate predicates were derived: capital exposure zero, approvals zero, authority ended, ownership with the sponsor, and every nonce the wallet ever used mapped to an archived receipt. Then the operator typed the retirement phrase, the signing seed was shredded, and the one claim that cannot be proven — "no copy remains" — was recorded as an attestation with a standing falsification rule: any nonce above 4 on this wallet, ever, breaks it.
The machine's wallet held capital only between just-in-time funding and the mint — and the chain proves the empty states on both sides. The width of this plateau is deliberately not drawn to scale: the funding timestamps were not archived. What the chain proves is the entry and exit states, not the duration. The close on 2026-08-28 added no second plateau: the proceeds went from the position manager straight to the sponsor.
machine wallet token holdings (SUPRA + WETH)
─────────────────────────────────────────────────────────────────────
┌─────────────┐
│ funded │
0 ─────────────────────┘ └───────────────0──────────0──
proven empty wei-exact, proven empty proven AGAIN
@ 25810586 spent in @ 25810671 @ 25810738
(nonce still 0) 2 txs allowances 0/0 RESET case tx
balances 0/0 allowances 0/0
─────────────────────────────────────────────────────────────────────
"Capital entered, did its one job, and left. Nothing stayed behind."
The complete on-chain history of the execution wallet, from its first transaction to its last. Not "few" transactions — a countable, closed list, and now a closed life.
Check the address yourself — 0xC4F8b3d7a9737e8e85825F306bf0A8C6AEACb00B — any fifth transaction breaks this claim AND falsifies the seed-retirement attestation. Nonce read on two independent RPCs at the terminal block on 2026-09-05: 4. A watcher re-reads it every six hours.
The left column describes a common automation pattern — not any specific provider.
| A common automation pattern | This mandate |
|---|---|
| Standing token approvals that remain open after the trade | Allowances back to zero — read at the mint block itself, re-proven by a dedicated transaction |
| Capital parked in the bot's wallet, waiting | Capital arrives just-in-time, wei-exact, and is spent in the same ceremony |
| The bot holds the position; you trust it to hand it over | Position minted directly to the sponsor — never held by the engine |
| The bot can send any number of transactions, any time | This wallet sent exactly 4 transactions in its lifetime — all four listed above, provable via nonce — and its seed is retired under a falsifiable attestation |
| The bot keeps its keys — and its access — after the job | The mandate had an expiry; after it, a termination proof derived five predicates on-chain, the seed was shredded, and a standing watch will contradict the attestation the moment the wallet moves again |
| "Trust me" after the fact | Block numbers before, during and after — and a frozen mandate the outcome is measured against |
The question is never whether software can trade. The question is what it could have done — and here the answer is on-chain: nothing beyond the mandate.
10/10 criteria passed by the internal verifier AND by independent standalone verifier code, for OPEN and RESET; CLOSE followed on 2026-08-28. The verdicts are persisted as machine-readable files with sha3-256 pins.
The evidence bundle — the three case directories, the two termination records, the authority proofs and all 15 verdict files — is downloadable from the evidence index below.
The public verifier at heros.cloud/verifier/ carries the live policy pins (an additive update, profile id unchanged). Anyone can re-run the 10/10 check on each case and the termination check on each record. The 1.3.1 REJECT runs from before the republish are archived in the bundle alongside the ACCEPTs, deliberately.
Five termination predicates proven at a pinned terminal block on two RPCs; the seed-retirement attestation is the weakest evidence in the record and is labelled so. Should the standing nonce watch ever be falsified with block-pinned, two-source evidence, this line becomes "Terminated, contested".
Every block, transaction and nonce on this page is public — and so is the verdict: download the bundle and the verifier, run both offline, and compare. We ask you to check us, not to trust us.