01
Declare
The launcher chooses the recipient profile before the token exists. The route is not decided after attention arrives.
Creator rewards, redirected.
Simp for someone.
Launch a token around someone. Creator rewards generated by the launch are routed toward the declared recipient.
Token created↓
Fee route declared↓
Recipient verified↓
Fees claimed
The idea
A token can carry a destination.
The usual launch ends when the token is created.
SIMP.FUN adds one more thing to that moment: a declared recipient.
A public recipient profile is attached before launch. The fee route is established as part of the token’s setup. When the recipient verifies ownership, they connect the wallet that receives the claim.
It is a simple change to the launch flow.
But it changes what creator fees are attached to.
Recipient profile
creator.example/profile
Route
100.00%
Status
Declared at launch
The recipient comes first.
02
Verify
The recipient proves control of the submitted profile and connects a payout wallet.
03
Claim
Once verified, the recipient can view and claim the fees allocated to their route.
For the recipient
Profile → Verify → Wallet → Claim
If a token was launched for you, it should be easy to find.
SIMP.FUN gives recipients one place to locate routes attached to their public profile.
Enter the profile URL.
Verify ownership.
Connect a wallet.
View what has been assigned.
The details are public. The route is deliberate.
Every launch creates a record.
Every recipient route has a defined allocation.
Every completed claim leaves a transaction trail.
SIMP.FUN is built around a simple premise: if a fee route matters enough to talk about, it should exist before the first trade.
01Route record
02Recipient verification
03Claim history
04Transaction references
Launched through SIMP.FUN
Every launch leaves a record.
Tokens created through SIMP.FUN appear here with their declared recipient route.