Account Structure

Aegis employs an advanced account abstraction model to ensure security, isolation, and automation capabilities. This structure is built upon the ERC-4337 standard and utilizes Coinbase's Base Account solution.

1

The Three-Address Architecture

The system relies on a strict one-to-one-to-one mapping between three distinct address types for every user. This "Trinity" ensures that asset ownership remains clear while enabling autonomous management.

User Address

  • Definition: The external wallet address used by the user to sign in to Aegis (e.g., MetaMask EOA or a third-party smart wallet).

  • Role: The ultimate owner of the capital. All deposits originate here, and all withdrawals return here. The User Address holds the authority to configure strategies and initiate withdrawals.

Smart Address (Smart Contract Account)

  • Definition: A dedicated ERC-4337 smart contract wallet deployed on the Base network.

  • Technology: Built on the Coinbase Base Account implementation.

  • Role: The custodian of the investment assets. When a user deposits funds into Aegis, they are transferring them to this specific address.

    • Isolation: Every user has their own unique Smart Address. There is no commingled "Aegis Pool."

    • Positions: All DeFi positions (e.g., aToken balances, Morpho shares) are held directly by this address.

Agent Address

  • Definition: An EOA (Externally Owned Account) controlled securely by the backend AutoFi Agents.

  • Role: The controller of the Smart Address.

  • Authority: The Agent Address has the permission to execute transactions on behalf of the Smart Address. This authority is limited to the scope of investment operations defined by the protocol's logic.

2

Mapping and Initialization

Upon a user's first successful Sign-In (via EIP-712 signature):

1

Generate Agent Address

The system generates a unique Agent Address.

2

Provision Smart Address

The system deploys (or provisions) the Smart Address.

3

Establish Mapping

The mapping User Address <-> Smart Address <-> Agent Address is immutably established in the system database.

3

Security Implications

This architecture provides a robust security model:

  • Physical Isolation: Since assets are not pooled, a compromise in one user's strategy or a theoretical bug in a specific interaction does not directly expose other users' funds.

  • Authorized Execution: The AutoFi Agents can only move funds within the context of the Smart Address logic. They do not have custody of the User Address's private keys.

  • Transparency: Because the Smart Address is a standard on-chain entity, users can independently verify all holdings and transactions via any block explorer, ensuring "Don't Trust, Verify" principles are upheld.

Last updated