Keyfree · your own policy on testnet

Run your own policy

Paste your contract, pick chains and limits. You get the code hash your policy's allow list must hold, a ready setup/config.json, and the exact commands in order. Everything is computed in this page: it asks for no key and makes no network request at all.

Testnet only. The guardian and the reserve should be accounts you create on other devices, not on the machine where the agent runs. Before real money this needs a professional audit (SECURITY.md lists the known limits).

1 · Your contract

Paste init code Load a Foundry or Hardhat artifact

Init code (hex)

Creation bytecode followed by the ABI-encoded constructor arguments, exactly what the deploy transaction carries.

2 · Who decides and where

Account names are NEAR testnet ids (lowercase letters, digits, -, _, .; 2 to 64 characters; ending in .testnet). The setup script creates the policy and the agent as sub-accounts of the owner, so both names must end in .<owner>. The guardian and the reserve must already exist.

Rules delay, hours

Upgrade and role delay, hours

Chains

Gas cap per transaction

Fee cap, wei per gas

3 · What you get

The code hash your allow list must hold

Give a valid contract in step 1.

setup/config.json

Fix the fields in step 2.

Save it as setup/config.json in the repository. Everything not set above is copied from setup/config.example.json.

The commands, in order

Run them from the repository root (Node 20.3+). The owner's key is read from ~/.near-credentials/testnet/<owner>.json.

Fix the fields above.