Everything read on this venue, and what has not been. Figures are ours unless a line says a venue reported them.
Users act on every vault. Whether the vault acts, moving assets when nobody deposited or withdrew, is a separate reading, and it is what separates a managed strategy from a container.
Read all 2 of its vaults over 25.5 days and found no asset movement outside a deposit or a withdrawal, nothing we can attribute to a vault acting on its own account.
Read 2026-10-11.
How much of the capital on Almanak sits under a vault an agent runs, and what stands behind each answer.
$12.6k of $12.6k is under a vault we have reason to call agent-managed; 100.0% of the capital, in 2 of 2 vaults.
| Who can move it | Capital | Share | Vaults |
|---|---|---|---|
| Agent, declared by the venue | $12.6k | 100.0% | 2 vaults |
Each vault counts in one band only, its strongest evidence, hover a band for what stands behind it.
Composition
Networks, not vaults. How a venue spreads across chains is a shape; which vault sits on which chain is the register below, and that is the paid half.
The underlying asset each vault reports. ‘Not read’ is a vault whose asset we have not established, which is different from one holding nothing.
| Asset | Vaults | Capital |
|---|---|---|
| USDT | 1 | $11.5k |
| USDC | 1 | $1.1k |
| Vault | Network | Capital | APY | Risk |
|---|---|---|---|---|
| Ethereum | $11.5k | — | 12 | |
| Base | $1.1k | — | 46 |
Three ERC-4626 vaults, read from chain. Its user-created vaults are a separate and larger set behind a factory we do not yet enumerate, so this is a floor on Almanak rather than all of it.
Capital and yield are as the venue or an aggregator reports them unless a vault’s own page says it was read from the contract. Nothing on this page is a recommendation, and a venue appearing here is not an endorsement of it.