sGhosGho
Savings GHO, deployed by Aave · 0xe175…ca1d · asset GHO
Aave publishes this address in its own address book as GhoEthereum.SGHO.
Read at block 25,922,119 · every figure below is a call answered at that block, on this vault and on the contracts it names.
What the vault's stored yield index says its shares are worth — not the GHO it holds.
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^18 — this vault's own decimals.
How savings GHO works
One vault over GHO, one hop. A holder’s shares grow with a stored yield index rather than with a balance the vault receives, which is why totalAssets() above is not the GHO the contract holds: that figure is the index applied to the whole share supply, and the balance is a separate reading. Withdrawals are clamped to the balance. The rate the index grows at is a setting the risk council writes, and the vault accepts deposits up to a cap it also sets. The vault is not paused at this block.
The rate the risk council has set, in the units the contract stores it in. Not a return, and not annualised here.
The ceiling the risk council has set on what this vault will hold.
The vault's own maxDeposit() — the cap less what totalAssets() already counts.
The token balance at the vault's address. This is what withdrawals are clamped to.
Two reads at one block, stated rather than reconciled. It can fall either way and nothing here asserts an order.
A timestamp the contract stores, not this block's own — it is when the vault was last touched.
The two slots the conversions run on, as the contract stores them, both RAY-scaled (1027): the yield index 1013313383644845626345108242 and the rate per second 1426940639269406392. convertToAssets(shares) is shares times the index over one RAY, and the index is grown by the rate and rewritten on every mint, burn and transfer. Neither number is compounded out to a period here.
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,119 — 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.