A number that can explain itself: MADGER’s live supply endpoint

MADGER now publishes a machine-readable circulating-supply endpoint at its canonical domain. When every verification step succeeds, the endpoint returns one deliberately small JSON object:

{"circulatingSupply":224999994.992743}

The useful part is not the formatting. It is the chain of evidence behind the number. The endpoint reads finalized Solana state, checks the identity of five documented Jupiter Lock token accounts, performs the calculation in integer base units, and rereads supply before responding. Its complete source and behavioral tests are public.

This is shipped verification infrastructure, not a claim that a listing provider has accepted the value. MADGER’s current Jupiter metadata update remains pending and cannot be amended while it is under review. Other services make independent decisions about whether, when, and how they use submitted supply data.

The reader benefit: one number, three ways to challenge it

You do not have to trust a screenshot or a ticker label. You can inspect the live response, read the exact code that produced it, and reproduce the last dated calculation from the underlying accounts.

1. Use it. Open madgercoin.com/api/circulating-supply. A successful response contains only the numeric circulatingSupply field.
2. Audit it. Read the production calculation, including every account identity and every condition that can stop publication.
3. Reproduce it. Compare the October 6 evidence record with the mint and five escrow token accounts on an independent explorer.

The exact official Solana mint is BHauMX8akk2umqkQqnJwpYkCRkZmefGnEBFByeFXRKqv. Match the entire address before using any supply figure. A copied ticker or logo can point to a different asset.

Reproduce the October 6 snapshot

The dated evidence record used finalized commitment and six-decimal integer amounts. It did not remove balances from ordinary unlocked project wallets and did not estimate whether unlocked holders were actively selling.

The equation is:

999,999,994.992711 − 774,999,999.999968 = 224,999,994.992743 MADGER.

The calculation runs in base units first: 999999994992711 − 774999999999968 = 224999994992743. Dividing by one million happens only after subtraction. That avoids silently rounding large token values before the answer is known.

The latest automated mint report, generated October 8, still records total supply of 999,999,994.992711 MADGER, six decimals, the classic SPL Token program, initialization, and revoked mint and freeze authorities. Those checks describe the mint; they do not establish demand, liquidity, price stability, or custody safety.

What happens on every successful request

A short response can hide a weak method. This endpoint is intentionally more demanding than “read one balance and subtract a hard-coded number.”

1. Read total supply at finalized commitment. The endpoint asks Solana for the official mint’s current supply and records the response slot.
2. Require six decimals. An unexpected decimal count stops the request instead of producing a mis-scaled number.
3. Read all five escrow token accounts together. The request uses the first supply read’s slot as a minimum, preventing an older account snapshot from being mixed into a newer supply snapshot.
4. Verify every identity. Each account must belong to the classic SPL Token program, hold the exact MADGER mint, have the documented Jupiter Lock owner, and report six decimals.
5. Sum integer balances. Only the five publicly documented escrow token accounts are excluded.
6. Read supply again. If supply changed while the escrow accounts were being read, the endpoint retries the complete sequence once.
7. Check the result’s bounds. The answer cannot be negative or greater than total supply.

This does not make the endpoint an oracle or an audit firm. It makes the assumptions visible and machine-checkable.

Why a refusal can be the most trustworthy answer

If the Solana RPC fails, returns incomplete data, reports a mismatched account identity, changes supply during both attempts, or produces an invalid result, the endpoint returns HTTP 503 with {"error":"Supply temporarily unavailable"}. It does not reuse an old successful number and present it as current.

The Worker can use a private RPC binding when one is configured and otherwise relies on a public mainnet RPC. Solana’s cluster documentation warns that shared endpoints are rate-limited and have no uptime guarantee. That external limitation is another reason the API exposes a temporary failure instead of silently serving stale state.

The endpoint also contains a scheduled safety boundary. The earliest documented cliff begins on March 12, 2027 at 08:30 UTC. From that moment, a token can remain inside an escrow account while becoming withdrawable. Account balance alone would no longer prove every token is locked. The current code therefore stops serving the calculation at that cliff until the vesting logic and evidence method are reviewed.

Temporary unavailability is inconvenient. Publishing a number after the method stops proving it would be worse. “Fail closed” means uncertainty becomes visible instead of being converted into false precision.

Maximum circulating is not the same as active float

The endpoint uses maximum circulating supply because it excludes only tokens that the documented locks prevent from circulating at the observation time. It does not claim every remaining token is trading, liquid, for sale, or controlled by unrelated parties.

Four terms should stay separate:

• Total supply is the current quantity recorded by the mint.
• Provably locked supply is the balance excluded under the documented lock evidence and current time boundary.
• Maximum circulating supply is total supply minus that provably locked amount.
• Active market float is a looser market concept and cannot be proven merely by reading token-account balances.

A service may use a different definition, evidence policy, or review schedule. That difference should be named rather than hidden behind the same label.

A five-minute independent audit

1. Open the live endpoint and record the HTTP status and response.
2. Open the official mint on Solscan and match all 44 characters.
3. Open the Jupiter Lock directory and compare it with MADGER’s five-account evidence record.
4. Read the timestamped inputs, including each token account, owner, amount, and observed slot.
5. Inspect the source and confirm that its mint and five account pairs match the evidence.
6. Run or read the tests, which cover a successful calculation, an escrow-owner mismatch, RPC failure, and the first-cliff shutdown.

If the live endpoint returns 503, do not substitute a cached screenshot and call it current. Use the dated evidence for historical reproduction, then wait for a successful fresh response or investigate the failing source.

The listing-provider boundary

This endpoint was shaped for a future circulating-supply submission, but deployment is not acceptance. MADGER cannot state that Jupiter, CoinMarketCap, Birdeye, DEXTools, or another provider has adopted the value unless that provider’s public surface or direct response confirms it.

The same boundary applies to MADGER’s replacement X account. The official directory now identifies @MadgerDaBadger, while the dated correction log separates submitted requests from confirmed provider changes. A correction request is work performed; it is not proof that every third-party profile has changed.

What this release proves—and what it does not

It proves that MADGER has deployed a public, source-visible method for computing maximum circulating supply from finalized mint data and five identified lock accounts. It proves that the method has automated tests and explicit stop conditions. The dated evidence lets another reader reproduce the current baseline without taking a market ticker on faith.

It does not guarantee that the API, Solana RPC, Cloudflare, an explorer, or a listing provider will always be available. It does not guarantee token price, liquidity, future lock balances, holder behavior, project execution, or investment returns. It does not convert a maximum-circulating calculation into a promise about active float.

If you are new to Solana, keep technical verification separate from purchase execution. The beginner buying guide remains the dedicated path for wallet setup, SOL network fees, mint matching, slippage, and transaction risk. The Burrow Commons remains available without a wallet or token purchase.

The signal

A trustworthy number should arrive with a method, a timestamp, a failure mode, and a way for someone else to disagree using the same evidence. That is the utility of this endpoint: not “believe our supply,” but “open the process that calculates it.”