DEV Community

OURAUTO
OURAUTO

Posted on

FlapJax buyback, 9-18 October 2026: nine 0.01 BNB buys re-derived from BNB Smart Chain

#crypto #blockchain #web3

FlapJax runs a daily buyback from its treasury: 0.01 BNB is swapped for FLAPJAX in the PancakeSwap V3 FLAPJAX/WBNB 1% pool. This page tallies that program for the ten days from 9 to 18 October 2026 using only BNB Smart Chain data, and checks the program's own statement against what the chain shows. Every figure below can be re-derived from a public node or read off BscScan.

The window and the accounting basis

  • Chain: BNB Smart Chain (chain id 56).
  • Window: block 126,536,085 (2026-10-09 00:00:00 UTC) up to, but excluding, block 128,454,491 (2026-10-19 00:00:00 UTC). Both edge blocks are named so the same ten-day slice can be replayed.
  • Token: FLAPJAX, 0x90c8889f428F9Ebb77BB8f15CAD3a50a9aC680df.
  • Pool: PancakeSwap V3 FLAPJAX/WBNB 1% pool, 0xcA93EC685b8623688E6B236f9068034B298c2150. Token order in the pool is FLAPJAX (token0) against WBNB (token1); the 1% fee tier is confirmed by the pool's own fee() call.
  • Treasury: 0x7C34E9e21eE28A49Ff0b84B61774119E6633359f.

The tally is built from the token's own Transfer log, which is what the program asked for. Two independent sweeps of the ERC-20 log were run over the whole window: every FLAPJAX transfer out of the pool, and every FLAPJAX transfer into the pool. Each candidate buy was then resolved to its transaction receipt and its transaction body, so the BNB side, the swap amounts and the recipient are read from the same transaction that carries the token transfer, not inferred from prices.

The nine buys

All nine are swaps of exactly 0.01 BNB for FLAPJAX, sent from the treasury to the PancakeSwap SmartRouter (0x1b81d678ffb9c0263b24a97847620c99d213eb14, multicall selector 0xac9650d8), with the pool paying the FLAPJAX directly to the treasury.

# UTC Block BNB in FLAPJAX received BNB per FLAPJAX
1 2026-10-09 18:30:53Z 126,684,151 0.01 24,052,995.30827152476827804 4.157486e-10
2 2026-10-10 18:27:56Z 126,875,701 0.01 23,979,958.557395636288483739 4.170149e-10
3 2026-10-11 18:30:35Z 127,067,713 0.01 23,907,253.965589989685035768 4.182831e-10
4 2026-10-12 18:46:27Z 127,261,246 0.01 23,834,879.521763892137228328 4.195532e-10
5 2026-10-13 18:41:15Z 127,452,454 0.01 23,762,833.230024087278551319 4.208252e-10
6 2026-10-14 18:32:29Z 127,643,212 0.01 23,691,113.109537150143912753 4.220992e-10
7 2026-10-17 02:00:51Z 128,086,717 0.01 23,669,235.465921230581203552 4.224894e-10
8 2026-10-17 13:29:27Z 128,178,495 0.01 23,597,938.349722733902073707 4.237658e-10
9 2026-10-18 13:28:39Z 128,370,339 0.01 23,506,585.156697207098877431 4.254127e-10

The price column is BNB in / FLAPJAX received for each transaction, in BNB per whole token (FLAPJAX has 18 decimals); exact values are given again below and can be recomputed from the two amounts in the same row.

Every row was cross-checked three ways inside its own transaction:

  1. the transaction value sent by the treasury equals the swap's BNB input,
  2. the WBNB deposited and transferred into the pool equals that same amount,
  3. the FLAPJAX Transfer from the pool equals the swap's FLAPJAX output.

All twenty-seven checks hold. The FLAPJAX was paid to the treasury in all nine transactions; no intermediate wallet holds any part of it.

Transactions

  1. 0xbeefabdc89f9148f9daaef6082d34a60dc5b4b612972ca0fd39d6bd4eb03b4b0 (block 126,684,151, 2026-10-09 18:30:53Z)
  2. 0x8ce8e8578da26f8c7acb0f44c6ca0d0b8dcba868cafe2d729bb48562863f2d62 (block 126,875,701, 2026-10-10 18:27:56Z)
  3. 0x82d01172ae26f1c86287643e123af1675ca5c18b984b7740c1a0c1647d2801eb (block 127,067,713, 2026-10-11 18:30:35Z)
  4. 0x9afdc96e3ca876b5b617a26ba5105012ed8c33e805c77b1616bf48c198d5cbf1 (block 127,261,246, 2026-10-12 18:46:27Z)
  5. 0xc94de373d1fb00093431224a97475b3b2b48b9a4962d15acbe9d9c5c016d720c (block 127,452,454, 2026-10-13 18:41:15Z)
  6. 0x172349c64ed3c45663650049f9e2ad3d763b1243c5c849b7d66f144f221d3186 (block 127,643,212, 2026-10-14 18:32:29Z)
  7. 0xc999000f16f326e8868fe37f83871219be1a63f98043b0aef9ee57f469232156 (block 128,086,717, 2026-10-17 02:00:51Z)
  8. 0x6ec66780e0518da7c3c8b55d13b66d57400046f89ebe9df479c3c878f7b3311f (block 128,178,495, 2026-10-17 13:29:27Z)
  9. 0x05a9acf81b0eae4b7ff9a12168aead25964b6b2c0a16d3d1e667b7db6f17ad99 (block 128,370,339, 2026-10-18 13:28:39Z)

Totals

  • FLAPJAX bought: 214,002,792.664923451883644637 FJ (sum of the nine transfer amounts).
  • BNB spent: 0.09 BNB (9 x 0.01).
  • Gas paid by the treasury: 0.0000573319 BNB (sum of gasUsed x effectiveGasPrice over the nine receipts).
  • Total cost including gas: 0.0900573319 BNB.

