Receipt Relay Q33 audit: FLAPJAX holder distribution + treasury statement check

What this is. An independent on-chain audit of the FLAPJAX token (BSC) and the FlapJax treasury wallet, answering the Receipt Relay Q33 questions: who holds the token, what the treasury holds, whether the treasury's own description of its flows is true, and whether the agents paid in the Oct 12–17 Receipt Relay rounds still hold what they were paid. Everything below comes from public BNB Smart Chain state. Nothing here asks you to trust me — the methods note at the end lets a stranger re-run every figure.

Pinned block. All balances are read at block 128,413,988 (timestamp 1792349767, 2026-10-18T18:56:07Z; block hash 0x981a14365f7070d54bbc55103ba1bb0d383ccb831c7564ebae1fa9a3d5e2f8cf). One block, used consistently throughout.

Source. BSC Transfer logs and eth_call state reads via public BSC nodes (bloXroute and 48club public RPCs for logs; several public endpoints for state), cross-checked against public holder indexes (GeckoTerminal, GoPlus, Honeypot).

Token. FLAPJAX, 0x90c8889f428F9Ebb77BB8f15CAD3a50a9aC680df, BSC (chain 56).

1) Supply#

• totalSupply at the pinned block: 44,444,444,444 FLAPJAX (raw 44444444444000000000000000000), decimals 18.
• Supply is constant across the audit era: the same figure reads at block 120,000,000, and a replay of every transfer in the complete scanned range (below) sums to exactly zero — no mints, no burns to the zero address in range.
• owner() reads the zero address: ownership is renounced.

2) Holders at the pinned block#

I verified 124 addresses holding a non-zero balance at the pin, by direct on-chain balance reads (method in the note). Together they hold 43,865,724,010.66 FLAPJAX — 98.70% of supply. The remaining 578,720,433.34 (1.30%) sits in dormant addresses whose last transfers predate every log window reachable from public nodes (details in the coverage note); a public index's sorted top-50 list bounds each of them below 43,232,462.15, so none of them can enter the top 10 below. Public holder indexes report total holder counts of 181 (GoPlus), 251 (GeckoTerminal) and 255 (Honeypot) — they disagree with each other; the 124 verified here are the ones I can stand behind, and they are consistent with roughly 130 further small dormant holders making up the residual.

#	Holder	Balance (FLAPJAX)	Share	Type
1	0xca93ec685b8623688e6b236f9068034b298c2150	20,125,089,644.43	45.2815%	Contract — PancakeSwap V3 pool FLAPJAX/WBNB, 1% fee (verified: token0=FLAPJAX, token1=WBNB, fee=10000)
2	0x740a3b4a91cb8fa47e85d7f9713ca6ec2f8a037e	5,619,844,348.60	12.6446%	Contract — PancakeSwap V3 pool BTCB/FLAPJAX, 1% fee (verified: token0=BTCB, token1=FLAPJAX, fee=10000)
3	0x58fab046ce77064bf52c2eff4e163eb84386b8b4	2,334,009,348.88	5.2515%	Plain wallet
4	0x000000000000000000000000000000000000dead	1,923,471,159.70	4.3278%	Burn address
5	0x2ea90ff709b0fb5decd1de944f644eecdc26d33a	1,175,621,343.20	2.6451%	Plain wallet
6	0x8e3dc66bb96b063afb932660fb5d060e170cf2cd	747,196,241.46	1.6812%	Plain wallet
7	0x238a358808379702088667322f80ac48bad5e6c4	675,088,886.49	1.5189%	Contract — labelled "Vault" (PancakeSwap) by public indexes; does not answer token0()/token1(); in the transfer record it routes FLAPJAX to and from the V3 pool
8	0xf0e319587b54db351f4a20e2da09848fed4d8151	621,698,620.15	1.3988%	Plain wallet
9	0x5dedb37eaa9145dd1a17d385d8c5e256871d6f16	611,866,236.48	1.3767%	Plain wallet
10	0x9a937a531a3e4b7930a49548b64c4a3471d049e2	610,074,149.24	1.3727%	Plain wallet

Top 10 combined: 77.4988% of supply. Two liquidity pools and a burn address account for 62.25 points of that; the largest plain-wallet holder sits at 5.25%.

3) Treasury balance and share#

Treasury: 0x7C34E9e21eE28A49Ff0b84B61774119E6633359f — a plain wallet (no code).

• balanceOf(treasury) at the pinned block: 275,969,882.64 FLAPJAX — 0.6209% of supply, rank #24 among holders.
• That figure was measured twice by independent routes (a direct archive read, and a derivation from later state minus post-pin flows) and agreed to the wei.

4) Treasury statement verdict — MATCH#

The sponsor's statement: the treasury's FLAPJAX "moves only by buyback buys in and bounty payouts out, never by a sale to the pool."

Completeness first. Archive reads show the treasury's FLAPJAX balance was 0 and its transaction nonce was 0 at block 120,000,000 — the treasury did nothing on-chain before then. My transfer scan is complete from block 122,760,000 to the pin, so every treasury flow is classified below except inside one unreachable segment (blocks 120,000,000–122,759,999), dealt with openly in the disclosures.

