RailsPreview
Vaults · Ethereum · Find your position

Finding a MetaMask position on Ethereum

All vaults on Ethereum

What MetaMask’s own pages say about where the shares are held, where the app shows an address, and what the app calls a vault — and what the chain record on Ethereum shows beside it.

Is the position personal, or pooled with everyone else's?

Personal, and held at the account’s own address. MetaMask describes a smart account as its own basic account pointed at a MetaMask contract, and states that this happens “without migrating your funds or changing your address”; the account is still governed by the same secret recovery phrase and keys it was before.

That is what EIP-7702 does: an externally owned account keeps its address and its keys, and gains the code of the contract it points at. So the holder of the shares is the customer’s own account, not a MetaMask address holding many customers’ shares with the split kept off chain — and a reading of that address on this site is a reading of one holder.

The contract those accounts point at is published by MetaMask itself, twice: its help page names the delegator contract by address, with a link to that address on Etherscan, and its delegation framework carries the chain-1 deployment record for the same address. That publication is what ties the address below to MetaMask — the same source can be redeployed by anyone, so a verified contract name on its own would identify the code and not the app.

Stated by MetaMask:MetaMask Help Center — What is a smart account?MetaMask Help Center — Switch to or revert from a smart accountMetaMask — delegation-framework, the chain-1 deployment record for this delegate

Where does the app show an address?

At the ordinary place, because the address does not change. MetaMask states that switching an account to a smart account leaves the address as it was and moves no funds, and that the switch is made per network from the account’s own details — so the address holding the shares on Ethereum is the address the account already had.

MetaMask documents where that address is shown: in the extension the account’s Ethereum address sits under the account dropdown and is copied by clicking it, and on mobile the copy icon on the home screen opens the account’s addresses to choose from.

No page cited here says the app links out to a block explorer for this position, and nothing is claimed about one.

Stated by MetaMask:MetaMask Help Center — How to copy your account public addressMetaMask Help Center — Switch to or revert from a smart account

What the app calls the vault, and what the chain calls it

The MetaMask pages cited here are about the account, not about any particular vault, and none of them names one. Whatever a vault is called in an app is that app’s own label for it.

The vaults in this directory are the ones Aave deploys and publishes on Ethereum, and the roster is answered by Aave’s own enumerators rather than swept from logs. A name still does not identify a vault — a share token’s name is a string its contract returns — and the address settles it. The vault this guide’s chain figure is about is named, addressed and linked below.

Stated by MetaMask:MetaMask Help Center — What is a smart account?

What the chain record shows

An account of its own, not a pooled address, by the pages above. On chain, the evidence this guide rests on is the delegate contract those accounts' own code names — one contract the block explorer verifies under the name EIP7702StatelessDeleGator. Under EIP-7702 a holder like that is an externally owned account with 23 bytes of code — the indicator 0xef0100 followed by the delegate — so the address in the record is the account's own, and the delegation is a fact about the block it was read at.

163 holders of Umbrella Stake Wrapped Aave Ethereum USDC v1 (0x6bf1…8aa6) carry code naming the verified EIP7702StatelessDeleGator delegate at block 25,920,356. That is a count of accounts and a fact about the wallet software they run, not a count of people and not a statement about who they are. Both the census and the code reads are on Ethereum, at that block, and a delegation set there can be cleared in any later one.

Find your position

An address’s share of every ERC-4626 vault Aave deploys and publishes on Ethereum — the whole roster Aave's own enumerators answer, at the block the reading is taken — one balanceOf on each. The result is read at one block and the address rides in the URL, so the reading is shareable. A reader who has only a transaction — the Etherscan link a wallet app shows beside a deposit — can enter that instead: the holder address is found in the transaction’s own vault Transfer events. A vault address in this catalogue opens that vault’s own page instead of a holder reading.

Sources