Security

Proof of reserves

The treasury holds recipients’ money until they claim it. The proof page compares what the treasury holds on chain with what our ledger says it owes, at the moment you load it. This page explains the comparison and is plain about its limits.

The check

What /proof computes

treasury = SOL balance of the treasury address, read from Solana now
owed     = every credit ever made to recipients
         − payouts confirmed on chain
         − recipient burn orders whose buy has landed
surplus  = treasury − owed
solvent  = surplus ≥ 0

A payout in the queue, a payout in flight and a burn order still waiting for its buy all count as owed. A payout is in flight from the moment it is signed and sent until the chain confirms it: it may still expire without landing, and then the same amount is owed again on the payout that replaces it, so it stays owed until it is confirmed. The platform’s own money is not in owed: it is part of the surplus, and the page shows the platform’s available balance next to it so you can see how much of the surplus is ours.

Figure	Source
Treasury balance	Solana, at request time. Anyone can read the same number on Solscan
Owed	Our ledger, in one database snapshot
Queued payouts, payouts in flight, pending burns	Our ledger. Already inside owed, shown on their own for clarity
Platform available	Our platform ledger: shares in, fees, rent, buybacks and confirmed withdrawals out

What it proves

At the moment of the check, the treasury holds at least what the ledger says recipients are owed. If it did not, solvent would be false and the surplus negative, and the page would show both.
The treasury address is real and public. Its balance is not our claim; it is read from the chain and you can read it yourself.
The platform has not paid itself out of recipients’ money. Platform withdrawals come out of the surplus, and one that reached into what is owed would turn it negative. The console refuses such a withdrawal; the check shows whether anything got past it.

What it does not prove

Stated plainly

The treasury is a hot key we operate. The proof shows that the money is there now. It cannot show that it will be there in an hour, and nothing on chain stops the holder of that key from moving it. No proof of reserves can prove that its operator will not steal. It can only make a theft visible within minutes.

It trusts the ledger’s side. owed comes from our database. You can audit it rather than trust it: every credit comes from a sweep with a public signature, and every sweep’s amount is in pump.fun’s events on chain. See Sweeps.
It is a snapshot. It says nothing about the moment before or after it was taken.
It does not cover the vaults. Fees not yet swept are in pump.fun’s vaults or in a token’s creator address, not in the treasury, and are not owed to anyone until a sweep credits them.
It does not cover key compromise. If the treasury key leaked, whoever held it could empty the treasury. The proof would show it; it would not prevent it.

Checking it yourself

Take the treasury address from Addresses or from the proof page, and read its balance on Solscan.
Read owedLamports from GET /api/proof, or rebuild it from GET /api/ledger: sweep totals minus their platform shares, minus payouts with status confirmed, minus burns with source recipient. A buy that is between its swap and its burn can make the two differ for a minute.
Spot-check sweeps on Solscan: each signature shows the collect events and the balance of the token’s own creator address, which together make the amount the ledger credited, and the transfer into the treasury.

curl and jq

curl -s https://slicepad.fun/api/proof \
  | jq '{treasury, treasuryLamports, owedLamports, surplusLamports, solvent}'

The live page is /proof. The endpoint is documented on GET /api/proof.