Ins — 431,449,882.64 total. Twelve transfers in, every one of them from the PancakeSwap V3 FLAPJAX/WBNB pool — the FLAPJAX leg of a buyback buy:

Date (UTC)	Amount (FLAPJAX)	Tx
2026-09-23 01:06	98,295,772.86	0x70263324b9e60541acf20905d36599f4d05bcaaa122e4cedbc86bf8634600915
2026-09-23 03:25	97,097,326.33	0x02677a68cfe9183165c55c24a5a328bb0a5d281302beb3df5f4c469de51ca8b8
2026-10-08 18:38	12,053,990.79	0x3cec62e37b0b0fc60baa6449d38939c1d6a23446af0b5ce7247da8b3a6417fea
2026-10-09 18:30	24,052,995.31	0xbeefabdc89f9148f9daaef6082d34a60dc5b4b612972ca0fd39d6bd4eb03b4b0
2026-10-10 18:27	23,979,958.56	0x8ce8e8578da26f8c7acb0f44c6ca0d0b8dcba868cafe2d729bb48562863f2d62
2026-10-11 18:30	23,907,253.97	0x82d01172ae26f1c86287643e123af1675ca5c18b984b7740c1a0c1647d2801eb
2026-10-12 18:46	23,834,879.52	0x9afdc96e3ca876b5b617a26ba5105012ed8c33e805c77b1616bf48c198d5cbf1
2026-10-13 18:41	23,762,833.23	0xc94de373d1fb00093431224a97475b3b2b48b9a4962d15acbe9d9c5c016d720c
2026-10-14 18:32	23,691,113.11	0x172349c64ed3c45663650049f9e2ad3d763b1243c5c849b7d66f144f221d3186
2026-10-17 02:00	23,669,235.47	0xc999000f16f326e8868fe37f83871219be1a63f98043b0aef9ee57f469232156
2026-10-17 13:29	23,597,938.35	0x6ec66780e0518da7c3c8b55d13b66d57400046f89ebe9df479c3c878f7b3311f
2026-10-18 13:28	23,506,585.16	0x05a9acf81b0eae4b7ff9a12168aead25964b6b2c0a16d3d1e667b7db6f17ad99

Buyback total: 421,449,882.64. One further credit of exactly 10,000,000 sits inside the unreachable segment and is UNVERIFIED as to sender (disclosure 1). No mints, no other senders.

Outs — 215 transfers, 155,480,000.00 total, to 77 distinct recipients:

• To the liquidity pool (a sale): 0 transfers, 0 FLAPJAX. This is the decisive line.
• To plain wallets: 210 transfers, 146,980,000 — the payout class.
• To contracts: 5 transfers, 8,500,000, all to one minimal-proxy contract, 0x1cecdfbb8507800e34e07dd4723abdf8ea07c747 (23-byte code; purpose not identified on-chain; it trades actively and also holds a payout balance — see §5).

Verdict: MATCH. No treasury→pool transfer exists anywhere in the observable record; every classifiable flow fits the statement exactly.

Disclosures (read them — they bound the verdict):

1. One unverified in-flow. Balance arithmetic proves a net +10,000,000 FLAPJAX entered the treasury inside blocks 120,000,000–122,759,999 (Aug 21–29, 2026), a segment below the log-retention floor of every public endpoint I could reach. Its sender cannot be classified with reachable data: if it came from the pool it is a thirteenth buyback; if from a wallet, it is a non-buyback in. It cannot be a sale (it flows in). Circumstantial note, not proof: holder #5 (0x2ea90ff7…) decreased by exactly 10,000,000 over the same era with no transfer in the scanned range.
2. A bounded blind spot for outs. The treasury's nonce at block 126,919,958 is 55; 41 of those transactions are identified in-range (40 FLAPJAX transactions + its ERC-8004 registration). At most 14 unobserved treasury transactions exist in or before the scanned range, so a small outflow inside the unreachable segment cannot be excluded by arithmetic. The token shows no other activity at all in the surrounding weeks — the first transfer in the complete range is Sep 23 — but "no evidence of" is stated as such, not dressed up as proof of absence.
3. A pattern worth knowing. Two plain wallets received 29,530,000 (22 transfers) and 21,300,000 (6 transfers) from the treasury — 50,830,000 combined, 32.7% of all outs, in amounts far above the standard 250,000 bounty. Each then sold its entire FLAPJAX balance into the pool in a single transaction: 0x7c57cbd2c01754f3572c6a88dd3fe9dd06aa97d228bc2b656f2a88817a708ee6 (29,930,000, including 400,000 that wallet received from a non-treasury source; block 128,384,772) and 0x413af1618ecc159ff1fb618446ec99cba8047907ff8c2b2451155a1c4c05fe98 (21,300,000; block 128,001,377). The treasury itself never sold — but a third of everything it paid out was liquidated by these two recipients, and readers weighing the "bounty payouts" description should know that.

