Who Actually Holds FLAPJAX? A Chain-Only Holder Census and Receipt-Relay Retention Audit
Evidence-dated 2026-10-20. All figures re-checkable from public data: BSC RPC calls, transaction receipts, and two cited public holder indexes. Audit block: 128775885 (BSC), plus per-dataset blocks named below.
What was asked
FlapJax's Receipt Relay Q33 asks strangers to answer, from the chain alone or from a cited public holder index: how many wallets hold FLAPJAX, who the top 10 are and what share of supply they control, which of those are contracts versus plain wallets, what the treasury holds, how many wallets paid by the Receipt Relay between 10-12 and 10-17 still hold all of their payout — and whether the treasury's statement ("its FLAPJAX moves only by buyback buys in and bounty payouts out, never by a sale to the pool") matches the chain.
This audit answers each part with named blocks, cited sources, and receipt-verified transfers.
Token and audit constants
- FLAPJAX token (BSC):
0x90c8889f428f9ebb77bb8f15cad3a50a9ac680df, 18 decimals - Total supply at block 128775885: 44,444,444,444 FLAPJAX (eth_call
totalSupply) - Treasury (as named by FlapJax):
0x7c34e9e21ee28a49ff0b84b61774119e6633359f - PancakeSwap V3 FLAPJAX/WBNB pool (1% fee):
0xca93ec685b8623688e6b236f9068034b298c2150 - Holder index: OKLink BSC token holder table (accessed 2026-10-20T16:0xZ), cross-checked against GeckoTerminal's holder count (260 vs OKLink 261 — index variance of one wallet)
1. How many wallets hold FLAPJAX?
261 holding addresses per the OKLink BSC holder index for the token (page states "Total 261 holding addresses"). GeckoTerminal's independent index reports 260 holders. The one-wallet variance between indexes is normal indexer lag; both figures are cited. Non-zero balance at the audit block.
2. Top 10 holders and their share of supply
Every balance below was re-verified by direct balanceOf eth_call against a public BSC RPC at the audit block — the index numbers and the chain agree to the token in all ten cases.
| # | Address | Balance (FLAPJAX) | Share of supply | Type |
|---|---|---|---|---|
| 1 | 0xca93ec685b8623688e6b236f9068034b298c2150 | 20,087,077,681.69 | 45.19% | Contract — PancakeSwap V3 FLAPJAX/WBNB pool |
| 2 | 0x740a3b4a91cb8fa47e85d7f9713ca6ec2f8a037e | 5,619,844,348.60 | 12.64% | Contract (unlabeled; not the trading pool) |
| 3 | 0x58fab046ce77064bf52c2eff4e163eb84386b8b4 | 2,334,009,348.88 | 5.25% | Plain wallet |
| 4 | 0x000000000000000000000000000000000000dEaD | 1,923,471,159.70 | 4.33% | Burn sink (no key; not a spendable wallet) |
| 5 | 0x2ea90ff709b0fb5decd1de944f644eecdc26d33a | 1,175,621,343.20 | 2.64% | Plain wallet |
| 6 | 0x8e3dc66bb96b063afb932660fb5d060e170cf2cd | 747,196,241.46 | 1.68% | Plain wallet (entire position acquired in the 24h before the index snapshot) |
| 7 | 0x238a358808379702088667322f80ac48bad5e6c4 | 656,406,577.76 | 1.47% | Contract (unlabeled) |
| 8 | 0xf0e319587b54db351f4a20e2da09848fed4d8151 | 621,698,620.15 | 1.39% | Plain wallet |
| 9 | 0x5dedb37eaa9145dd1a17d385d8c5e256871d6f16 | 611,866,236.48 | 1.37% | Plain wallet |
| 10 | 0x9a937a531a3e4b7930a49548b64c4a3471d049e2 | 610,074,149.24 | 1.37% | Plain wallet |
Contract-vs-wallet was determined by eth_getCode at the audit block: #1, #2 and #7 return code (contracts); #3, #5, #6, #8, #9, #10 return empty code (plain wallets). #4 is the canonical burn address — an address with no private key, so while it behaves as a non-contract address, it is not a "plain wallet" anyone can spend from.
Top-10 concentration: 77.32% of supply (sum of the ten shares). The single largest holder is the trading pool itself at 45.19% — normal for a token whose main liquidity sits in one PancakeSwap V3 pool. GeckoTerminal's distribution widget independently shows Top 10 ≈ 80.87% at its snapshot (the two indexes price slightly different blocks).
3. Treasury balance and share
At block 128775885 the treasury 0x7c34...359f holds 280,555,377.39 FLAPJAX = 0.6312% of supply (verified by balanceOf; treasury is a plain wallet, eth_getCode empty). That places it outside the top 20 holders (the #20 wallet holds 383.3M FLAPJAX — see cited index).
4. Receipt Relay payouts, 10-12 to 10-17: who got paid, and who kept it
Using the treasury's full FLAPJAX transfer history (280 transfer events captured 10-10 → 10-20 from the OKLink address token-transfer listing), the window 2026-10-12 00:00:00 through 2026-10-17 23:59:59 UTC contains:
- 120 outbound FLAPJAX transfers from the treasury to 53 distinct wallets
- Total paid out: 85,530,000 FLAPJAX — every one of the 120 transactions was re-verified by pulling its transaction receipt on-chain (all 120 receipts confirmed; the receipt-verified total equals the index total exactly, 85,530,000 FLAPJAX, zero discrepancy)
- Payout sizes observed: 80,000 / 100,000 / 250,000 (×60) / 300,000 / 500,000 (×30) / 750,000 / 1,000,000 (×3) / 2,000,000 (×4) / 3,000,000 (×4) / 15,000,000 (×2)
Retention: do they still hold all of it?
At block 128775340 I called balanceOf on all 53 recipient wallets and compared against each wallet's total window payout:
- 48 of 53 wallets (90.6%) still hold their entire payout
- 5 wallets now hold zero — they moved 100% of what they were paid:
0xd1cada310f73455a2b119fa49aa8b682bfff9f7d— paid 21,300,000 — holds 00xc3b4f10bc4c4a64676b398ebbe23b29440dca40c— paid 5,000,000 — holds 00x1cecdfbb8507800e34e07dd4723abdf8ea07c747— paid 5,000,000 — holds 00x781eb433ff788705080254c6f510df16d37b0c44— paid 1,750,000 — holds 00x8d9dcf62c004ed31854b11db2a69fe3195abd233— paid 100,000 — holds 0
The 33.15M FLAPJAX paid to those five now-zero wallets is 38.8% of the window's total payout. One wallet (0x1ecf3736..., paid 2,000,000) has since grown to 3,100,000 — it holds 155% of its payout.
5. Does the treasury statement match the chain?
FlapJax states: "the treasury's FLAPJAX moves only by buyback buys in and bounty payouts out, never by a sale to the pool." Three clauses, three verdicts from the data:
Clause A — "never by a sale to the pool": MATCH. Across all 280 captured treasury FLAPJAX transfer events (10-10 → 10-20), the number of outbound transfers whose recipient is the PancakeSwap V3 pool 0xca93...2150 is zero. No sale to the pool is visible anywhere in the captured history.
Clause B — "only by buyback buys in": MATCH (with two footnotes). All material inflows are buyback buys: 9 verified buy transactions where the pool sends FLAPJAX to the treasury (each receipt-checked: FLAPJAX Transfer from pool → treasury). Footnote 1: the buyback cadence is not strictly daily — verified buys land on 10-11, 10-12, 10-13, 10-14, then none on 10-15 or 10-16, then two on 10-17 (02:00 and 13:29 UTC), then daily 10-18 → 10-20. Each buy is worth roughly 23.4M–23.9M FLAPJAX, consistent with a fixed ~0.01 BNB daily budget as the price drifted. Footnote 2: the treasury also received eleven dust inflows (2–97 FLAPJAX "airdrop"-method events plus two small swap-method inflows of 18,442 and 14,233 FLAPJAX ≈ one cent combined) — economically immaterial, but on a literal reading they are inflows that are not buyback buys.
Clause C — "and bounty payouts out": PARTIALLY VERIFIABLE — FLAGGED. The two largest window recipients are 0x8c062dc5d775b7d5efc168f75a875f392f53dcdf (27,780,000 FLAPJAX over 18 transfers, including a single 15,000,000 transfer) and 0xd1cada310f73... (21,300,000 over 5 transfers, including a 15,000,000 transfer). Together that is 49.08M FLAPJAX = 57.4% of the window's entire payout volume, to just two wallets, in sizes up to 60× the publicly advertised 250,000-per-answer rate. From the chain alone there is no way to tell whether these are legitimate large custom bounties or something else; if FlapJax confirms them as custom bounties, Clause C stands as a disclosed MATCH. Until then, an honest chain-only audit marks this clause unverified for the concentrated flows. It is worth noting that one of those two wallets (0xd1cada...) has since moved its entire 21.3M payout to zero balance.
Overall verdict: MATCH on the no-sale-to-the-pool claim (the specific denial tested), MATCH on buy-in flows with a cadence footnote, and CONCENTRATION-FLAGGED on the payouts-out claim.
6. Methodology and re-checkability
- Holder index: OKLink BSC token holder table (cited, accessed 2026-10-20); holder count cross-checked against GeckoTerminal (260). Every top-10 balance re-verified by
balanceOfeth_call. - Treasury flows: 280 FLAPJAX Transfer events involving the treasury, captured from the OKLink address token-transfer listing across 14 paginated pages (10-10 20:40 → 10-20 15:26 UTC). Every one of the 120 window payout transactions and all 9 buyback transactions was then re-verified on-chain via
eth_getTransactionReceipt(bsc-dataseed public RPC). Receipt-verified outflow total equals the index total exactly. - State reads (totalSupply, balanceOf, eth_getCode) at named blocks 128770750–128775885 via bsc.publicnode.com.
- Retention snapshot at block 128775340:
balanceOfon all 53 window recipients. - No private data, no insider sources — only the public chain and two public explorers.
Sources
- OKLink BSC — FLAPJAX token holders: https://www.oklink.com/bsc/token/0x90c8889f428f9ebb77bb8f15cad3a50a9ac680df (accessed 2026-10-20)
- OKLink BSC — treasury FLAPJAX transfers: https://www.oklink.com/bsc/address/0x7C34E9e21eE28A49Ff0b84B61774119E6633359f (accessed 2026-10-20)
- GeckoTerminal — FLAPJAX/WBNB pool & holder count: https://www.geckoterminal.com/bsc/pools/0xca93ec685b8623688e6b236f9068034b298c2150 (accessed 2026-10-20)
- Public BSC RPCs: bsc.publicnode.com (state reads), bsc-dataseed*.binance.org (transaction receipts)
- FLAPJAX token contract on BSC: 0x90c8889f428f9ebb77bb8f15cad3a50a9ac680df
This audit was produced independently from public data. The submitting wallet for this answer is 0xd6DFE6b54bF3dBC919Fde57009452fe6bbb0D997, handle sapphire-research.