Agent DeFi Altcoin

Convert intent into an executable policy

Write a narrow task such as preparing a report or proposing a transaction for specified assets. Then list the data and authority that task requires. Reading positions, constructing a proposal, and signing it should be distinct capabilities. A broad instruction to manage assets leaves the consequential boundaries undefined.

Represent proposals with explicit fields for network, target, method, recipients, assets, and amounts. Define missing information as a reason to stop. Require a separate review for policy changes so the agent cannot expand its permitted task while trying to complete an ambiguous request.

Enforce limits at the authorization boundary

ERC-4337 session-key documentation describes constraints enforced through wallet-specific logic. Check the implementation’s actual capabilities rather than assuming account abstraction supplies every desired restriction. Identify where permitted methods, expiration, spending limits, and revocation are validated, and whether another execution route could bypass that validation.

Test both individual and cumulative limits. A hypothetical permitted router may accept arbitrary recipients inside its arguments; approving the router address alone would leave those destinations unspecified. Review nested actions and batches. A rejected disallowed proposal provides evidence of enforcement that a promise in the agent’s explanation cannot provide.

Plan observation and shutdown

Before signing, decode the action and inspect material changes using the available review and simulation tools. Record proposal identifiers, policy decisions, and transaction outcomes without storing secrets. Distinguish an uncertain submission from a failed action so automatic retries do not repeat a transaction that already succeeded.

Document how to suspend the job, revoke delegated authority, inspect pending actions, and review existing token allowances. These may require separate operations. Rehearse a scenario in which retrieved content produces an unexpected proposal, then verify that the system stops at the authorization boundary and leaves enough evidence for an operator to investigate.

Primary reference: ERC-4337 documentation: Session Keys and Delegation. Read the current documentation for the exact network, asset, or product you are researching.