Loading
Networks
Dydx
Capital only. We track vaults here and read no agent rail, so nothing on this page speaks to whether agents transact on this network.
Capital
$1.72M
1 vaults, 0 agent-managed
Agent events
no rail read here
a gap of ours, not a finding
Last 30 days
nothing to count
Flows held
none read yet
we hold vaults here but have read no movement
Who manages the capital
How much of the capital on Dydx sits under a vault an agent runs, and what stands behind each answer.
$0 of $1.7M 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 | $1.7M | 100.0% | 1 vault |
Each vault counts in one band only, its strongest evidence, hover a band for what stands behind it.
Protocols holding the capital
The venues we read on this network, and what each holds. Agent-native means the protocol was built for agent-run strategies rather than having them arrive later.
Largest vaults here
| Vault | Capital | Risk |
|---|---|---|
| dYdX MegaVault dYdX | $1.72M | unscored |
What we can and cannot say here
Risk coverage
no agent vaults
Under one key
none found
every vault here had its control readable
Sitting idle
not read here
Changes recorded
1
on vaults here in the last 30 days
Capital is the total under vaults we track on Dydx, not the network’s total value locked, we read agent-managed strategies and a comparison set, never the whole chain. Everything here is computed from records we hold; where a figure is missing this page says which kind of missing it is rather than printing a dash. See Methodology for how far back each reader reaches and whose limit it is.