Trust, by verification.

Two separate proofs. Neither is an endorsement.

Route verified

The fees really go there.

Onchain Pump.fun config: right token, one recipient, 100%, finalized.

Recipient verified

The person really is them.

The X account owner signed in with X. Shown separately, only once it happens.

0%FeeTo’s cut in V1

100% of routed creator fees go to the recipient. Solana network fees still apply.

Route verification

You pick an exact X account. FeeTo creates a dedicated Solana fee destination for that account. You set it as the Pump.fun creator-fee recipient, then paste the token address once.

Before a route goes public, FeeTo reads the finalized Pump.fun configuration onchain and checks the token, the canonical config, that this destination is the only recipient, and that it receives 100%. If any check fails, nothing is published. A verified route can’t be moved to another token.

Identity verification

Routes attach to the X account’s stable ID, not its handle — a renamed or recycled handle doesn’t move fees. Looking up an account identifies it; only the owner signing in with X verifies it.

Sign-in runs through Privy with X. FeeTo checks the session server-side and never asks for an X password.

Funds and signing

Each destination is a Privy wallet assigned to the recipient’s X identity. Sending SOL is signed by the recipient in their own session — FeeTo has no send endpoint of its own.

Sending stays closed until an independent live proof shows the recipient can sign and that no FeeTo, admin or recovery path can. Until then, FeeTo makes no non-custodial or exclusive-control claim.

Reading the numbers

Fees received is history: finalized Pump.fun distributions FeeTo has observed. “Tracked” means since indexing began, so it may be incomplete — it is never labelled all-time.

Available is what sits at a destination right now. It can include other transfers and drops when SOL is sent. The two are never merged. Market cap is outside data, shown with its time, and missing values show as unavailable — never as zero.

What is public

Verified routes are public: token, recipient, destination, proof and observed numbers. Setups in progress, provider IDs, sessions and setup permissions are never published.

Anyone can route fees to any X account. A route never means the recipient launched, approved or endorses the token.

What V1 supports

X accounts. Solana. Pump.fun creator fees. Sending SOL from a destination once ownership is proven. No other networks, no fiat, no bank withdrawals.