Passport and Leaderboard
The passport is a record of what a wallet has actually done on Monad, rather than what it currently holds.
What Goes Into It
Reading a wallet's whole history on Monad gives:
- which protocols it has interacted with, out of those we can identify;
- how many distinct days it was active;
- how early it arrived;
- what it holds now.
Those become a score, plus badges for the thresholds crossed.
It Is Public
This is the part worth knowing before you create one.
Your address, your score, the protocols you used and your badges go on the leaderboard, which anyone can read without connecting anything. The share card renders the same figures as an image meant to be posted.
All of it is drawn from public on-chain activity, so nothing secret is being revealed. But it is assembled in one place, under your address, and made easy to look up. If you would rather it were not, do not create one, or ask us to remove it.
Creating One
Creating a passport requires connecting a wallet and signing, because building one is expensive and the signature is what proves you are asking about your own address.
Reading someone else's passport requires nothing.
Why History Comes From Etherscan
No Monad RPC keeps more than about eighteen days of history. Building a passport means reading a wallet's whole life on the chain, so that history is read from Etherscan's Monad index instead.
This means the address being looked up is sent to Etherscan. It is a public address and the request comes from our servers rather than your browser, so they see which address was asked about, not who asked. The privacy policy says the same thing in more detail.
Refreshing
A passport can be rebuilt. Rebuilds are incremental: only blocks since the last scan are read, so a refresh costs far less than the first build.