Pinchu whitepaper v1.0 — deployed rules

0Status of this paper

The rules below are deployed. Where this paper and the verified source disagree, the source wins. It says plainly what is not running.

What exists and what does not
Part	State	Meaning
PINCHU token and Mint	Deployed	BSC addresses on the status page. Sourcify exact match for creation and runtime bytecode.
Minting	Status loading	Read live. Deployed paused; the admin unpauses it once the website and wallet path pass checks. The page never assumes it is open.
PINCHU / BNCB pair	Created	Address fixed at token deployment; no liquidity and no trading until the pool opens (section 5).
Website and wallet minting	Working	Live count from the chain; each player approves and mints through their own wallet, never through the project’s wallet.
Task review, boards, points	Not running	No task can be claimed; no ranks or levels are computed.
Audit	None	No audit has been done. None is claimed.

Any address presented as the PINCHU contract that is not on the status page is not ours.

1Summary

Pinchu is a meme token with a fair-mint launch on BNB Smart Chain (chain ID 56). Holders of an Agent ID buy shares with BNCB. Each share mints PINCHU to the buyer and splits the payment: 80% to the pool, 20% to the treasury.

4,440,000 shares across 353 price tiers, from 0.25 BNCB to 2.0175 BNCB per share.
The first 10,000 shares pay 0.25 BNCB and get 50,000,000 PINCHU each. The mint that includes share 10,000 opens the PINCHU / BNCB pool in the same transaction.
After that, each share's PINCHU follows the pool's reserves.
Maximum supply is 444,000,000,000,000 PINCHU. It is a ceiling, not a pre-mint: tokens only exist once shares are bought.
No team allocation. No hidden pre-mint.

Pinchu has no AI service, no game, no dividends and no points token. Holding PINCHU gives no claim on BNCB, on the treasury or on anything else.

2PINCHU and BNCB

Two tokens are involved, and they are easy to mix up.

PINCHU: The token this project issues. ERC-20 on BSC, 18 decimals: 0xd0De40260B5ae1Ddc694AFF9Fafdfbd9E3FB0840. Only the Mint contract can create it.
BNCB: An existing outside token, used here only to pay for mints and to pair the pool. Contract on BSC: 0x4902c5ebc598265ed2212b559b042de8a5eeec3f, as given in Binance's original announcement^[7].
BNB: Pays gas. It is not accepted as mint payment.

What BNCB is, and is not

BNCB is a tokenized, securities-linked asset. On-chain it reads name CEA Industries, symbol BNCB, 18 decimals, display multiplier 1. It is not a stablecoin. Its own price moves, so a PINCHU price in BNCB can move against dollars even when nothing changes in the pool.

BNCB sits behind an upgradeable proxy. Its issuer can upgrade it, pause it, blacklist addresses and change its display multiplier. Any of these could stop or change minting. BNCB's issuer and Binance have no relationship with Pinchu and do not endorse it.

How BNCB amounts are handled

Prices are kept in raw integer units. One opening share is 250000000000000000 raw, shown as 0.25 BNCB at today's multiplier of 1.
On every mint the contract checks that BNCB still has 18 decimals and display multiplier 1, and that BNCB's pause manager does not report it paused. If the multiplier changes, the mint is rejected outright; it never silently changes the raw amount charged.
The contract credits what it actually received (balance before and after), not the requested amount. If BNCB ever starts taking a fee on transfer, the mint must not hand out tokens for BNCB that did not arrive.
Payment path for version 1: approve BNCB, then mint. BNB or USDT have to be swapped to BNCB first, outside Pinchu.

3Agent ID and allowance

Minting needs an Agent ID. The contract looks up the ID through the registrar's handleOf and checks that the caller owns it. Allowances are counted per ID, not per wallet. Any wallet can connect, but without an ID it cannot mint.

Allowance per Agent ID
Source	Shares	Rule
Base	10	Every Agent ID.
Invite	+1	When an ID you invited makes its first paid mint. Only that first paid mint counts. A self-invite, the same ID or a referrer without an Agent ID gives no credit; the mint still goes through and the chance is used up.
Follow on X	+1	Once per ID per task, after the review service checks it and signs an approval. One social account counts for one ID only.
Post on X	+1
Join Telegram	+1

One mint buys 1 to 10 whole shares.
Allowance is the number of shares an ID may still buy. It is not tokens you hold, and it is never paid out as cash or free tokens.
Extra allowance adds to the remaining amount; shares already minted stay counted.
Before the pool opens, ordinary PINCHU transfers are off. After it opens, anyone can trade on the pool with no Agent ID. The ID limit applies to minting, not to holding or trading.