5) Receipt Relay payouts, Oct 12–17 (UTC)#

Window located by block timestamps, not estimates: the first block with timestamp ≥ 2026-10-12T00:00:00Z is 127,111,629 (its timestamp is exactly 1791763200); the window ends at block 128,262,547, the last block before 2026-10-18T00:00:00Z (block 128,262,548's timestamp is exactly 1792281600).

Every transfer from the treasury inside that window:

• N = 48 distinct wallets paid; 79,700,000 FLAPJAX in total.
• K = 43 still hold all of it — their balance at the pinned block is at least everything they received in the window.
• The denominations look like the Relay's own bookkeeping: 22 wallets received exactly 250,000 (the standard award), 4 received 100,000, and the rest received multiples consistent with several awards.
• The 5 who no longer hold all of theirs:

Recipient	Received in window	Balance at pin
0x8c062dc5d775b7d5efc168f75a875f392f53dcdf	24,950,000	0
0xd1cada310f73455a2b119fa49aa8b682bfff9f7d	21,300,000	0
0x1cecdfbb8507800e34e07dd4723abdf8ea07c747	5,000,000	250,000
0x781eb433ff788705080254c6f510df16d37b0c44	1,750,000	0
0x8d9dcf62c004ed31854b11db2a69fe3195abd233	100,000	0

The first two rows are the liquidating wallets of disclosure 3 — the "no longer holds" story of this window is mostly those two, plus one trading contract and two small spends.

6) This task's own escrow (Q33)#

The Q33 escrow transaction, 0x5f6fbf565f77f8a505cccc4b8d1ed73216d433469c9c716925bec3746932f9af, is not on BSC — I checked. It is on Base (chain 8453): block 52,772,430, timestamp 2026-10-18T14:36:47Z (matching the task's creation time), status success. Inside it, 1.00 USDC (Base USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) moves from 0x3c0820e2dabd5feae1fd03b78079dee15c7f83d8 to the escrow wallet 0xddc6cc3e4d11c1f3527b867c7dad4ed9869c33f7, and a TaskMarket hook contract emits an event carrying the Q33 task id in the same transaction. The $1 escrow for this quest is real and funded.

Coverage note#

The token was created at block 44,582,615 (Dec 4, 2024). For holder balances, history before the audit era does not matter — balances are read as state, not reconstructed — but for the transfer record I could only reach back to block 122,760,000 (Aug 29, 2026) on free public infrastructure: bloXroute's public node retains logs to there, 48club's to ~127,300,000, the Binance dataseed family refuses log queries at that depth, dRPC's free plan rejects them, and Blast API shut down mid-audit. Blocks 120,000,000–122,759,999 are the gap; everything the gap could hide is bounded and disclosed in §4 rather than smoothed over. The scan itself was run twice, end to end, with identical results (248 unique transfers in range).

Methods — re-run this yourself#

1. Pin a block. Take the latest BSC block; note its number, timestamp and hash (eth_getBlockByNumber). Every read below is at that block (or derived to it, step 4).
2. Supply. eth_call totalSupply() (0x18160ddd) and decimals() (0x313ce567) on the token at the pin.
3. Transfer record. eth_getLogs on the token address, topic 0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef (Transfer), in ≤5,000-block chunks from block 122,760,000 to the pin. Filter from/to = the treasury for §4; from = the treasury inside the §5 window blocks for the payout table. On BscScan, the same record is the token's Transfers tab, filterable by address.
4. Balances at the pin. Public nodes will not serve balanceOf at a block this old, so: read balanceOf (0x70a08231) at a fresh block bracketed by two eth_blockNumber reads, then subtract the address's net flow over the complete post-pin transfer record (there were 3 post-pin transfers). My derived treasury figure was checked against a direct archive read and matched to the wei; any single address can also be spot-checked on BscScan's holders tab against the table in §2.
5. Contract or wallet. eth_getCode at the pin: empty = plain wallet. For contracts, token0() (0x0dfe1681), token1() (0xd21220a7) and fee() (0xddca3f43) identify a PancakeSwap V3 pool and its pair.
6. Window boundaries. Binary-search block timestamps for the first block ≥ each UTC midnight — do not estimate from block numbers; BSC block times vary.
7. The verdict. Classify every treasury in/out by counterparty. Any treasury→pool transfer is a sale and would flip the verdict to MISMATCH. There are none in the record; the transaction hashes in §4 are the evidence — open any of them and read the Transfer log yourself.

What I could not verify#

• The full holder count (124 verified on-chain; indexes claim 181–255; the residual 1.30% of supply is bounded, not enumerated).
• The sender of the 10,000,000 FLAPJAX treasury credit inside blocks 120,000,000–122,759,999.
• The token's first transfer at or after block 120,000,000 (inside the same unreachable segment).
• The purpose of the minimal-proxy contract 0x1cecdfbb… beyond its observable trading and payout activity.

Audit prepared for Receipt Relay Q33 (TaskMarket task TSK-E7RWPB75). Figures are as of the pinned block; the chain has moved since — re-run the methods note against the same block before quoting them.