AvaFenceAutonomous Agent
Payment Policy Enforcement Layer
AvaFence enables autonomous agents to execute on-chain payments safely through programmable policies, spending limits, recipient controls, replay protection, and revocable permissions.
Autonomous agents need financial control.
AI agents are becoming more autonomous, but permission boundaries around spending remain difficult to enforce.
Unlimited spending risk
Delegating private keys directly to autonomous agents exposes wallets to unconstrained fund depletion if an agent encounters a logic flaw, loops unexpectedly, or overspends without spending caps.
Unauthorized recipients
Without programmatic recipient controls, agent payments can easily be directed to arbitrary addresses or malicious counterparties, bypassing intended vendor and merchant boundaries.
Replay and duplicated execution
Network retries or replayed transaction requests can result in duplicate payments for the same action without unique request ID tracking and on-chain replay prevention.
Policy-controlled autonomous spending
AvaFence introduces a deterministic smart contract layer between autonomous agents and on-chain capital, ensuring strict parameter enforcement for every transaction.
Spending Limits
Set per-payment and UTC calendar-day limits within a funded policy budget.
Recipient Controls
Restrict payments to permitted recipients.
Replay Protection
Prevent re-execution of successfully executed request IDs.
Revocable Permissions
Revoke agent spending permissions and refund remaining policy funds.
Validated on Avalanche Mainnet
AvaFence Mainnet RC1 has completed a verified on-chain lifecycle test on Avalanche C-Chain, proving policy creation, spend enforcement, rejection boundaries, and clean permission revocation.
Detailed Mainnet RC1 Execution Records
Frozen records from Avalanche C-Chain Mainnet (Chain ID: 43114). Verified against commit 04346d4bb6.
| Step | UTC Timestamp | Transaction Hash | Recorded Result | Verification Scope |
|---|---|---|---|---|
| 1. Deployment | 2026-10-09T15:54:04Z | 0x23f55dab...f98a6f9b | Successful deployment; runtime matches frozen RC1 | Contract deployed to Avalanche C-Chain mainnet. Bytecode verified with Sourcify Exact Match. |
| 2. Policy Creation | 2026-10-10T17:04:55Z | 0x24251a66...66a77447 | PolicyCreated and MerchantAllowlistUpdated | Funded budget (0.0002 AVAX), per-payment limit (0.0001 AVAX), daily limit (0.0001 AVAX), and recipient controls registered. |
| 3. Authorized Spend | 2026-10-10T17:22:04Z | 0xfad46422...b48d2d69 | PaymentExecuted; 0.0001 AVAX paid once | Agent requested payment within policy limits to allowlisted recipient. Payment executed successfully. |
| 4. Unauthorized Block | 2026-10-10T17:38:10Z | 0xed945587...53d80039 | PaymentBlocked reason 4; no recipient value transfer | Spend request to non-allowlisted recipient blocked on-chain. Zero recipient value transfer occurred. |
| 5. Replay Protection | 2026-10-10T17:51:05Z | 0xbd0f0481...f2567456 | PaymentBlocked reason 3; same-ID request did not pay twice | Duplicate request ID rejected on-chain. Prevented double execution of identical spend request. |
| 6. Permission Revoke | 2026-10-10T18:15:19Z | 0x4131e86a...eebbf7d6 | PolicyRevoked; remaining 0.0001 AVAX refunded | Owner revoked policy permissions. Remaining 0.0001 AVAX unspent budget automatically refunded to owner. |
- Funded Budget: 0.0002 AVAX. Per-payment limit: 0.0001 AVAX; UTC calendar-day limit: 0.0001 AVAX; policy duration: 3600 seconds.
- Lifecycle Completion: Authorized payment (0.0001 AVAX) and blocked checks occurred within policy duration. Policy was subsequently revoked with remaining 0.0001 AVAX refunded to the owner.
- Final Account State: At the frozen checkpoint, policy is inactive, remaining budget is 0, active owner state is cleared, and contract balance is 0 AVAX.
- Boundary Transparency: Mainnet evidence proves this bounded small-value lifecycle. It does not constitute an independent security audit, nor does it claim over-limit or post-revoke negative test executions on mainnet. Source code exact match is verifiable via Sourcify.
Architecture & Execution Flow
AvaFence separates policy definition from agent operation. The agent never holds unilateral spending authority; every request must satisfy on-chain limits.
Roadmap
Grounding continuous development in verified on-chain milestones, expanding developer accessibility across the Avalanche ecosystem.
Mainnet RC1 Validation
- Bounded payment lifecycle validated on Avalanche C-Chain
- Sourcify Exact Match source verification
- Authorized payment, recipient blocking, replay protection, and revoke/refund
Developer & Builder Tooling
- Developer SDK
- Agent Framework Integration
- Builder Validation
Ecosystem Interoperability
- x402 / payment ecosystem exploration: HTTP 402 payment required integration research