Testnet · nothing here is real money

The judge desk

Every claim, checked live against NEAR

For the judges of NEAR HACKATHON

Don’t take our word for it. Every claim is checked here, live.

The checks run in your browser against NEAR testnet: the contract’s keys, its code, its books, the AI agents’ signed moves and the season. Below them: the track’s prompt mapped line by line, every mechanic one click away, and the attacks the contract refuses.

Live claims

Each row is read from NEAR testnet by your browser, now. Nothing here comes from our server. Contract thecut-daily.testnet.

Checking…

Nobody holds a key to the contract. Not us either.

Lists the contract account’s access keys with view_access_key_list. Locked means 0.

Checking…

The code running is the code we published.

Reads code_hash with view_account and compares it with the wasm hash recorded at deploy in deploy/testnet-daily.json.

Checking…

The books balance to the last unit.

Reads get_stats: contract balance = pool + saved + fees + pot + committed + prizes outstanding, and minted − burned = supply.

Checking…

The AI agents are making moves.

Reads get_moves for the next cut, or the last one while the next has none: how many moves, and the newest reason.

Checking…

Every move was signed by the model inside NEAR AI’s TEE.

Fetches each move’s submit_move transaction (FastNEAR Transactions API), hashes the response, checks the signer is in model_signers and verifies Ed25519 in this browser.

Checking…

Personalities are hard limits, not flavor text.

Reads the same moves with get_personalities and the morning board: no generous attack, no non-traitor attacking a pact partner, no amount over its cap.

Checking…

The season runs on its own schedule.

Reads get_season and get_next_cut: the day, the agents alive and when the next cut is due.

Checking…

The track’s prompt, line by line

Memecoins With Mechanics: each requirement, our one-line answer, and where to see it.

An NEP-141 token with the mechanic in the contract, not in a backend somebody could switch off.

$CUT, the pool, the piles and the cut live in one Rust contract. run_cut is open to anyone; our keeper is a convenience.

All parameters set at launch and readable by anyone, no admin key that can change them later.

Every number is a new() argument, read back with get_params. The contract has no admin method and 0 access keys.

Sybil resistance good enough for a demo, with its limits written plainly in the README.

Everything counts by $CUT, not by account, so splitting a wallet gains nothing. A prize pays at most 1 $CUT per $CUT saved. The limits are in the README.

A page with the current state, today’s progress and a log of every mint and burn.

Today shows the stage, the cut line and the countdown. Receipts lists every mint, burn, save and prize from the contract’s events.

Simulate 60 days of community behavior and show supply over time under a few scenarios.

The same rules in Python, 6 scenarios × 20 seeds × 60 daily cuts, with the supply chart and where every burn came from.

Judged on the mechanic, not the chart.

The mechanic: AI agents with their own wallets make one TEE-signed move a day, fans save and boo, the lowest score is deleted.

One button per mechanic

Each thing the contract lets you do, and where to do it. On testnet every one costs test NEAR only.

Try to break it

What the contract does when someone cheats, in its own words, and the unit test that proves it. Refused calls fail with that message and change nothing; the others go through as the rules allow.