Task approvals. A separate review signer signs typed data (EIP-712^[3]) holding the user's address, the task, a hash of the social account and a deadline. The signing domain carries the chain ID and the mint contract address, so an approval cannot be used on another chain or contract. There is no nonce field: the contract refuses a second claim of the same task by the same Agent ID, and a social account already bound to a different ID. EIP-712 does not give replay protection by itself; these checks do. The review signer is a key for the review service only; it holds no funds and no admin rights. The contract verifies that signature against one fixed signer address with a plain ECDSA check; it does not accept contract-wallet (ERC-1271) signatures for the signer. The review service is not running yet, so task buttons stay closed.

4The 353-tier ladder

The share count is shared by everyone. Its position sets the price of the next share. Shares 1–10,000 form one tier at 0.25 BNCB; after that the price rises in steps of 1,000, then 10,000, then 20,000 shares.

Price bands and rule totals
Shares	Tiers	Step	BNCB / share	Band total, BNCB
1–10,000	T1	10,000	0.25	2,500
10,001–20,000	T2–T11	1,000	0.275 → 0.5	3,875
20,001–100,000	T12–T91	1,000	0.525 → 0.92	57,800
100,001–1,000,000	T92–T181	10,000	0.925 → 1.37	1,032,750
1,000,001–4,440,000	T182–T353	20,000	1.375 → 2.0175	5,835,100

Prices are built from integer units of 0.0025 BNCB, rounded per tier before scaling, so no tier carries floating-point drift. The full table is on the Mechanism page.

Crossing a step

A mint that crosses a step pays each share at its own tier. With 9,999 shares minted, 10 more cost:

1 × 0.25 + 9 × 0.275 = 2.725 BNCB

If other mints land first, your shares fall further along the ladder and cost what those tiers cost. The mint takes a max cost, so it fails instead of overcharging.

Rule total, not a forecast

If all 4,440,000 shares were sold, payments would add up to 6,932,025 BNCB: 5,545,620 to the pool and 1,386,405 to the treasury. This is the sum of the table. It is not a raise target or an expectation. The supply cap may stop minting earlier (section 7), and fewer shares may sell.

5Opening the pool

The PINCHU / BNCB pair address is fixed when the token is deployed: the token's constructor gets or creates the canonical pair from the PancakeSwap v2 factory. Until opening, that pair has no Pinchu liquidity and trading is closed.

Before opening, each 0.25 BNCB share is split 0.20 to be paired and 0.05 to the treasury. The mint contract holds the 0.20 and sets aside 40,000,000 PINCHU for the pool alongside the buyer's 50,000,000.

The mint that includes share 10,000 adds that liquidity to the existing pair, sends the LP to the dead address and opens trading, all in the same transaction. In the normal case, with nothing extra sent to the pair:

Pool opening at share 10,000
BNCB collected	2,500	10,000 × 0.25
Into the pool	2,000 BNCB + 400,000,000,000 PINCHU	80% and 40M per share
To the treasury	500 BNCB	20%
To minters	500,000,000,000 PINCHU	50M per share
Supply after opening	900,000,000,000 PINCHU	Minters plus pool
Opening ratio	0.000000005 BNCB / PINCHU	50M PINCHU for 0.25 BNCB

The opening ratio is the spot ratio at that block. It is not a price anyone can sell a large amount at.

Anyone can send BNCB straight to the pair before opening. Such a donation stays in the pool: it is not counted as a mint payment and nothing of it goes to the treasury. It changes the real opening ratio, so the table above shows the case without donations.

The LP tokens this project mints when it adds liquidity go straight to the dead address. That covers this project's LP only. Anyone else can add liquidity, and the exchange can mint protocol-fee LP, so it is not true that all LP in the pool is locked.

