Keyfree · live on NEAR testnet
Your AI deploys contracts. Nobody holds the key.
Not a spending limit: Keyfree decides which code an AI agent may deploy and which upgrades it may make, and nobody holds the key that signs them.
Read from public NEAR nodes in your browser for
policy13.keyfree-lab.testnet. Anything that cannot be read says unknown.
Pick a door
How it works
The agent asks
The agent's NEAR key can only call the request methods; rules, roles and upgrades belong to a council of three humans.
A contract on NEAR decides
The policy is a NEAR contract with no access keys. It holds the rules: which init code may be deployed, on which chains, with which caps and daily budget.
NEAR MPC signs
The policy builds the EVM transaction itself and asks NEAR MPC to sign it for its own derived address. It never signs a hash someone hands it.
Why now
Teams lose real money when one key can upgrade their contracts. In each case below a single stolen key was enough (sources).
- Wasabi Protocol, April 2026: about $5 million.
- Zoth, March 2025: about $8.4 million.
- DeltaPrime, September 2024: nearly $6 million.
Each was one stolen key that could upgrade contracts.
For judges
| Criterion | Where to click |
|---|---|
| Technical implementation | CLAIMS.md: every claim with its evidence; npm run check:claims re-checks them. |
| Design | The challenge and the explorer |
| Impact | The Why now section above, and examples/ci |
| Originality | How this differs from other ways to keep the key from the agent |
| Sustainability: what it takes to use it | Run your own policy |