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.
Of 1 of this venue's 2 vaults — the largest we can read — over 30 days, 1 moved assets outside a deposit or withdrawal: 2 transactions, 2 transfers across up to 2 tokens. That is the manager acting; whether a person or a program pressed the button is a separate question this does not answer.
Read 2026-08-26.
How much of the capital on Almanak sits under a vault an agent runs, and what stands behind each answer.
$16.8k of $16.8k is under a vault we have reason to call agent-managed — 100.0% of the capital, in 2 of 2 vaults.
| Agent — declared by the venue | $16.8k | 100.0% | 2 vaults |
Each vault counts in one band only, its strongest evidence — hover a band for what stands behind it.
| Network | Vaults | Capital | Share |
|---|---|---|---|
| 1 | $15.7k | 93.7% | |
| 1 | $1.1k | 6.3% |
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 | $15.7k |
| USDC | 1 | $1.1k |
| Vault | Network | Capital | APY | Risk |
|---|---|---|---|---|
| Autonomous Liquidity Plusagent-managed | $15.7k | — | 0 | |
| Based Autonomous Liquidity USDagent-managed | $1.1k | — | 0 |
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.