BLINDKEY key mark

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 BLINDKEY key sealed in a dark glass box rimmed with green light
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.

Proposal gateSimulation
MPC signerChain Signatures · idle
Committed policy · fixture data, no fundsRecipient A · 0.01 ETH/order · 0.05 ETH/session · 0.001 ETH max fee
    Deposit slip · proof receiptSimulation
    proofDigest— awaiting a valid proof
    paramsDigest—
    reservedCost—
    nonce—
    SimulationSigned · MPC
    The owner commits a private policy while the agent's proposal waits at the sealed key

    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.

    1. create_session
    2. Groth16 verify
    3. reserve costMax
    4. contract builds type 2 bytes
    5. MPC signs
    6. relayer broadcasts to Robinhood Chain testnet
    Private limits stay sealed behind frosted glass while the proof receipt stays verifiable

    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.

    1. private recipients · caps · max fee · expiry
    2. agent never touches the signer
    3. policy witness never shown
    4. 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

    Simulation

    /terminal · proposal timeline

    Terminal

    Simulation

      /verify · five flags, never a total

      Verify

      Simulation

      Each flag stands alone. There is no combined result. ZK confirms execution rights, not model reasoning or profitability.

      Create session · policy ritual

      Close session?

      New proposals will be refused and no further signatures will be requested. Signatures already issued are not revoked.