The pool is on PancakeSwap v2^[1]. The contracts move funds through the pair directly (transfer, then the pair's own mint, swap or sync); the router is not on the payment path and is listed only as an outside reference for traders. The pair orders its tokens by address, so the contract must not assume PINCHU or BNCB is token0, and it must not reuse paths built for USDT or WBNB. The pair exists on BSC at 0xD11f1e705281e8f8233C8Fd84840818ec3E13069; the opening itself has been tested on a fork of BSC, not yet on mainnet.

Before opening, unsynced BNCB sent to the pair can be taken by anyone through the pair's public skim; Pinchu adds no withdrawal right of its own. Opening uses the donation actually present at that moment.

Opening early

The admin (dev) address may open the pool at any count from 1 to 9,999 shares, and the contract emits an event when it does. It works the same way as the normal opening, with the BNCB and PINCHU set aside so far. The default target stays 10,000. If it is used, opening-tier shares still get 50,000,000 PINCHU each, and the PINCHU paired after that follows the live pool reserves instead of a fixed 40M. The treasury multisig does not hold this right.

No refund. If 10,000 shares are never reached, the design has no refund path. Opening early is an operating choice by the admin, not a refund right for minters.

6Minting after 10,000

From share 10,001, PINCHU for each share is minted at the pool's ratio, divided by 0.99:

PINCHU per share = share cost × PINCHU in pool ÷ BNCB in pool ÷ 0.99

80% of the payment is paired with newly minted PINCHU at the pool's current ratio and added to the pool; 20% goes to the treasury. Both legs move the reserves, so each later share gets a slightly different amount.

Example, right after opening (400,000,000,000 PINCHU and 2,000 BNCB in the pool), share 10,001 at 0.275 BNCB:

0.275 × 400,000,000,000 ÷ 2,000 ÷ 0.99 ≈ 55,555,556 PINCHU

The 0.99 divisor means the mint gives slightly more PINCHU than the spot ratio at that block. It is not a guaranteed 1% profit: selling pays the 2% sell tax and the pool fee, moves the price, and the pool may have moved before you sell. Nothing here is redeemable for BNCB.

Every mint takes three limits that the contract checks: max cost in BNCB, minimum PINCHU out, and a deadline. If any is missed, the whole mint reverts. The site's estimate alone protects nothing.

7Supply limits

Two ceilings. Whichever is reached first stops minting.

4,440,000 shares.
444,000,000,000,000 PINCHU (444T) maximum supply, 18 decimals.

444T is a cap on what may ever be minted. None of it is minted in advance. Supply grows only as shares are bought: to minters and to the pool.

After the opening, the PINCHU per share depends on the pool, so the token cap may be hit before all 4,440,000 shares are sold. When a mint would push supply past 444T, the whole mint is rejected. It is never filled in part, and the site must not show a failed mint as partly done.

Tokens sent to the dead address still count in the ERC-20 totalSupply^[2]. Burning to dead does not lower supply and does not make room for more minting.

8Pool upkeep

The design keeps a reference line in BNCB:

line = mint principal paid × 50,000,000 ÷ 27,727,060

“Mint principal paid” is the Mint's totalPaid: BNCB paid for shares only. Donations sent to the pair and BNCB from swapped tax are not in it.

The ratio 50,000,000 ÷ 27,727,060 is carried over from the original plan as a fixed constant. It is not derived from the money collected, and it is not a guarantee or a cash reserve.

When circulating PINCHU × the pool's spot price falls below the line, a new mint moves part of the pool's PINCHU to the dead address and syncs the pool, which raises the spot price. The amount removed is bounded twice: the removal on its own may lift the spot price by at most 0.8% from the price at the start of that mint, and the removal never targets below 11,666,666,667 PINCHU in the pool. That is a limit on the removal only, not a guaranteed pool minimum: an early opening below 292 shares starts with less, and trades can take reserves lower. The 0.8% resets every transaction, so ten 1-share mints and one 10-share mint can end differently.

The 0.8% applies to this removal only. It is not a cap or a promise on how far the price moves in a transaction or a block: the mint's own liquidity, other people's swaps, tax swaps and donations all move the price too.

It runs only during a mint. No mints, no upkeep.
It spends no BNCB. It is not a buyback.
It is not a floor price and nobody can redeem at the line.
An upper value can be read for display. There is no automatic action at the top.

9Taxes

Taxes on PINCHU movements
Movement	Tax	Where it goes
Buy from the pool	1%	Mint contract balance, swapped to BNCB for the treasury
Sell to the pool	2%	1% dead address, 1% mint contract balance
Wallet to wallet	0%	Still subject to the pool and receiver rules in section 10

There is no separate tax contract. Tax in PINCHU goes straight to the mint contract, which swaps it to BNCB through the pair and sends the BNCB to the treasury. The swap is limited (in the design, at most once per block and at most 0.1% of the pool's PINCHU each time) to limit price impact. The pool's own swap fee is separate and is not part of these numbers.

Not all PINCHU held by the mint contract is tax. Before opening it also holds the PINCHU set aside for the pool (section 5).

10Controls

Not every control can be given up, and this paper does not claim it will be. The roles are fixed in the deployed contracts and cannot be rotated. Both are existing addresses, not Pinchu contracts:

Admin (dev): Deploys the contracts and holds the retained admin calls below. 0x424858Acf751A30481Ba4387AC2d1550c68901C9
Treasury: An existing Safe multisig^[5]. It receives the 20% share of payments and the BNCB from swapped tax; its owners sign any spending from it. It is not an admin and does not approve individual mints. Public reads show 3 owners and a threshold of 2; this paper does not vouch for who controls those owners. 0xF588d2efBCdc533C0f1834E43732d5dB3bF17EE1

Retained controls
Control	Who	What it does
Mint pause	Admin	Stops minting. Does not touch balances or the pool.
Receiver rules	Admin	Non-whitelisted contracts and other pools can be refused as receivers, so PINCHU trades on the one pool.
Early opening	Admin	Opens the pool at 1–9,999 shares (section 5). Emits an event.
Renounce	Admin	Gives up the admin calls above. If minting is paused at that moment, renouncing unpauses it, and receiver blocks the admin set stop taking effect. It does not remove the fixed review signer or the limits written into the contract (the fixed manager/vault receiver rules and the automatic block on other pairs stay), so renouncing does not mean nobody has any control left.
Treasury spending	Treasury Safe	Moves BNCB out of the treasury. 2 of 3 owner signatures.

A third fixed key, the review signer 0x085fAf14Fe310bFfa11E0Ae58Db487BC4F01BFb8, can only sign task allowances (section 3); it holds no funds and its service is not running. The Mint was deployed paused; the header of every page shows the live state. Three outside addresses (the PancakeSwap v2 and Smart routers and Binance Wallet's Permit2) are protected from receiver blocking; they get no tax exemption or spending right. The verified source shows which library code is used^[6].

Outside Pinchu's control: BNCB's issuer can pause, blacklist or upgrade BNCB (section 2), which could block minting or trading regardless of these settings.

11Price tiers and activity

The production Tiers view shows the 353 fixed prices against confirmed shared progress, verified connected-player quota and balances, and actual Mint events. It does not generate personal points, scores, cards or ranks. Personal reward levels and social tasks are not enabled.

Binance Agentic Wallet login uses an independent server session for each player. Transactions are limited to a finite BNCB approval to the Mint and the deployed Mint call. Each requires a parsed preview and explicit player confirmation; unknown outcomes are retained and never automatically resubmitted.

12Implementation

Token and Mint, written to this paper. Done
Local tests on the production bytecode and a run against real BNCB and PancakeSwap on a fork of BSC. Done
Deployment on BSC, Sourcify exact-match verification, addresses on the status page. Done
Read-only data service (count, quote, wallet allowance) and wallet minting on this site. Wired
Unpausing the Mint, after checks of the website and wallet path. Status loading
Task review service, boards and points. Not built

What has not been shown on mainnet yet

A player's real approve and mint, and the normal opening at share 10,000. Forked-chain runs are evidence, not a mainnet result.
Tax swaps against real trading volume.
Any audit.

13Risks

Unaudited new code. The contracts are deployed and source-verified, but nobody has audited them, and no player has minted on mainnet yet.
Outside services. The data service and its public RPC can fail; the site then stops offering to mint rather than show old numbers. Your wallet and BscScan remain the final check.
BNCB. Its price moves, and its issuer can pause, blacklist, upgrade or rescale it.
Pool price. A meme token pool can fall fast. The opening ratio, the 0.99 divisor and the upkeep line are not floors.
No refund. If minting stops early or the pool opens late, there is no way back to BNCB except selling.
Controls. The admin can pause minting, set receiver rules and open the pool early (section 10). Some control remains even after renouncing.
Fakes. Only the addresses on the status page are Pinchu. Approve BNCB only to the Mint 0x22A7…9BA8.

Nothing in this paper is investment advice.

14Open decisions

Not yet decided
Item	Current position
Board settlement	00:00 UTC daily from a fixed confirmed block, proposed; ties and reorgs to be defined.
Renouncing admin	Not done. If done, it ends pause, early opening and receiver changes; fixed rules and the review signer remain.
Opening the mint	Only by unpausing on-chain. No date is promised here; the live status is the answer.

15References

Technical background. A reference here does not mean Pinchu uses that code or has any relationship with its authors.

PancakeSwap v2 — Addresseshttps://developer.pancakeswap.finance/contracts/v2/addressesOfficial BSC factory and router. The factory created the pair; the Mint uses the pair directly.
Sourcify — PinchuMint on BSChttps://repo.sourcify.dev/56/0x22A716ab76627CB24667D1298A9bFA70868a9BA8Exact-match verified source. The Token is at the same service under its own address.
EIP-20: Token Standardhttps://eips.ethereum.org/EIPS/eip-20approve, transfer and totalSupply behaviour.
EIP-712: Typed structured data hashing and signinghttps://eips.ethereum.org/EIPS/eip-712Format for task approvals; replay protection comes from the signed fields.
ERC-1271: Standard Signature Validation Method for Contractshttps://eips.ethereum.org/EIPS/eip-1271Signatures from contract wallets.
Safe Docs — Glossaryhttps://docs.safe.global/home/glossaryOwners and threshold, as used by the existing treasury Safe. Pinchu did not create it and claims no audit of its owners.
OpenZeppelin Contracts 5.x — Utilitieshttps://docs.openzeppelin.com/contracts/5.x/api/utilsBackground on common security utilities. No integration claimed.
Binance — original BNCB announcementhttps://www.binance.com/en/support/announcement/detail/d625f87897a843febc1f4c139740d875Source for the BNCB contract address. No endorsement of Pinchu.

v1.0 · deployed rules · 2026-10-30 UTC Next: how to use Pinchu