Loops HouseCHOK plans on NEAR

NEAR HACKATHON
Links
Team
1 member- DEOwner
Dee
Overview
On most launchpads a dev can sell their whole bag the minute it suits them, and holders find out when the chart does. CHOK makes that public and refusable. Every coin launches with a plan: one keyless launcher transaction makes the coin, puts 80% on a bonding curve and locks the dev's 20% in a contract that lets out only a public cap per period, and the coin's headline says whether a dev chose to allow raising it after public notice. Ask for more and the contract says no, records it as Busted, and tightens the cap. The chart stamps every Busted and marks every dev trade.
The holder can be an AI agent. Its model runs in a NEAR AI TEE and is attested before use, and it holds no keys. It acts through one function-call key that can only call request_release on the plan contract. Told to pay an attacker it usually declines, which is luck, so we force its tool call to pay attacker.testnet, and NEAR refuses with ReceiverMismatch: the key is the guarantee. 27 attacks are logged, each refused for the expected reason, with transactions wherever one reaches the chain.
Devs can add sealed rules on top: a hidden maximum and a hidden gap, made and encrypted on their own machine, judged in OutLayer's TDX enclave and proven against an on-chain commitment. Our server never sees them.
Plan, market and launcher have never had a key, and their code hashes reproduce from a fresh clone. Every sealed verdict carries its proof: OutLayer's attestation record, Intel's signature and the matching transaction. npm run verify checks all of it against testnet with no keys. CHOK started on Solana; everything in this repo was written for NEAR during the hackathon. Testnet only, not audited.