Read your referral total straight off Base

An earlier primer walked through what a referral link on this site actually is: a wallet address in a URL, handed to the next person's mint. This one is shorter and more hands-on. If someone minted through your link, the contract keeps a running tally for your address, and you can read it yourself without connecting a wallet, trusting the interface, or asking anyone. Here is how, and one honest wrinkle I ran into while checking.

The two views that hold the tally

The contract exposes two read-only functions keyed to an address:

function referrerEarnings(address) view returns (uint256)
function referrerCount(address) view returns (uint256)

The first returns a number of wei credited to that address as referral earnings. The second returns how many mints have been counted toward it. Both are view functions, which means calling them changes nothing and costs nothing. You are asking the chain a question, not sending a transaction, so there is no fee, no signature, and no wallet involved.

Reading it with Cast

If you have Foundry's cast installed, two calls against Base's public RPC do it. Swap in the address you want to check:

cast call 0x069DCA9E0090B5c32Aa1ac73D9a748d7c27E31E5 \
  "referrerEarnings(address)(uint256)" 0xYourAddress \
  --rpc-url https://mainnet.base.org

cast call 0x069DCA9E0090B5c32Aa1ac73D9a748d7c27E31E5 \
  "referrerCount(address)(uint256)" 0xYourAddress \
  --rpc-url https://mainnet.base.org

The first prints a wei figure; divide by 10¹⁸ to read it as ETH. The second prints a plain count. If both come back zero, no mint has been credited to that address yet, which for most addresses is simply the honest state of things.

No Foundry? The same two calls work as raw eth_call requests over JSON-RPC, the way the site itself reads them. The four-byte selectors are 0xeb3ba72f for referrerEarnings and 0x71602692 for referrerCount, each followed by the 32-byte, left-padded address. The reply is a single 32-byte word you read as an integer.

Where the 10% comes in

The interface next to the referral widget names a ten percent share. That figure is not decorative: the contract stores a royalty rate as basis points, and a read-only ROYALTY_BPS() call returns 1000, which is ten percent. The mint price reads back the same way, 0.001 ETH, from MINT_PRICE(). So the arithmetic behind a credited referral is checkable end to end. What I want to avoid is turning that into a promise. Ten percent of nothing is nothing, and whether anyone mints through your link is entirely outside the contract's control.

The wrinkle: a logged referrer is not a credited one

Here is the part that made me slow down. Every mint emits a SecondMinted event, and that event carries the referrer address that was passed into the call. It is tempting to treat that logged referrer as the same thing as the credit ledger. It is not.

The earliest mint on this contract, second 333 holding token 1, recorded a referrer in its event log equal to the buyer's own wallet address (0x818f…1245). A self-referral, in other words. When I then read referrerEarnings and referrerCount for that same address, both came back zero. The log says an address was passed as referrer; the ledger credited it with nothing.

I cannot show you the exact contract rule from the front-end code, so I will not claim to know precisely why. The reasonable reading is that the contract does not pay you for referring yourself, which is a sensible guard and matches what the numbers show. What I can say plainly is the useful lesson: the referrer field in an event is a record of what was submitted, and referrerEarnings is a record of what was actually credited. Those are two different questions, and they can give two different answers. If you want to know what you have earned, read the ledger view, not the log.

Why read it yourself at all

Because it collapses a whole category of doubt. Ordinary referral programs ask you to trust a dashboard that a company controls and can quietly change. Here the tally sits in public contract storage, and the same call the site makes is a call you can make. If your reading and the site's reading ever disagreed, the read-only view is the one to believe, because it is the state, not a rendering of it.

None of this is financial advice or a hint that a link will pay off. Minting costs a real fee on Base, transactions are irreversible, lost keys stay lost, and phishing is a permanent hazard around anything that touches a wallet. A referral share is a share of activity that may never happen. Reading these views, though, costs nothing and asks for nothing, so there is no reason to take the number on faith.

→ How referrals work onchain · Read your second straight off Base · Read the 86,400 cap off the contract