Loading...

Metalos keeps on-chain complexity low by integrating with proven Solidity vault contracts and layering orchestration on top. The vaults handle custody, strategy execution, and share accounting, while Metalos automation batches transactions, monitors safety thresholds, and coordinates session-key permissions.

Core Components

• Vault Contracts – ERC-4626-style vaults that accept an underlying asset (USDC or LP tokens) and mint share tokens representing proportional ownership. They expose canonical methods such as deposit, withdraw, balance, and getPricePerFullShare for accounting.
• Strategy Contracts – Dedicated modules that deploy capital into specific protocols (Morpho lending, Aerodrome liquidity pools). Strategies harvest rewards, reinvest them, and report profits back to the vault.
• Automation Coordinator – Off-chain service that batches approvals, swaps, liquidity provision, and deposit/withdraw steps into intent-based transactions. It also watches vault events and aggregates analytics.
• Session Key Registry – Optional signer delegation system that lets users authorize trusted devices with scoped permissions and limited lifetimes, making repeated interactions seamless without exposing the primary wallet key.

Vault Lifecycle

Each vault follows a predictable flow:

1. Deposit – Users approve the vault to spend the underlying asset, then call deposit. The contract calculates shares based on the current pricePerShare and mints them to the depositor.
2. Deploy Capital – The vault forwards assets to its strategy via earn() or automatic hooks. Strategies interact with external protocols, manage liquidity positions, and track pending rewards.
3. Harvest – When yield accrues, strategies convert rewards back to the underlying asset and return them to the vault. The vault increases pricePerShare, so all share holders benefit proportionally.
4. Withdraw – Users burn share tokens through withdraw or withdrawAll. The vault requests liquidity from the strategy if needed, then transfers underlying assets back to the user.

Strategy Implementations

• Morpho Lending Strategy (Extremely Safe tier) supplies USDC to Morpho’s lending optimizer. It avoids leverage and focuses on consistent interest income. Withdrawals simply redeem liquidity from Morpho and hand funds back to the vault.
• Aerodrome WETH-USDC Strategy (Not Very Risky tier) provides balanced liquidity to Aerodrome, stakes LP tokens, and compounds trading fees plus AERO incentives. Exits unwind the LP position and swap proceeds back to USDC.
• Aerodrome AERO-wstETH Strategy (Moderately Risky tier) pairs the AERO governance token with wstETH to capture a broader yield mix. It unwinds liquidity positions carefully to manage slippage before returning funds to the vault.

Security Model

Metalos layers operational controls on top of these audited contracts:

• Audit Requirements – Integrated vaults have undergone third-party audits, have significant time in production, and hold material TVL. Metalos reviews audit reports and on-chain history before onboarding.
• Upgrade Monitoring – Vault and strategy upgrades require multisig approval with timelocks. Metalos automation listens for upgrade events and pauses deposits if a change has not been reviewed.
• Emergency Pauses – All vaults expose pause switches so the Metalos multisig can halt deposits or withdrawals if anomalies appear (e.g., sudden drops in pricePerShare).
• Anomaly Detection – Off-chain monitors compare pricePerShare, share supply, liquidity metrics, and strategy balances against expected ranges. Deviations trigger alerts or automatic safeties.
• Session Key Limits – Delegated session keys are scoped to specific ABI methods (e.g., batched deposits) and expire quickly. Revocation can be performed on-chain if a device is compromised.

Integration Guidance

External developers can treat Metalos vaults like standard ERC-4626 tokens:

1. Deposits – Approve the vault address to spend the underlying token, then call deposit(amount, recipient) using ethers.js or another client library. The vault emits Deposit events with share amounts and new balances.
2. Withdrawals – Call withdraw(shares, recipient) to redeem underlying assets. For full exits, withdrawAll() simplifies the flow. Contracts emit Withdraw events for off-chain accounting.
3. Accounting – Use balanceOf(address) to read share balances and getPricePerFullShare() (or convertToAssets() in strict ERC-4626 implementations) to calculate current value. Combining both yields the user’s portfolio worth.
4. Automation – Batch approvals and deposits wherever possible (EIP-5792) to minimize user signatures. Respect slippage and gas constraints when invoking strategies that touch AMMs.