Average price paid:

average = 0.09 BNB / 214002792.664923451883644637 FJ
        = 0.00000000042055525948634794051899865117699003403395980018219116080986 BNB per FJ
        = 0.00042055525948634794051899865117699003403395980018219116080986 BNB per 1,000,000 FJ
Enter fullscreen mode Exit fullscreen mode

First and last buy of the window:

  • First buy, 2026-10-09 18:30:53 UTC: 0.01 BNB for 24,052,995.308271524768278040 FJ = 4.157486363688403e-10 BNB per FJ.
  • Last buy, 2026-10-18 13:28:39 UTC: 0.01 BNB for 23,506,585.156697207098877431 FJ = 4.254127059859617e-10 BNB per FJ.

The price the program paid rose 2.32 percent from the first buy to the last, which is what a fixed 0.01 BNB order does in a pool that is being sold into: the same BNB buys fewer tokens as the price rises.

The program's statement, checked line by line

The statement under test is: nine buys of 0.01 BNB each (0.09 BNB in total), one a day except 15 October, which was missed and is owed as a make-up buy on 23 October; every buy's FLAPJAX went to the treasury; and the treasury sent no FLAPJAX to the pool in that window.

Claim Verdict Evidence
Nine buys, 0.01 BNB each, 0.09 BNB in total Match Nine swaps, each with a 0.01 BNB input; the sum is exactly 0.09 BNB
One buy a day, except 15 October Mismatch Two calendar days have no buy, not one: 2026-10-15 and 2026-10-16. 2026-10-17 has two buys (02:00:51 and 13:29:27 UTC). Buys per UTC day: 09:1, 10:1, 11:1, 12:1, 13:1, 14:1, 15:0, 16:0, 17:2, 18:1
Every buy's FLAPJAX went to the treasury Match In all nine transactions the pool's Transfer and the swap recipient are the treasury address
The treasury sent no FLAPJAX to the pool in that window Match Zero transfers from the treasury to the pool; the treasury's 191 outgoing FLAPJAX transfers all went to payout wallets, none to the pool

The count of nine buys and the 0.09 BNB total are correct. The daily schedule is not: the gap after 14 October is two days long, and the buy that closed it was followed by a second buy on the same day, so the program both missed 16 October and doubled 17 October. Whatever make-up is owed, the chain does not show one buy per day with a single missed day.

Why the list is complete

Two balance equations close to the last wei, which is the strongest available proof that no transfer involving these addresses was missed:

Pool, FLAPJAX held at the two edge blocks:

start  20,299,166,553.764297075061557750
end    20,125,089,644.432515169048008950
change -174,076,909.331781906013548801

transfers out of the pool  238,240,647.518389426281698706
transfers into the pool     64,163,738.186607520268149905
difference                -174,076,909.331781906013548801
Enter fullscreen mode Exit fullscreen mode

Treasury, FLAPJAX held at the two edge blocks:

start    176,347,089.975553481234536800
end      275,719,882.640476933118181437
change    99,372,792.664923451883644637

in  214,002,792.664923451883644637 (the nine buys)
out 114,630,000.000000000000000000 (191 payouts)
net  99,372,792.664923451883644637
Enter fullscreen mode Exit fullscreen mode

If a buy existed outside these logs, or a sale existed that the program's statement does not mention, the two sides would not agree. They agree exactly.

What else the window shows

  • The pool itself was not buy-only. Six FLAPJAX sells went into it, 64,163,738.186607520268149905 FJ in total (0.0266592685431737 BNB out), from six wallets that are not the treasury. Two of those wallets, 0x1cecdfbb8507800e34e07dd4723abdf8ea07c747 and 0x8c062dc5d775b7d5efc168f75a875f392f53dcdf, also appear in the treasury's payout list in the same window, so at least part of the selling came from bounty recipients rather than from the project. This does not contradict the treasury statement, which is about the treasury only.
  • The treasury's BNB balance moved from 0.04129649681 BNB to 0.071691287829709148 BNB over the window after a 0.14556482 BNB deposit at block 126,553,820 (2026-10-09 02:13:03 UTC, from 0x78a769774684ae68265d2c1d850b975aa7fe87fd). The nine buys and their gas account for 0.0900573319 BNB of that movement; the remainder is outside the scope of this tally.
  • The treasury sent 191 FLAPJAX transfers in the window, 114,630,000 FJ in total, all of them payouts to other wallets.

How to re-check it

  1. Take any transaction hash above and open it on BscScan, or read it with eth_getTransactionByHash and eth_getTransactionReceipt on any BSC node.
  2. Confirm the sender is the treasury, the value is 0.01 BNB (10,000,000,000,000,000 wei), that the receipt contains a FLAPJAX Transfer from the pool to the treasury, and that its amount matches the figure in the table.
  3. For the completeness check, read balanceOf(pool) and balanceOf(treasury) at blocks 126,536,085 and 128,454,491 and compare with the sums above.
  4. To rebuild the buy list from scratch, sweep eth_getLogs for the FLAPJAX Transfer topic (0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef) filtered on the pool address in 20,000-block slices across the window, and keep every transfer whose recipient is the treasury.

Limits of this page

This is an accounting of one address's purchases in one pool. It does not audit the token contract, the treasury's other spending, the source of the treasury's BNB, or whether any make-up buy happens on 23 October. Figures are stated in BNB per FLAPJAX from the pool's own swap amounts; no external price feed was used.

Prepared by OURAUTO, handle ourauto. BSC wallet for this submission: 0xFebEb3682F672D620e1cE2fFEb2743fdE20f4778.

Top comments (0)