Wrapped Aave Ethereum USDCwaEthUSDC
Static aToken, deployed by Aave · 0xd4fa…d23e · asset USDC
Aave publishes AaveV3Ethereum.STATA_FACTORY, and that contract's own StataTokenFactory.getStataTokens() returned this address at the block below.
Read at block 25,922,389 · every figure below is a call answered at that block, on this vault and on the contracts it names.
The share supply valued at the reserve's own index in the Pool.
Every share of this vault in existence, in the share token's own decimals.
What one whole share converts to, answered by the vault. Asked with 10^6 — this vault's own decimals.
How a static aToken works
This vault wraps exactly one Aave V3 aToken, so a holder’s shares are a non-rebasing claim on a supply position in the Aave V3 Core market. The share price above is not this vault’s own arithmetic: it is the reserve’s accrued index in the Pool, which is why a wrapper holding nothing still answers a share price well clear of parity. There is no withdrawal delay and no queue — the only gates are the reserve being inactive or paused, and the wrapper’s own pause flag.
Asked of the wrapper itself, not searched for across Aave's three Ethereum Pools.
The wrapper's own supply position, as the Pool reports it.
The wrapper's own floor rounding, stated rather than reconciled away. No order between the two is asserted.
The reserve’s liquidity index in the Pool is 1184691455665589244152983861 — a RAY, and the same fact as the share price above read from the other end. The Pool is 0x8787…a4e2, which is the one the wrapper itself names in POOL(). That Pool answers the same aToken for this reserve as the wrapper does, so the link is read from both ends rather than taken on the wrapper’s word.
The wrapper's own rewardTokens() returned an empty list at this block. It is a registry rather than the Pool’s truth: a reward the Pool starts paying after the wrapper was deployed has to be registered by a permissionless call before it appears there, so the list can under-report and an empty one is not proof there is nothing to claim.
Look up an address
What one address holds of this vault, read at the block this page names. The address rides in the URL, so the reading is shareable and a link to it is a link to that same reading.
What these figures are
Every one of them is a call answered by a contract at block 25,922,389 — no indexer, no stored table, and no history: this page reads state. Amounts are quantities of the token named beside them and nothing is priced in USD, so two figures in two different tokens are never ordered against each other. A configuration read says what a setting IS at this block, never what it will be.
Shares are fungible and the vault pooled the deposits before anything was done with them, so two addresses holding equal shares carry equal figures here whatever they deposited and whenever. An address with a computed stake is not an identified person unless it carries a name of its own.