Build

Vault operations

Know which controls are local policy simulation and which require an owner-signed Arc transaction.

Offline and live

Every new agent starts with an offline vault record. Offline mode supports policy preflight and security simulations but never reports an on-chain payment as executed. A vault becomes live only after Peribolos verifies the deployed contract and its agent key.

Live state is chain-authoritative

The dashboard reads owner, balance, signer, expiry, pause, caps, retained float, and action bitmap from Arc. It does not let a database edit masquerade as a contract rule change.

Rules and pause

For a live vault, connect the owner wallet on the Vaults page. Update rules on Arc calls setRules; Pause and Unpause call the contract directly. After receipt confirmation, the app invokes:

POST

/v1/vaults/:id/sync

Refresh the workspace mirror from the authoritative Arc contract. It accepts no client-supplied rule values.

Funding

Arc Testnet uses native USDC for value transfers. The dashboard sends value from the connected wallet to the vault, then records the event only after verifying receipt status, recipient, sender, and amount.

POST

/v1/vaults/:id/fund

Verify and record an already-mined funding transaction. This endpoint does not move funds.

Signer rotation

Live rotation is deliberately two-phase:

/signers/rotate/prepare provisions one pending managed signer.
The connected owner calls rotateAgentKey(newSigner, expiry).
/signers/rotate/confirm verifies the transaction targeted this vault, emitted AgentKeyRotated for that signer, and matches current contract authorization before promotion.

confirmation body

{
  "vaultId": "v_…",
  "agentId": "ag_…",
  "newSignerAddress": "0x…",
  "txHash": "0x…"
}

Hosted signer revocation

Revocation is not an on-chain pause

Revoking the managed signer stops Peribolos from using it. If the vault is live, the contract still recognizes that address until the owner pauses the vault or rotates its agent key. The API reports this owner action explicitly.

Offline and live

Live state is chain-authoritative

The dashboard reads owner, balance, signer, expiry, pause, caps, retained float, and action bitmap from Arc. It does not let a database edit masquerade as a contract rule change.

Rules and pause

For a live vault, connect the owner wallet on the Vaults page. Update rules on Arc calls setRules; Pause and Unpause call the contract directly. After receipt confirmation, the app invokes:

POST

/v1/vaults/:id/sync

Refresh the workspace mirror from the authoritative Arc contract. It accepts no client-supplied rule values.

Funding

POST

/v1/vaults/:id/fund

Verify and record an already-mined funding transaction. This endpoint does not move funds.

Signer rotation

Live rotation is deliberately two-phase:

/signers/rotate/prepare provisions one pending managed signer.
The connected owner calls rotateAgentKey(newSigner, expiry).
/signers/rotate/confirm verifies the transaction targeted this vault, emitted AgentKeyRotated for that signer, and matches current contract authorization before promotion.

confirmation body

{
  "vaultId": "v_…",
  "agentId": "ag_…",
  "newSignerAddress": "0x…",
  "txHash": "0x…"
}