Docs

FlowX is a BNB Chain launchpad and creator-fee distribution platform built for meme tokens.

FlowX connects token launches with an automated creator-fee system. When a token is launched through FlowX, its creator fees can be routed through the FlowX treasury and distributed according to the protocol's fee structure.

Each launch can specify an X account as the intended recipient of the creator's share. Once fees are generated, FlowX processes the accumulated balance and distributes the applicable share without requiring the recipient to manually claim creator fees on chain.

The idea is simple: creators launch, fees are processed automatically without the recipient lifting a finger, and every claim and transaction can be verified on-chain.

FlowX does not operate its own launchpad. It integrates with existing launch environments on BNB Chain and handles the creator-fee distribution from there. Tokens are created on the launch environment; FlowX is the fee-routing and distribution layer.

four.meme is the first venue FlowX supports, on BNB Chain.

On four.meme a token is created as a Tax Token (for example in four.meme Free Mode) with its trading tax split configured so that the recipient share is directed to the FlowX treasury. That recipient is locked in at creation and enforced by the four.meme protocol, and the tax is active during the bonding curve and after graduation.

Once a token routes its recipient share to FlowX, the downstream process is the same regardless of venue: fees are collected, processed, divided, and distributed. Additional launch environments or networks may be added in the future.

FlowX uses the launch environment's own fee configuration. On four.meme that means a Tax Token whose recipient share is set to the FlowX treasury: recipientRate = 100 and recipientAddress = the official FlowX treasury. The remaining allocation fields (burn, dividend, liquidity) are set to zero so the whole recipient share reaches FlowX.

A participating token must: be created (or configured) on a supported environment; direct the applicable recipient share to the designated FlowX treasury; provide a valid recipient designation; and satisfy the registration requirements enforced by FlowX.

The recipient address is fixed at creation and cannot later be changed, which is what makes the fee direction permanent. Sending fees to an unrelated address does not register a token with the protocol.

The treasury provides a single accounting point for creator fees. Instead of requiring each recipient to interact with the launch environment's fee system, FlowX handles the collection and distribution process from the treasury.

FlowX needs to know which X account should receive the creator's share. The launch description should contain the designated recipient using the FlowX-recognized format:

Fees to @yourhandle via FlowX

The handle should be the X account intended to receive the payout. Creators can include additional information in their token description, but the recipient declaration should remain clear and unambiguous. If a valid recipient cannot be identified, FlowX may be unable to process the creator allocation until the issue is resolved.

The recipient does not need to hold a crypto wallet, does not need to launch the token, and does not need to manually claim creator fees on chain. They may receive a payment from a token they were not directly involved in launching. Receiving a FlowX payout does not by itself represent an endorsement of the token or its creator.

FlowX uses a fixed allocation for processed creator-fee claims. The recipient receives 80% of the applicable processed creator-fee amount. The remaining 20% is allocated to the FlowX protocol according to the protocol's treasury and token mechanism.

The split is calculated when the claim is processed. There are no additional FlowX fees added on top of the stated allocation unless explicitly disclosed by the protocol.

Example: if a processed claim contains $100 in eligible creator fees, $80 goes to the recipient and $20 to the FlowX protocol allocation. The exact dollar value received can vary depending on the asset conversion and payout process used at the time of settlement.

Creator fees are generated as the token trades and accumulate until FlowX processes them. FlowX does not need to execute a separate transaction for every individual trade; accumulated fees are processed periodically.

Each successful claim is associated with its corresponding blockchain transaction, creating a direct connection between trading activity → accrued fees → on-chain claim → distribution.

Failed claims: blockchain transactions can fail for reasons including network conditions, reverted transactions, RPC issues, or insufficient execution conditions. A failed claim does not create a completed distribution. Where appropriate, FlowX can retry the claim while the underlying fees remain available according to the applicable fee mechanism.

If an eligible token designates your X account as its recipient, FlowX handles the distribution process. There is no requirement for the recipient to manually withdraw creator fees from the token contract.

Your X account is designated; trading activity creates creator fees; FlowX claims and records accumulated fees; the recipient allocation is determined according to the FlowX split; your share is sent through the supported payout mechanism; and FlowX provides the applicable transaction or public confirmation associated with the distribution.

The recipient does not need to promote the token, acknowledge the token, or hold a wallet simply because their account was designated.

FlowX separates the blockchain fee collection process from the recipient payout process. The token's creator fees are collected on BNB Chain, while the recipient's allocation is settled through X Money. The recipient therefore does not need to interact directly with the underlying creator-fee contract.

