SELECT PLATFORM
Choose a supported creator identity.
$XFOUR · CREATOR PAYMENTSTOKEN FEES.
TOKEN FEES.
PAID TO CREATORS.
Launch a token and designate any supported X, GitHub, Binance Square or fomo account as the recipient of a configured share of eligible trading taxes.
01 X02 GITHUB03 BINANCE SQUARE04 FOMO
PAYMENT NETWORK INDEXER NOT CONNECTED
TOTAL CONFIRMED CREATOR PAYMENTS0NO PAYMENT ASSET
ALLOCATED0
CLAIMABLE0
PENDING0
PAID0
NO ALLOCATIONSWaiting for confirmed fee events
0NO CLAIMSNo verified creator claims
0NO PAYOUTSNo supported wallet payouts
0NETWORK ACTIVITYMONEY MOVEMENT.
MONEY MOVEMENT.
NOT FAKE MOMENTUM.
Every surface begins at zero and fills only from confirmed contracts, verified identities and indexed transactions.
TOP TOKENS
BY CREATOR FEESx4
NO TOKENS INDEXED
Token rows appear after launch contracts and market providers are connected.
TOP CREATORS
BY ALLOCATED@
0 CREATORS
No verified creator profiles.
RECENT PAYMENTS
PUBLIC LEDGER↗
0 PAYMENTS
No confirmed claims or payouts.
NAME RECIPIENT
Resolve a stable account identifier.
LAUNCH TOKEN
Deploy with disclosed fee rules.
ALLOCATE FEES
Record confirmed eligible amounts.
VERIFY + CLAIM
Bind creator account to a wallet.
PUBLIC RECEIPT
Publish the onchain result.
LAUNCH A TOKEN.
NAME A CREATOR.
LET THE FEES FLOW.
The token, the recipient and the payment—connected by transparent rules and public receipts.
TOKEN DISCOVERYEXPLORE
EXPLORE
xFOUR.
Discover real creator-linked launches once the BNB Chain indexer is configured.
TOKENRECIPIENTPLATFORMCREATOR FEESCLAIMED
x4
NO VERIFIED TOKENS
No demo coins, invented market caps or fake fee totals.
CREATOR REGISTRYVERIFY.
VERIFY.
CLAIM.
Verification proves account control. It does not automatically endorse any associated token.
Account verification
Challenge adapters are not connected.
1
CONNECT WALLETSign authentication message
LOCKED2
GENERATE CODESingle-use and wallet-bound
LOCKED3
PROVE OWNERSHIPUse supported platform method
LOCKED4
BIND ACCOUNTRegister verified wallet
LOCKEDCreator rewards
Assets and source tokens remain separated.
AVAILABLE TO CLAIM0NO VERIFIED ACCOUNT
ASSETSOURCE TOKENSAVAILABLE
—00
PUBLIC LEDGEREVERY FEE.
EVERY FEE.
EVERY PAYMENT.
Allocations, claims and payouts stay distinct and independently traceable.
RECIPIENTSOURCE TOKENAMOUNTASSETTYPETRANSACTIONTIME
↗
LEDGER AT ZERO
No allocation, claim or payout transactions are indexed.
TOKEN LAUNCHPADLAUNCH.
LAUNCH.
TIP ANYONE.
Build a local token configuration. Deployment stays locked until the launch adapter and fee-routing contracts are configured.
Select creator platform
Choose the identity network for the named beneficiary.
AVAILABILITY: A platform becomes claim-enabled only after a secure verification adapter is deployed.
IMPORTANT: The named account is a beneficiary. Being named does not imply endorsement, partnership or participation.
CONTRACT REQUIRED: Percentages are configurable only within deployed contract limits. A creator allocation is a share of eligible collected fees—not trade value.
REVIEW: Confirm the network, token, beneficiary, stable account identifier and enforceable fee rules before any wallet signature.
NETWORKBNB CHAIN
BENEFICIARY STATUSNAMED ONLY
DEPLOYMENTLOCKED
x4
DEPLOYMENT ADAPTER REQUIRED
No contract address or transaction will be created by this standalone interface.
PROTOCOL NOTESTHE PAYMENT
THE PAYMENT
LAYER.
A creator-payment network that happens to use token trading—not a fake revenue dashboard.
From token fee to creator
A token is launched with a named beneficiary. Confirmed eligible taxes are routed according to deployed rules. The creator verifies control of the social account, binds a wallet and claims—or uses a supported verified payout route.
Identity before payment
Usernames are mutable, so xFour should resolve stable platform identifiers where supported. Claims remain disabled when no secure verification method exists.
LAUNCH ADAPTER
Creates tokens with disclosed fee rules.
BENEFICIARY REGISTRY
Maps tokens to creator identities.
CREATOR REGISTRY
Binds verified accounts to wallets.
FEE ROUTER
Allocates confirmed eligible fees.
REWARD VAULT
Tracks separated creator assets.
CLAIM CONTRACT
Prevents replay and double claims.
Security boundary
No seed phrases. No private-key storage. Wallet-bound challenges expire and are single-use. Contracts must enforce permissions, prevent reentrancy, reconcile events and handle failed transfers safely.