Square — docs

01Overview

A deployer launches a token on Flap and sets its creator-fee beneficiary to the Square treasury, permanently. The token's description names a Binance Square handle. From then on, everything is mechanical: fees accrue as the token trades, Square claims them on a schedule, converts them to the payout asset the deployer chose, and credits them to the handle inside the escrow contract. The creator proves the handle is theirs and claims to any wallet.

The recipient does nothing in advance. There is no account to make and no wallet to connect until the moment they want the money. They can also refuse it; see the section on stopping payments.

A token directs its fees

At launch, its Flap beneficiary is the Square treasury. Only the current beneficiary can move it, so once it's Square's, it stays.

The description names a handle

One line: Fees to @handle via Square. That's who the fees are for.

The token registers itself

The claimer sees the beneficiary and the line on chain. No approval step, no queue.

Fees are claimed and credited

On a schedule, Square claims from Flap, converts to BNB or USDT, and deposits into the escrow under the handle's hash. Each step is a transaction.

The creator claims

They post a one-time code from their Square account, name a wallet, and the escrow pays that wallet. Square signs the authorization but cannot redirect it.

02Directing fees

Square works with tokens launched on Flap (BNB Chain). The fee direction is set at creation, as the token's beneficiary. Flap lets only the current beneficiary hand it on, so the assignment is its own lock: the deployer cannot take it back afterwards.

Two rules hold. It has to be the whole fee, because a partial share would mean the published payout is a fraction of what the token earned with no way for the recipient to tell which. And it has to be permanent, because a direction that can still be changed is a promise that can still be withdrawn.

Venue: Flap, BNB Chain. Live.
When: At creation, as the beneficiary.
Token type: Flap tax tokens (address ending 7777). The sell tax is what funds the payout; 100% of it goes to the beneficiary.
Made permanent by: The assignment itself. Only Square can move it.

Directing a token's creator fees to the Square treasury is the deployer's own transaction and decision. Square is the fee rail, not the issuer of the token.

03Naming the recipient

The handle that gets paid is read from the token's description. Put this line in it, with the handle you want paid:

Fees to @yourhandle via Square

Add in USDT at the end to be paid in USDT instead of BNB. Write whatever else you like around it: the line is what we read. The wording matters because a description can mention several accounts; "Fees to" and "via Square" bracket the handle so only one reading is possible. If the line is missing, the token does not register.

Handles are stored on chain only as a hash of the lowercase name. The recipient does not need to agree, know in advance, or hold a wallet.

04The split

100%

To the recipient

Square protocol cut

Every claim is credited in full to the handle. Square keeps nothing from creator fees. What Square does keep: balances of handles that asked not to be paid (see stopping payments). Gas for claiming and converting is paid by the treasury and is not deducted from the recipient.

05How claims work

Creator fees don't arrive continuously. They accrue at Flap as the token trades and sit there until Square claims them, which happens on a schedule rather than every trade; claiming per trade would cost more in gas than it collects on a quiet token. Claims below a small threshold wait for the next cycle.

Each claim is one transaction from the treasury to Flap, and each credit is one Deposited event on the escrow keyed by the handle's hash. If the fee arrived in a different asset than the payout, the conversion is its own transaction in between. A claim can fail (chains halt, RPCs drop); a failed claim creates no credit and is retried, and the fees stay at Flap in the meantime.

06Getting your fees

If a token named your handle, the money is credited to you as it's claimed. To collect it:

Look up your handle

On the claim page. It shows what's held for you, per asset.

Prove it's yours

Enter the wallet you want paid to, get a short code, and post it from your Square account. Once confirmed, the handle is linked to that wallet.

Claim

Connect that wallet and send the claim. The escrow pays it directly. The authorization Square signs names your wallet, so it can't be redirected, and it's single use.

Receiving a payment does not make you a customer of Square or a promoter of the token that named you. Money you receive may be taxable to you; Square doesn't issue tax documents and nothing here is tax advice.

08Verifying

The verify page reads BNB Chain directly, with no server in between. It shows every credit and claim for any handle, each with its transaction, and the exact eth_getLogs query so you can reproduce it against any RPC. It proves custody inside the escrow. It cannot prove who owns a Square handle; that happens off chain in step 2 above.

09Stopping payments

Send a request from your handle, or with reasonable proof you control it, to the Square operator. Your handle is marked blocked on chain: new credits to it revert, the claimer stops claiming fees of tokens that name it (those fees stay at Flap, unclaimed), and any balance already credited passes to the treasury. Removal is honored within 7 days.

10If a token isn't registering

Wrong beneficiary: Fees point at an address that isn't the Square treasury. Check it against the launch page.
No line: The description doesn't contain Fees to @handle via Square.
Not a tax token: Standard Flap tokens have no tax, so nothing accrues to the beneficiary.
Too recent: The claimer scans on a schedule. A token created minutes ago hasn't been seen yet.
Below threshold: Accrued fees are under the minimum claim size and will be picked up next cycle.

11What you're trusting

Square is not trustless. Be clear about what the operator can and cannot do.

The operator can: decide when to claim and convert (timing and slippage), decide whether a handle is verified, and block a handle. The operator cannot: redirect a claim to a different wallet than the one the recipient verified with (the signature names it), pay the same authorization twice, credit a blocked handle, or hide any of it: every credit, claim and sweep is a public event.

Handle verification is the weakest link. Binance Square has no public API, so ownership is proven by posting a code, confirmed by an operator. Treat a payout as authoritative only after it's on chain.

12Glossary

Creator fees: What Flap pays a token's beneficiary from trading in that token. For Square tokens, the sell tax.
Beneficiary: Flap's field for who receives creator fees. Set at creation; only the current one can move it.
Treasury: The Square wallet that is every registered token's beneficiary, claims fees, and deposits them.
Escrow: The contract that holds credited balances per handle until claimed or expired.
Handle hash: keccak256 of the lowercase handle without @. The only form a handle takes on chain.
Claim: Two meanings: Square claiming fees from Flap, and a creator claiming their balance from the escrow.
Authorization: A signed message from Square's signer naming a handle, an asset, a wallet and a deadline. Unlocks one claim.

How Square works.

00Contents