The ability to receive a payout depends on X Money's requirements, which are controlled by X and not by FlowX. X Money requires its own account setup, and availability, verification, geographic eligibility, and age requirements are set by X. Where a recipient can already receive, a payout simply lands; otherwise it arrives as a claimable payment.

FlowX does not override X Money's rules. If a payment cannot be completed because the recipient is not eligible, the payment is handled according to X Money's procedures and the FlowX unclaimed-payment policy.

A payment may remain unclaimed when the recipient has not opened X Money or completed the requirements necessary to receive it. The payment is still sent: if the handle can receive, it deposits automatically; if not, X Money holds it as a claimable payment. The claim period is set by X Money, usually within 14 days.

If a payment expires before being claimed, the funds are returned to the FlowX-controlled X Money balance and handled according to the protocol's treasury policy. An expired payment does not remain indefinitely available.

Payment states: Pending means the payment was created but isn't complete yet. Claimable means the recipient can still finish the required steps. Completed means it was received. Expired means the claim window passed and the funds returned to the FlowX balance.

FlowX is designed around transparent fee distribution. Every payout is announced: FlowX replies to the recipient from its official X account with the amount and the token it came from, and X's own receipt is attached, so recipients and the community can understand where a payment originated.

A public confirmation may include the recipient account, the token, the amount processed, the associated claim, and the relevant transaction. Blockchain transactions remain the underlying source of truth for on-chain activity.

The FlowX treasury is the central point used to process creator-fee activity. For the initial FlowX implementation, creator fees are handled within the BNB Chain environment.

The treasury does three things. Collection: creator fees enter the treasury. Accounting: each claim is tied to its transaction and distribution. Settlement: the recipient and protocol allocations are processed from the resulting balance.

If FlowX expands to additional networks in the future, the treasury architecture may be extended to support those networks. Any cross-chain movement introduced by the protocol will be disclosed separately.

The protocol allocation from creator fees is used to support the FlowX ecosystem according to the mechanism defined by the project. If the FlowX token includes a buyback-and-burn mechanism, the applicable portion of protocol revenue can be used to purchase the token from the open market and permanently remove those tokens from circulation. Any buyback transaction occurs at the market price available when the purchase is executed.

Holding the FlowX token does not automatically determine who can launch a token, who receives creator fees, the creator-fee percentage, or the recipient's payout allocation. Those rules are determined by the FlowX protocol. The FlowX token mechanism and its associated disclosures should be considered separately from the creator-fee distribution system.

A recipient can request that FlowX stop sending future payments to their X account by contacting FlowX through its official communication channels. FlowX may require reasonable evidence that the requester controls the relevant X account.

Once a valid removal request has been processed: the account is added to the FlowX do-not-pay list; future creator-fee claims associated with that recipient are handled according to FlowX's removal policy; and future payouts to the account are stopped.

A payment that has already been initiated may remain subject to X Money's existing payment or claim window. Stopping future payments does not retroactively reverse a completed transaction.

Registration is designed to be automatic when all required conditions are satisfied. If a token does not appear in the FlowX system, common causes may include: incorrect fee destination; incorrect allocation; configuration not finalized; recipient is missing; invalid recipient; token is too recent; or an unsupported launch.

Creators should verify: the token's network; the creator-fee destination; the fee allocation; the recipient declaration; and whether the token has been indexed by FlowX.

Creator fees: fees a token generates for its creator from trading on the supported venue.

FlowX treasury: the official address or addresses FlowX uses to receive and process creator fees.

Claim: an on-chain transaction through which FlowX processes accumulated creator fees.

Recipient: the X account named to receive the creator allocation.

Recipient share: the part of a processed claim allocated to the named recipient.

Protocol allocation: the part of a processed claim kept by FlowX for the purposes the protocol defines.

Payout: the settlement of a recipient's allocation through X Money.

Unclaimed payment: a payment that was initiated but not yet received by the recipient.

Treasury: the FlowX-controlled balance that holds creator fees and protocol funds.

Launchpad: the FlowX platform where supported tokens are created and launched.

Registration: how FlowX detects that a token meets the requirements to take part in the creator-fee system.

Claim transaction: the blockchain transaction tied to a specific fee claim.

FLOWX token: the native token tied to the FlowX ecosystem, if one is issued.

FlowX is not affiliated with X Corp.

This deployment runs on BNB Chain. four.meme is the initial supported launch environment; additional environments may be added in the future.

The ability to receive a payout depends on X Money's requirements. Any cross-chain movement introduced by the protocol will be disclosed separately. Digital assets are highly speculative and involve risk of loss.