RailsPreview
Vaults · Base · Find your position

Finding a Safe position on Base

All vaults on Base

What Safe'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 shows beside it.

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

Held at the account's own address. Safe describes a Safe as a smart contract wallet, deployed to a blockchain, that requires a minimum number of its owners to approve a transaction before it is sent, and states that it gives “complete self custody over your funds”.

So the holder of the shares is a contract account of its own, not a Safe 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.

How many people stand behind one such account is a different question, and the chain record does not answer it. A Safe is operated by its owners, and a threshold of them signs; Safe documents both as settings of the account, changed from the account's own settings screen. The figure below is a count of accounts for exactly that reason.

The contracts those accounts run are published by Safe itself, as a table of the addresses each released version is deployed at with the chains it is registered for, Base among them. That table is what ties the addresses below to Safe: 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 Safe:Safe Knowledge Base — What is Safe?Safe Knowledge Base — Managing Safe owners and signaturesSafe — safe-deployments, the table naming these singletons on Base

Where does the app show an address?

On the account's own screen, as the address assets are received at. Safe's page on receiving assets says a deposit is sent to the Safe using the Safe address, that the address is copied from the app by clicking the copy icon or scanning the QR code, and that “All you need to receive assets is your smart account address.”

That address is the holder's own — the Safe's — and it is what the lookup at the foot of this page wants.

One caution Safe states itself: the same Safe can be created at the same address on several networks, and it has to be deployed on the network the assets are on. So an address alone does not say which chain a position is on, and the readings here are Base.

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

Stated by Safe:Safe Knowledge Base — How can I receive assets?Safe Knowledge Base — Deploying a multi-chain Safe

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

No Safe page cited here names a vault. The one that comes closest is Safe's page on DeFi lending, which describes an Earn tab in the app and a deposit routed through Kiln, and names assets and a rewards token rather than any vault on chain.

That page also says what a deposit through it returns: shares “issued in the form of a soulbound ERC-20 token — meaning they cannot be transferred to someone else”. A catalogued vault's own share token is an ordinary transferable ERC-20 — which is how the accounts counted below were enumerated at all, out of that token's own Transfer stream. The two are different tokens, and nothing here says which route any one account took.

On chain a name does not identify a vault — two Base vaults can carry the same name, and this directory catalogues one pair that does. The address settles it, and the vault this guide's chain figure is about is named, addressed and linked below.

Stated by Safe:Safe Knowledge Base — DeFi lending in Safe{Wallet}

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 contract those accounts delegate to, at an address the app publishes itself — 4 contracts the app's own deployment table names, each under the name listed beside it. A holder like that is a contract account of its own, and the address in the record is that account's: the contract it delegates to is named in its storage or embedded in its code, and this guide's figure was read from whichever of the two the account keeps it in.

377 holders of Steakhouse Prime USDC (0xbeef…83b2) name one of the singletons listed above at block 50,907,089. 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.

Find your position

An address’s share of every MetaMorpho vault this directory catalogues on Base — 505 of them, as the two factories had deployed them at block 50,900,229 — and what that share attributes to in each Morpho Blue market those vaults supply. 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 Basescan 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 catalog opens that vault’s own page instead of a holder reading.

Sources