Onchain asset management, defined
Onchain asset management uses blockchain accounts and smart contracts for some or all of a portfolio's custody, permissions, execution, accounting or settlement. The public ledger can make balances and transactions inspectable. It does not automatically make the manager non-custodial, the strategy safe, the accounting complete or withdrawals available on demand.
The right starting point is the control boundary. Identify who owns the assets, who can move them, which contracts can change, where prices come from, how returns are calculated and what happens when the normal exit path fails.
Five common structures
| Structure | Where assets sit | Who decides? | What to inspect |
|---|---|---|---|
| Self-managed wallet | User-controlled account | User or delegated tool | Approvals, signer security and transaction review |
| Smart account mandate | User-linked programmable account | Policy-bound signer or agent | Allowed functions, limits, expiry and recovery |
| Tokenized vault | Pooled strategy contracts | Strategy role, keeper or governance | Share accounting, privileged roles and withdrawal mechanics |
| Managed onchain vehicle | Segregated or pooled addresses | Named manager under a mandate | Legal claim, custody path, fees and reporting |
| Hybrid manager | Onchain and offchain venues | Manager, software and external custodians | Offchain completeness and reconciliation |
“Onchain” can accurately describe one layer while other layers remain offchain. A vault may settle deposits and withdrawals onchain while receiving prices from an oracle and using an offchain operator. A manager may publish wallet addresses while maintaining hedges on a centralized exchange. The label is useful only when its scope is stated.
The six questions that define control
Custody is not a yes-or-no label
A product may describe itself as non-custodial because the provider does not hold a conventional private key. Yet a smart contract can still grant an administrator, strategy role or upgrade authority meaningful control. Token allowances can let another contract transfer assets. A pause role can prevent exit, and an upgrade can change future behavior.
| Claim | Verify onchain | Verify outside the chain |
|---|---|---|
| “You keep custody” | Signer roles, allowances, transfer paths and upgrade authority | Recovery provider, user agreement and key-handling process |
| “Assets are segregated” | Distinct accounts, vault balances and commingling paths | Legal treatment and claims in insolvency |
| “Withdraw anytime” | Redemption function, gates, queues and available liquidity | Operational approval, sanctions and service dependencies |
| “Fully transparent” | Addresses, positions, debts and transaction history | Offchain hedges, liabilities, ownership and agreements |
Inspect exact contract addresses and roles instead of relying on a custody adjective. Ethereum's smart- contract security guidance recommends explicit access controls and disaster-recovery planning; it also warns that an audit cannot catch every defect.
How vault accounting should work
A pooled vault commonly represents each depositor's claim with shares. Deposits add assets and mint shares; withdrawals burn shares and return assets. A basic share price divides net assets by shares outstanding, but each term needs a policy.
share price = (assets at fair value − liabilities − accrued fees) ÷ shares outstanding The calculation becomes difficult when assets are illiquid, prices are stale, rewards are not claimable, debts change between blocks, or a hedge exists elsewhere. Deposits and withdrawals can also distort a naive wallet-balance chart. Performance reporting should use a method that accounts for cash flows and state the valuation time, price sources, fees and treatment of unclaimed rewards.
Gross yield is not portfolio return
A protocol's displayed annual percentage yield may exclude gas, swap losses, hedging costs, performance fees, idle collateral and rate changes. If leverage is involved, it may also hide liquidation exposure. Compare the depositor's change in redeemable value after all charges, not a selected component of the strategy.
What the blockchain can prove
- State: an address held a recorded balance or position at a specified block.
- Authorization: a valid signature or contract rule authorized a transaction.
- Execution: a transaction produced a recorded state transition.
- Rules: published contract code may reveal enforceable logic for a named version.
Those facts are valuable, but they have boundaries. They do not establish beneficial ownership, complete offchain liabilities, fair valuation, future liquidity, strategy suitability or the absence of a hidden hedge. A proof can verify a carefully defined statement; it cannot make an underspecified claim complete. The ZK trade-proof guide shows how to separate execution evidence from performance and judgment.
Where AI fits
AI may summarize positions, classify risk, propose allocations or coordinate approved actions. It should not replace the portfolio mandate or the accounting policy. An agent's output needs to become a typed intent that an independent control layer can approve, resize or reject.
Read the AI trading agents guide for that execution loop. When the agent operates across DeFi protocols, the DeFAI guide adds contract, oracle, allowance and transaction-simulation questions.
Risk does not disappear when records are public
- Contract risk: code, integrations or upgrades can contain exploitable behavior.
- Administrative risk: privileged accounts may change logic, pause exits or move assets.
- Oracle risk: a stale or manipulated price can corrupt valuation or trigger liquidation.
- Liquidity risk: the recorded position may not be redeemable at its displayed value.
- Bridge risk: assets represented across chains inherit additional validator and contract assumptions.
- Market risk: transparent positions can still lose value, gap or become crowded.
- Operational risk: signers, front ends, APIs, keepers and monitoring can fail.
- Legal risk: an onchain token does not by itself define the holder's enforceable rights.
The CFTC's DeFi report emphasizes that benefits and risks depend on a system's specific design and that many systems lie on a spectrum rather than being completely centralized or decentralized. A credible evaluation therefore maps responsibilities instead of assigning safety based on the label.
Due diligence before depositing
- Confirm the network, contract addresses, deployed code version and official interface.
- Map owners, multisigs, strategy roles, upgrade roles, pause roles and external keepers.
- Read audit scope, dates, unresolved findings and changes made after the reviewed version.
- List every asset, protocol, bridge, oracle, exchange and custodian the mandate can use.
- Check position, concentration, leverage, slippage and daily-loss limits.
- Understand share pricing, fee accrual, cash-flow treatment and benchmark selection.
- Test a small deposit and withdrawal path, including queue, delay and failure behavior.
- Find the emergency pause, permission-revocation, incident-response and communication process.
- Separate backtested, simulated and live results, and verify the covered dates.
- Determine which legal entity is responsible and what recourse exists if controls fail.
A clearer comparison with adjacent products
| Product | Primary relationship | Key question |
|---|---|---|
| Trading bot | Software executes rules in an account | Who owns the account and API credentials? |
| Copy-trading service | Follower mirrors another account's activity | How do lag, sizing and divergent fills affect results? |
| Onchain vault | Depositor receives a claim on pooled strategy assets | How are shares, authority and redemption defined? |
| Managed account | Manager acts under an individual mandate | Which controls are technical, contractual and supervisory? |
If the implementation crosses data, policy, execution and recovery components, use the automated trading systems reference architecture to inspect the complete operating path.
Sources and scope
- CFTC Technology Advisory Committee — Decentralized Finance report
- IOSCO — Policy Recommendations for Decentralized Finance
- Ethereum.org — Smart contract security
- Onchain Off Emotion — Backtests versus live results
- Onchain Off Emotion risk disclosure
The control model and accounting example are educational frameworks, not legal, tax or investment advice. They do not certify a product or establish the availability of a specific product feature.