Loops HouseTally on NEAR

NEAR HACKATHON
Links
Team
1 member- PAOwner
pab
Overview
Tally on NEAR is the check a wallet or an AI agent calls before it sends money to a trader.
Tally (tallypnl.com) checks crypto PnL cards for fakes. Until now a verdict lived in Tally's own database, so you had to trust Tally not to change it. For the hackathon I built four contracts on NEAR testnet and a site that uses them:
-
Proof registry (proof.notpab.testnet). Each check is recorded as the card's fingerprint, the verdict and the time. Nobody can delete or rewrite a record, Tally included. A corrected verdict is added on top and the first one stays visible. No names or handles go on-chain.
-
Verified card (card.notpab.testnet). An NFT that can only be minted for a card the registry says is Real. It can't be sold or moved. Anyone can ask for a recheck, and it is burned if the verdict is corrected. It can hold money, and only its holder can withdraw it.
-
Paid check (check.notpab.testnet). An agent's owner loads a little credit and gives the agent a key that can only pay for checks, so that credit is all it can ever spend. Part of each fee goes into the checked card's verified card.
-
Guard wallet (tally-guard.testnet), an example. It asks the registry in the same call that would send the money. It pays the holder of a card the registry says is Real and refuses everything else, with the reason.
There is also an MCP plug-in for Claude Code and Codex with three free reads.
Everything runs on testnet with sample cards. No real agents or real traders use it yet. The README has five "do this, see that" steps: one curl reads a record straight from NEAR, the demo page shows it in a browser, and three one-line scripts run the demo agent, the guard wallet and 14 claims checked against the contracts.