Testnet: tokens have no value, and the vulnerable contracts are our own test fixtures. Limits

Practice program — a tutorial (testnet)

A tutorial whose bug and proof are public: anyone can run a try on testnet, with no account and no key.

Try the practice program (14)

Practice program: a tutorialOpenround 0light-client confirmedstaging run, 2026-11-03
The staging run of 2026-11-03, on the same contracts before the lock: its results file records near-antibody with locked: false. The recorded run on the locked deployment (2026-11-04) is programs 5 (Acme Lend), 6 (practice) and 7 (fork mode).

Overview

The program as near-antibody stores it. Its manifest hash commits the anchor, the targets, the rules and the terms; once it is open, the deployment's owner can change nothing it depends on.
Project
antibody.testnet, account: antibody.testnet · ours
Description
TUTORIAL TARGET: 24 vaults with one textbook bug (sweep has no access check), published with its proof (docs/practice.md).
as written in the committed manifest
Program key
bounty.antibody.testnet/2, program key: bounty.antibody.testnet/2
Phase
Open round 0this round since
Created
Opened
Terms sha256
2a714747a7fe11e7…, terms sha256: 2a714747a7fe11e7c534424ec7c9f9b2baca7cb04928aa3aa3b69c32aeffae67
Manifest sha256
43a4abe4f18e0094…, manifest sha256: 43a4abe4f18e00947b4fb20d39731eb3c797ac44c9e94da3b08113dc2be442d1Uploaded in NEAR transaction 6xZqp2ZyDM…, NEAR transaction: 6xZqp2ZyDMCKuwG8jaVJ1RWYs7YEPNk6YvBc2eBykwya, opens an explorer in a new tab by antibody.testnet
Sealing key
e5fe5b7261f7e15b…, sealing public key: e5fe5b7261f7e15bdd37e85f79b3d05347c4accf9c3d8df8baa3dcb67bbb1715Proofs are sealed to it. It counts only once its activation run (run 22) is attested on NEAR.

Its record

At stake
0.0271wNEAR available now
Verified attempts
3
Paid findings
3
First claim
17 minafter it opened
Claimed in the first hour
10%of the escrow
Open for
147.3 h
view bounty.antibody.testnet.get_program({"program_id":2})

Holds if: the manifest hash shown here, as near-antibody stores it

antibody judge --program 2

Try it

A tutorial: its bug and its proof are public. Anyone can run the whole loop on testnet in a few minutes, with no account and no key; nothing here is a real vulnerability.

One rule, one textbook bug

Each of 24 small vaults holds a little ether, and its sweep(to) has no access check: anyone can send a vault's ether anywhere. The proof is one call to your vault; at the anchor the vault loses its ether, so vault_keeps_its_ether breaks. Each vault is its own target, so each try is its own finding.

antibody try --name <you>

The browser try and the CLI use the practice vending contract's program, program 14.

What a try does

  1. Vends you a practice account for a key your browser (or the CLI) generates; the key cannot withdraw or transfer.
  2. Builds the tutorial proof against the vault assigned to you, seals it to the program's key, commits and reveals it.
  3. Waits for the verdict and its attestation on NEAR.
  4. Allocates and pays (both permissionless), then closes the practice account: its NEAR goes back to the vending contract.

The payout goes to the vending contract's credit, which pays the next try's bond and run.

The rules as code

Each rule is one bit of the program's invariants contract. After a proof's calls, at the anchor, the verifier runs its check(): a set bit is a broken rule, paid by its severity. The verifier never reads a report.
The program's rules
RuleSeverityPayoutBudget per roundSource
vault_keeps_its_etherbit 0

No practice vault loses its ether.

Low
0.001 wNEAR
0.03 wNEAR

The budget caps what one rule pays per round, so many entry points into one root cause cannot drain the escrow. A finding's key is the rule and the entry point that broke it (by default, the target and function): the first proof of each key is paid.

The targets (25) on Sepolia

The terms

Committed in the manifest with the rules, their text fixed by the terms sha256, and enforced by near-antibody: no person decides a payout.

Payouts

The payout table
SeverityPayoutRules
Criticalnonenone
Highnonenone
Mediumnonenone
Low0.001 wNEARvault_keeps_its_ether
Bond per commit
0.0001 wNEAR · refunded, or forfeited to this program's escrow when the proof breaks nothing
Instant payments
up to 0.001 wNEAR
When a payout is instant

Paid in seconds when the verdict is attested on NEAR, within 0.024 wNEAR per 1 h. Otherwise a payout waits the challenge window; above the cap it also needs an agreeing second run.

Challenge bond
0.001 wNEAR
Protocol fee
none · pinned at 0 for this program
Release fee
none · pinned at 0 for this program
Verification deposit
0.03 NEAR per run, paid by whoever asks for it; OutLayer refunds the unused part

The escrow against the largest payout

27.1×the largest payout
0.0271 available / 0.001 wNEAR largest

The available escrow over the largest payout. Below 1× the status page raises an alert; a payout the escrow cannot cover is queued as debt, in commit order.

Pauses
No rule pauses anything.
Known issues
None allowed.
Gap lane
Off.
Unevaluable
A proof the rules cannot evaluate (check() reverts or runs out of gas) is refunded.

The windows

