How Unmask knows what it knows.
Everything Unmask prints is read from public chains. This page says what it treats as known, what it does not, and how a figure tells you which.
Who owns what
Most figures are per owner, so joining two wallets by mistake would make every one of them wrong. Unmask joins wallets only on what the chain shows them doing, never on statistics, and says how sure it is.
| Grade | When | In the figures |
|---|---|---|
| Certain | The same key on both chains, or a bridge crossing paired exactly by its own message and a sign of ownership on the far side. | Joined, and counted in every figure |
| Almost certain | One wallet sent the other a large amount in total (below), or a wallet that cannot sell wL1 itself has a recipient that wrapped its L1: the recipient acts for it. | Joined, and counted in every figure |
| Likely same owner | A large send to a fresh wallet that then staked, wrapped or sold it, where the send alone does not join them. | Shown with its evidence, never counted |
| Associated | L1 that went both ways between two wallets, repeatedly. Unmask does not join them: it may be the same owner, a partner, a fund they manage or an OTC deal. | Shown with its evidence; the L1 it holds printed apart as Associated (not owned), never counted |
Unmask joins two wallets as the same owner when one sent the other 1,000 L1 or more in total (on GenesisL1 or as wL1 on Base), because on GenesisL1 nobody sends that much to a stranger; never through a contract, pool, bridge, router or module, never a collector (4+ senders) or a distributor (1,000+ L1 to 4+ wallets); each joined wallet shows the send that joined it on its profile.
A crossing of the bridge alone never joins two wallets, and neither does a match of amount and time.
Owned, and associated
Owned. Certain is what the chain proves: the same key on two chains, or a bridge crossing paired exactly by its own message with a sign of ownership on the far side. Almost certain is what the wallets themselves did that nobody does with a stranger's wallet, such as the large send above. An owner's wallets are those and only those: what an owner holds, its place among holders, its tags and the count of owners read them alone.
Associated (not owned). Associated wallets moved L1 both ways with an owner's wallets, repeatedly and on several days: a strong two-way relationship, and nothing on the chain says whose they are. It includes "likely same owner" wallets (one large send to a wallet the sender funded) as well as two-way relationships. Unmask does not join them: it may be the same owner, a partner, a fund they manage or an OTC deal. The L1 they hold is printed apart, as Associated (not owned), on the owner's Holders row and profile, and Unmask never adds it to the owner's total. Not owned: in no total, ranking, tag or count of owners. A wallet associated with several owners counts in each owner's figure separately, and is never added across owners.
A wallet managed for a fund or an institution. A wallet someone manages for others, for a fund, a company or an institution, is not theirs: the L1 in it belongs to the people behind it. On the chain, managing a wallet looks like any other close relationship, L1 going out and coming back, and nothing says whose money it is. Adding it to the manager's total would put other people's L1 under one person's name, so it shows as associated, beside the owner, and never in the owner's figures.
Only what the chain shows. Unmask joins wallets only on what the chain shows them doing, never on what anyone tells it. A claim, a label or a message, from a wallet's holder or from anyone else, joins no wallet to another.
Not a tax statement. Owned, associated, cost and Result describe what the chain shows, by the rules on this page. They are not a statement of what anyone owns or owes for tax, accounting or any legal purpose, and none of them stands in for one.
Module accounts are not owners
A module account is an account the chain itself runs: the staking pools, the community pool, the fee collector, governance deposits and the like, and the escrows of its IBC channels. The chain lists them, and no private key exists for them, so nobody can sign for one and nobody decides what it does.
That is why none is an owner: an owner is someone who can act. Counting one would add somebody who does not exist, and put L1 under one name that is often many people's, as the staked L1 in the staking pool is its delegators'. The Holders tab shows them as a group of their own, and they are in no owner count, share, whale tag, cost figure or alert.
Every figure has a state
A number with no age cannot be trusted, so each one on the site carries one of three marks: a shape and a word, never a colour alone.
Current to the latest block Unmask has read. It says which block, or when it was read.
The last good reading, with its age and the reason the new one failed. A figure that could not be refreshed is never passed off as new.
No good reading at all, with the reason. Never shown as zero: a zero on Unmask is a zero on the chain.
Where it comes from
All of it is public, and read from the chains themselves. Nothing is entered by hand, and no figure comes from anyone else's summary of the chain.
Public GenesisL1 nodes: balances, staking, transfers, validators, and the chain's past state from its public archive.
Public Base nodes: the wL1/USDC pool, its positions, wL1 transfers and the bridge's half on Base.
Public Osmosis nodes: L1 traded and held there.
It checks itself every night
Reading block by block is fast, and a fast reading can miss something. So every night the figures kept up to date block by block are compared against full scans of the chain, and the site's main figures against the chain at the height each was read. A difference is investigated, not averaged away.
What it does not claim
Profit is stated over what has a known cost, and "not indexed" is never "no cost". What followed past events describes the past; it does not predict the next case. Unmask describes what happened. It never recommends anything.
Unmask, by FirstBlock