Sub-accounts
The Ethereum Vault Connector (EVC) gives one wallet 256 account IDs, each represented by a derived address. A sub-account can hold its own collateral, controller, and liability state while remaining under the same controlling wallet.
This lets users keep positions separate without maintaining another signing key and native gas balance for each one. For example, a user can keep a USDC/WETH borrow in one sub-account, a separate Multiply position in another, and authorize an operator for only one of them. EVC-aware integrations can also batch supported actions across sub-accounts.
Why use separate sub-accounts?
- Keep collateral and debt for unrelated positions separate.
- Use different controllers or collateral sets without combining every position.
- Grant an operator access to one position without authorizing it for all positions.
- Manage several positions from one wallet and, where supported, batch their actions through the EVC.
Sub-accounts separate account state, but they do not create a new owner. A compromised owner or shared operator can still affect every account it controls, and different positions may still share vault, oracle, and market dependencies.
Important considerations
Derived account identities: Sub-account addresses are derived EVC account identities. They are intended for EVC-aware vault and external-contract flows, including use as an on-behalf-of account. Do not send ordinary ERC-20 tokens directly to a derived sub-account address, and do not assume a non-EVC-aware contract recognizes its relationship to the owner. Use an integration that explicitly supports EVC sub-accounts.
Position isolation: Review each position separately and also consider the wallet's total exposure across sub-accounts.
Batched actions: The EVC can batch compatible actions, but token approvals, controller rules, authentication, and final account checks still apply.