Next.js on Vercel
The responsive website handles launching, project discovery, X authentication, fee status, and wallet export flows.
PONS X Fees documentation
How the protocol works.
PONS X Fees connects token launches with verified X identities. Launchers can assign a share of creator fees to any handle, while the recipient receives those fees through a dedicated personal wallet.
Core principleThe launch wallet and recipient wallet remain separate.
Launching a token never gives the launcher control of the recipient's wallet. Identity, fee entitlement, and settlement are verified independently.
01
System architecture
The product uses specialized services for interface, identity, application logic, and settlement.
Railway services
Server routes validate requests, manage verified sessions, coordinate fee collection, and communicate with Robinhood Chain.
X OAuth
X authorization proves control of a handle before launches or fees are shown for that identity.
Robinhood Chain
PONS contracts create tokens, accrue creator fees, and settle distributions onchain with public explorer records.
02
Launching a token
The launch flow keeps every configuration visible before the onchain transactions are signed.
Connect the launch wallet
The launcher connects MetaMask and signs a challenge so the selected address is verified.
Configure the token
Choose the name, ticker, image, description, trading tax, X recipient, and recipient share.
Deploy the recipient contract
A dedicated fee recipient contract is deployed and bound to the intended X identity.
Launch through PONS
The verified configuration is submitted to the official PONS factory on Robinhood Chain.
03
Routing and collecting fees
Recipients can receive fees before graduation and do not need MetaMask to collect them.
Fees accrue
Trading fees generated by the token accumulate in the PONS curve according to the launch configuration.
The recipient verifies X
The recipient signs in with the X account named during launch. No launcher wallet access is required.
A personal wallet is prepared
One encrypted personal wallet is assigned to that X identity when fees need to be received.
Fees are collected
The service sponsors the required gas, sweeps the accrued amount, and distributes it to the X wallet.
04
Security model
Browser input never decides the final recipient or claim amount. Onchain state remains authoritative.
Only launches matching the authenticated X identity are shown in the claims dashboard.
Personal wallet material is encrypted and the private key is shown only after fresh X verification.
A dedicated gas payer covers the Robinhood Chain fee so recipients do not need to fund their wallet first.
Token contracts, recipient contracts, and completed transactions can be inspected through Blockscout.
05
Understanding balances
The claims dashboard separates fees that are still on the curve from amounts ready for distribution.
Trading fees generated by the token that have not yet been swept.
Funds currently available for the recipient contract to distribute.
ETH already delivered to the personal X wallet.
After a successful collection, accrued and claimable values can return to zero because the transaction sweeps and distributes the fees immediately. The received amount then appears in the wallet balance.
06
Useful links
Inspect the protocol and market activity through the live network tools.