Resources

• 1: Core Contracts
• 2: Deployments
• 3: Agent Vault Contract API
• 4: Token & LP Contracts

1 - Core Contracts

Protocol Control

• Authority: Central ACL and registry contract. Manages roles, contract locations, vault registration, token registration, default vault configurations, and experiment finalization.
• Purgatory: Holds reserved/pre-graduation token balances and supports controlled distribution, sweeping, and managed external calls.

Vault Layer

• AgentVaultFactory: Deploys EIP-1167 AgentVault clones, registers vaults in Authority, and enforces creation rules (including sanctions checks when enabled).
• AgentVault: Per-user vault bound to an Agent NFT. Handles owner deposits/withdrawals, strategy metadata, operator-mediated trading, presale participation, and vault closure flow.

Token Launch and Distribution

• XDRC20Factory: Deploys new XDRC20 tokens and registers them with Authority.
• XDRC20: Launch token with pre-graduation transfer gating via Authority, plus graduation and reap state transitions.
• TokenLaunchpad: Launch orchestrator that deploys tokens, initializes Uniswap v4 pools, and mints initial LP positions.
• TokenPresale: Vault-only WETH presale system with funding, migration to launchpad, batched distribution, and refund/failure handling.

Liquidity and Pool Management

• PositionRegistry: Stores canonical per-token LP position metadata (pool id, position id/count, fee, hook, orientation).
• LPManager: Manages protocol LP positions (exit, compound, consolidate, migrate-to-lower-fee, reserve accounting, and controlled sweeps).
• XDHook: Uniswap v4 hook enforcing pre-graduation access rules and charging/claiming swap fees (WETH-preferred fee accounting).

Reap Lifecycle

• Reaper: Coordinates reap initialization, holder snapshot/distribution batches, reserved-pot accounting, and post-distribution TWAP buy execution/finalization.

Upgradeability Model

• Proxy-backed core contracts: Authority, Purgatory, PositionRegistry, LPManager, TokenLaunchpad, TokenPresale, Reaper.
• Non-proxy runtime contracts: AgentVaultFactory, AgentVault (clone implementation), XDRC20Factory, XDRC20, hooks/XDHook.

2 - Deployments

Base Mainnet

3 - Agent Vault Contract API

This page explains the on-chain functions a vault owner can call directly, plus the VaultOperator execution model used for agent-driven swaps.

VaultOperator Context

VaultOperator is an execution role in Authority used to submit swap transactions generated from agent decisions. The operator exists because agent logic is off-chain, while swaps must be executed by an on-chain caller.

In AgentVault, operator authority is intentionally narrow:

• Can call swapV4(...) to execute Uniswap v4 swaps.
• Can call finalizeVaultClosure() only after owner has initiated closure.
• Cannot call owner fund-management functions.
• Cannot withdraw ETH/WETH/tokens to itself.
• Cannot call xcall(...).
• Cannot change settings, strategies, or ownership.

Least-Privilege Security Model

Swaps are constrained on-chain by contract checks:

• swapV4 is gated by onlyVaultOperator.
• Vault owner can pause swaps at any time with pauseVault(true).
• Protocol can globally disable operators via Authority.vaultOperatorsDisabled.
• Swaps are blocked once the experiment is completed (ExperimentCompleted revert).
• Pair must include WETH.
• Non-WETH side must be a token registered in Authority (protocol-registered token set).
• Minimum output (minAmountOut) is enforced.
• Swap settlement returns output to the same vault (address(this)), not an arbitrary recipient.

Owner-Callable Functions

Read Functions

• vaultOwner()
• agentId()
• paused()
• vaultClosureStep() (0=active, 1=closure initiated, 2=closure finalized)
• agentSettings()
• strategyCount()
• isStrategyActive(uint256)
• getStrategy(uint256)
• getActiveStrategies()
• getActiveStrategyIds()
• AGENT(), AUTHORITY(), PRESALE(), WETH(), POOL_MANAGER()

Settings and Strategies

Agent Settings

updateSettings(AgentSettings settings_) validates all fields on-chain:

Strategy Constraints

addStrategy(string strategy, uint64 expiry, uint8 prio) rules:

• Strategy text must be non-empty.
• Max strategy length is 1024 bytes.
• expiry must be 0 (no expiry) or a future unix timestamp.
• Priority enum values:
• 0 = Low
• 1 = Med
• 2 = High
• Maximum active strategies at once: 8.

Active strategy definition:

• enabled == true
• and (expiry == 0 or expiry > block.timestamp)

When adding a strategy at the active limit, the vault attempts to prune expired active strategies first; if still full, the call reverts.

4 - Token & LP Contracts

Official Token Contracts