BLINDKEY · execution rights by proof · NEAR
Every move needs a proof.
Trong sản phẩm, move chỉ lệnh do agent được ủy quyền đề xuất.
In the product, a move is an order your authorised agent proposes. Nothing is signed without a proof.
the key is the signer · sealed
You commit a private policy on NEAR. Your agent proposes; a ZK proof shows the proposal matches the commitment. Only then does the contract ask Chain Signatures to sign. The agent never holds the key, and the policy witness is never shown.
Run proposal 1 to see a signature
All three proposals ran. Every move needed a proof; only one got a signature.
View full terminal
How it works
The onchain loop
Owner commits a private policy. Agent proposes. ZK proof confirms the proposal matches the commitment. Only then does the contract request Chain Signatures. Quota is reserved at max cost before anything is signed.
- create_session
- Groth16 verify
- reserve costMax
- contract builds type 2 bytes
- MPC signs
- relayer broadcasts to Robinhood Chain testnet

Why crypto natives care
Limits stay private. Rights stay provable.
Recipients, caps, fee ceiling and expiry live in a private policy; only its commitment is onchain. The agent never touches the signer: it can only propose, and a proposal without a valid proof halts at the first wrong cut. Anyone can verify the receipt afterwards.
- private recipients · caps · max fee · expiry
- agent never touches the signer
- policy witness never shown
- anyone can verify
MVP scope
- One agent per session.
- One EVM target chain.
- Native asset transfer type 2 only.
- Policy witness never shown.
- All demo data marked Simulation.
/sessions/new · policy ritual
Create session
/terminal · proposal timeline
Terminal
No proposals yet. Run the simulation from home.
/verify · five flags, never a total
Verify
Each flag stands alone. There is no combined result. ZK confirms execution rights, not model reasoning or profitability.