Overview
Balances and authority across your vaults.
Illustrative preview. Example balances and capabilities. Transactions are disabled.
How it works
Fund a root, authorize a master agent, and let it delegate smaller amounts and narrower permissions down a tree of separate on-chain vaults. The human owner keeps an independent recovery path — separate from the agents, ENS, and the activity indexer.
Capital, permission, and a running agent are three separate things. A valid mandate does not prove that a bot is actually running.
- A human funds a root vault and authorizes a master agent.
- The master moves part of its capital into a child's separate vault. Children can delegate again, up to three levels.
- ENS roles plus our controller enforce inherited limits — descendants can never broaden their mandate.
- Chat actions use a separate operator key. Creating a child vault does not start an autonomous worker.
- Revocation stops future management. Funds stay in the vault until a separate recovery action.
- Vault balances
- 24.865 USDC 12.570 DEMO-USD
- Nodes
- 6 / 32 6 active · three levels maximum
- Open positions
- 1 Uniswap v4
Nodes
View tree| Node | USDC balance | Status |
|---|---|---|
| capital.kanoki.eth | 14.625 USDC | active |
| market.capital.kanoki.eth | 3.700 USDC | active |
| scout.market.capital.kanoki.eth | 0.830 USDC | active |
| liquidity.market.capital.kanoki.eth | 1.960 USDC | active |
| steward.capital.kanoki.eth | 2.500 USDC | active |
| reserve.steward.capital.kanoki.eth | 1.250 USDC | active |
Owner 0x1234…7890. Recovery remains separate from node capabilities.
Owner controlsAgent tree
Inspect each vault’s capital, permissions and place in the delegation tree.
Owner control
Fund your root, authorize an operator and review the independent owner recovery controls.