Skip to main content

​
Contracts

AgentRegistry. Builder identity, agent listings and USDC bonds. A bond sets a tier, the tier caps a builder’s total AUM, and slashing splits 70/30 between harmed traders and the buyback pool. HLAgentVaultFactory. Deploys one EIP-1167 minimal-proxy vault per trader and listing. HLAgentVault. Holds the trader’s position on HyperCore. In vault mode it checks six conditions before sending each order; it reconciles orders, charges fees on reconciled size, and enforces the drawdown kill switch. Only the trader can withdraw. The Hyperliquid vault walks through it call by call. HLMarketWhitelist. The HyperCore assets agents may trade. Additions are timelocked and public; removals are immediate.

​
Why one vault per trader

On HyperEVM, a contract’s address is its HyperCore account. A single shared vault would put every trader in one account with commingled positions. Clones give each trader an account of their own, so attribution is structural rather than bookkeeping.

​
Talking to HyperCore

  • CoreWriter sends actions such as orders, API-wallet registration and builder-fee approval. Actions are applied a few seconds later, and the contract cannot see at send time whether they were accepted.
  • Read precompiles give positions, balances and mark prices, which reconcile uses to settle the truth.

​
Design records

The trade-offs are written up in docs/adr in agent-circle-evm: ADR-0001 on vault topology, ADR-0002 on execution modes.