Supported Assets
Assets Enablement Rules
Last updated
Assets Enablement Rules
Last updated
New assets can be added to dHEDGE V2 contracts if an asset has a Chainlink feed, or any reliable oracle feed, and has sufficient liquidity.
Up to 12 assets may be enabled for vaults to manage at any given time. Liquidity-providing tokens are considered assets that contribute to reaching that limit.
Assets enabled for a vault may be changed within the vault management page. All available assets are listed there as well.
For example, to utilize lending/borrowing via Aave, Aave Lending V3 token must be enabled.
Each vault in the protocol maintains a list of supported assets, which defines the tokens the vault can hold, trade, and accept for deposits. Pool managers can update this list by adding or removing assets, subject to strict protocol-level constraints to ensure vault integrity and user protection.
To add a new asset to the vault:
The token must be valid: It must pass the protocol’s asset validation checks (e.g. not a zero address, conforms to ERC-20, etc.).
Pools cannot add other vaults as assets: If the vault is connected to a price aggregator, it is restricted from adding other vault contracts as assets to avoid recursive pricing or circular dependencies.
Asset type is considered: Assets are internally sorted by type (as defined by the protocol) for consistent indexing and tracking.
Deposit flag is set: The manager can designate whether the new asset is allowed for direct user deposits into the vault.
If the asset is already supported, only its deposit flag is updated. Otherwise, the asset is added to the vault’s internal registry and indexed accordingly.
To remove an asset:
The asset must currently be supported.
Asset balances must be zero: A vault cannot remove an asset that still holds funds.
Guard logic may apply: If the asset is protected by a guard contract, an additional check is triggered before it can be removed.
Once verified, the asset is cleanly removed from the list and internal mappings are updated.
Maximum Asset Limit: Each vault has a cap on the total number of assets it can support. This maximum is enforced globally by the DAO by voting.
At Least One Deposit Asset: Every vault must support at least one asset that users can deposit.
Event Emissions: Every asset addition or removal is emitted on-chain for transparency and tracking.
Asset updates take effect immediately after a successful transaction by the vault manager. Changes are reflected on-chain, and visible to frontends, analytics tools, and integrators as soon as the block is confirmed.