The program's windows
WindowLengthWhat it bounds
Reveal
10 min
A commit is revealed within this, or it expires and its bond goes to the escrow.
Challenge window
60 s
A verdict that is not paid instantly is final after this; anyone may challenge it within it, with the challenge bond.
Resolve
5 min
A challenge with no attested result within this voids the verdict; both bonds are refunded.
Run timeout
4 min
A run that never answered is void after this.
Infrastructure grace
10 min
An infrastructure failure is retried this long, then the commit closes with a refund.
Round minimum
2 min
A round runs at least this long before the next one opens.
Re-run window
10 min
Re-runs at a proposed fix may be asked for within this of its confirmed check.
Disclosure delay
10 min
A paid proof becomes public at most this long after its claim.
Exit grace
60 s
After the deadline plus this, anyone may settle the program (exit).
Deadline
No commit is accepted after it.

The anchor

Every proof runs on the state proven at one block. A pause ticket, and the verdict guard, act only on an anchor the light client confirmed: on a project-attested anchor a verdict is about state the project chose.
Chain
Sepolia (11155111)
Block
12055610 (opens an explorer)
Hash
0x7abf2c838e6b13585937c0373c749dfebb710e8f02415fafe380ff087bb29d08
Its check
confirmed by the light clientnear-antibody compared the hash with client-eth2.sepolia.testnet when the program was created.
Base witness
The anchor state the rules and the round-0 checks read, proven against the anchor and pinned at activation.e134f0a610b94dcf…, base witness sha256: e134f0a610b94dcf632fcec0f405307013a9c2ce666bd6b5a19accfc8c7069d6Uploaded in NEAR transaction 2sQvyA4A7B…, NEAR transaction: 2sQvyA4A7BmxyGNSS6gw5vRM8MDvkg58WTifNSUGzBmS, opens an explorer in a new tab by antibody.testnet

Check the hash yourself

view client-eth2.sepolia.testnet.block_hash_safe(12055610 as 8 little-endian bytes: 0x3af4b70000000000)

Expected: byte 0 is 1 (the client holds the block), then 32 bytes equal to the anchor hash.

The same check from a terminal, and the one that also hashes the block header from a Sepolia RPC:

antibody judge --program 2
antibody anchor-check --block 12055610

Known issues

Declared sealed before open; a later proof with the same tag is not paid again. Their count, rules and severities are public; their content stays sealed for good.
0 sealed
No known issue declared: every key this program prices was open to the first proof.

The chains

Per chain: the program's adapter, the proxies it may pause or upgrade, and every permit near-guardian asked the MPC network to sign, with the transaction that carried it there.
Reading the chains…

The tries

Every proof committed to this tutorial, practice tries labelled as such: who, when, the state, the verdict and the payout; never the proof.
Zero-knowledge proofs: none yet
The tries, in commit order
CommitWhoWhenStateVerdictKeysPayout
Commit 7#0 · round 0
judge-1-p2.practice.antibody.testnet, account: judge-1-p2.practice.antibody.testnetour check of a fresh practice programpaid to practice.antibody.testnet (the practice vending contract)
Expired
no verdict yetno verdict yet
—
—
Commit 8#1 · round 0
judge-1-p2-2.practice.antibody.testnet, account: judge-1-p2-2.practice.antibody.testnetan earlier run's practice trypaid to practice.antibody.testnet (the practice vending contract)
Paid
ViolationAttested on NEAR
vault_keeps_its_ether76e6fa70…, tag of vault_keeps_its_ether: 76e6fa705b5c15fc7afad23b0d36aee8ba0749979cfb9fb201d2518e609c1ecc
Commit 9#2 · round 0
judge-2-p2.practice.antibody.testnet, account: judge-2-p2.practice.antibody.testnetour check of a fresh practice programpaid to practice.antibody.testnet (the practice vending contract)
Paid
ViolationAttested on NEAR
vault_keeps_its_ethercffde910…, tag of vault_keeps_its_ether: cffde9104e54a78c0b20cd698f62bbfcb7efdd831aface4b6eba6fe691e9b751
Commit 11#3 · round 0
check-1.practice.antibody.testnet, account: check-1.practice.antibody.testnetan earlier run's practice trypaid to practice.antibody.testnet (the practice vending contract)
Paid
ViolationAttested on NEAR
vault_keeps_its_ether07fdd947…, tag of vault_keeps_its_ether: 07fdd94722c2a4d685427074100718d9e20a4de25866f0c06fc53243909e9650

A key is a rule and the entry point that broke it: the first proof of each key is paid; a later one is a duplicate that keeps its own proof record. Each commit's page shows its proof card and how to check it.

antibody status --program 2

Rounds and the release gate

A round ships a fix as code overrides at the same anchor. The enclave checks it, every paid proof is re-run against it, and a release permit is signed only for code that every paid proof fails against.
No round yet: this program still runs its round-0 code. A round is how a fix ships, and only a fix every paid proof fails against is released.

The ledger

Every movement of the escrow keeps funded equal to available + reserved + paid + fees + returned. Amounts in wNEAR, which has no value on testnet.
balances

Where the escrow is

Available0.0271
Reserved0.0000
Paid0.0030
Fees0.0000
Returned0.0000
Funded0.0301

What came in

Deposits0.0300
Forfeited bonds0.0001
Challenge bonds0.0000
Funded0.0301

Forfeited bonds go to this program's escrow, where they pay future findings: never to us. Here, 0.0001 wNEAR came in that way.

The audit

Accounted
0.0301
Reservations
0 · held by the commits; equals reserved when it balances
Debt
0 · owed and not yet funded, queued in commit order
Defaulted
0
view bounty.antibody.testnet.audit({"program_id":2})

Holds if: ok: true (funded equals accounted, and reserved equals the commits' reservations)

antibody view --contract bounty.antibody.testnet --method audit --args '{"program_id":2}'