Supply verification for $BRIAN on Base, for CoinMarketCap, CoinGecko and any
other listing desk.
- Contract:
0x3ecced5b416e58664f04a39dd18935eb71d33b15 - Symbol:
BRIAN - Chain: Base (chain id
8453)
https://x-auto-post-service-production.up.railway.app/api/supply/brian
It works the number out from the chain on every request — total supply minus every burn address — so it cannot go stale, and nobody has to remember to update it. It also shows its working: each excluded address, its balance, its reason, the block everything was read at, and the method, so anyone can re-derive the figure with a block explorer and take nothing here on trust.
Numeric-only endpoints, in the format CoinMarketCap asks for — the whole body is one plain number and nothing else:
| Circulating | …/api/supply/brian/circulating |
| Total | …/api/supply/brian/total |
If it cannot read the chain it answers 503 with a word, never a number. A supply figure that can't be proven right now is one that must not be served — an endpoint that guesses is worse than one that admits it is down.
circulating_supply.txt, total_supply.txt and supply.json mirror the live
endpoint. They exist so that anything already pointed at these raw URLs keeps
reading a true number. The live endpoint is authoritative; prefer it for
anything new.
They are currently refreshed by hand, which is the flaw that caused the
problem described below, so treat their updated_at as the real freshness of
this file and the live endpoint as the real freshness of the number.
An automated six-hourly refresh is written, validated and waiting in
automation/ — see that folder for the one step needed to turn
it on. It is parked outside .github/workflows/ because the credential used
here lacks the workflow scope GitHub requires to write there.
These files used to be edited by hand. They were correct the day they were written — the method was right and the decimals matched to the last digit — and then the chain moved and the file did not. By 2026-08-27 they were 14 tokens wrong, and the repo had been archived, so they could not be corrected at all.
Fourteen tokens out of 972 million is a rounding error. That is not the point. The point is that the error only grows, silently, in a number published to listing desks as fact. Another token was burned during the afternoon this was fixed.
circulating = totalSupply() − balance of every burn address
$BRIAN's ownership is renounced and the contract has no mint function, so total supply is fixed at 1,000,000,000 and can only fall through burns. There is no team allocation, no vesting and no locked address, so nothing else is excluded.
The only excluded addresses are the two nobody holds a key to:
| Address | Why |
|---|---|
0x000000000000000000000000000000000000dEaD |
Burned |
0x0000000000000000000000000000000000000000 |
Burned |