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.
Not read yet. We have this venue’s deposits and withdrawals, which are things done to a vault; what its manager does has not been looked at. That is a gap in our reading and not a finding about the venue.
How much of the capital on Avant avUSD sits under a vault an agent runs, and what stands behind each answer.
$0 of $104.9M is under a vault we have reason to call agent-managed; 0.0% of the capital, in 0 of 1 vaults.
| Who can move it | Capital | Share | Vaults |
|---|---|---|---|
| Not agent-managed | $104.9M | 100.0% | 1 vault |
Each vault counts in one band only, its strongest evidence, hover a band for what stands behind it.
| Network | Vaults | Capital | Share |
|---|---|---|---|
| AvalancheAvalanche | 1 | $104.91M | 100.0% |
The party the venue names as curator or manager, where one is named. A venue is a place; an operator is somebody making decisions in it.
| Operator | Vaults | Capital |
|---|---|---|
| 1 | $104.91M |
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 |
|---|---|---|
| avUSD | 1 | $104.91M |
| Vault | Network | Capital | APY | Risk |
|---|---|---|---|---|
| Avalanche | $104.91M | 7.8% | — |
The venue’s own published size is $124.96M against the $104.91M we hold across 1 vaults. The two measure different things, theirs is the whole protocol, ours is the vaults we track, and the gap is our coverage rather than a disagreement.
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.