How GoLaunchMe works

GoLaunchMe turns a token's creator fees into donations to a real fundraiser. A deployer launches a token on a supported venue and locks its creator fees to a wallet GoLaunchMe creates for that project alone. The token's description names a GoFundMe campaign, and that campaign is who the fees are for.

Everything between the two is mechanical. Fees accrue to the project's own wallet as the token trades, GoLaunchMe claims them on chain, 80% is converted to dollars and donated to the campaign on GoFundMe, and 20% buys $GLM and burns it. Every step is recorded against the claim that produced it, and every donation is confirmed in public.

The campaign organiser is not asked to do anything first - there is no account to make and no wallet to connect, so a donation can arrive from a token they have never heard of. Control sits where it already did: the organiser decides whether the campaign accepts donations, and can also ask us directly. Section 13 covers stopping donations.

1. 1

   A token directs its fees

   The deployer locks 100% of creator fees to the project's own dedicated wallet, permanently. See section 3.
2. 2

   The description names a campaign

   One line in the token description says who the fees belong to. See section 4.
3. 3

   The token registers itself

   The indexer sees the fee direction on chain and registers the token. There is no approval step.
4. 4

   Fees are claimed

   GoLaunchMe claims accrued creator fees on a schedule and records each claim against its transaction signature.
5. 5

   The campaign is funded in dollars

   The campaign share is donated on GoFundMe from a pre-funded float, and a public post confirms it.

A token can direct fees to GoLaunchMe from a supported launchpad. Which one it launched on changes how fees are directed and how the direction is made permanent, and nothing else: the split, the donation rail and the ledger are identical. pump.fun is live today; pons.family is not live yet.

pump.fun

Solana. Live. Fees directed after creation, from fee sharing. $GLM is issued here.

pons.family

Robinhood Chain. Not live yet. Fees will be directed at creation, as the fee wallet.

four.meme

BNB Chain. Being explored. Not supported, and may never be. See the disclosures page.

Both venues end in the same place: GoLaunchMe is the token's fee recipient, permanently, and it cannot be moved afterwards.

Two rules hold on both. It has to be the whole fee, because a partial share would mean the donation we publish is a fraction of what the token earned with no way for the campaign to tell which. And it has to be permanent, because a fee direction that can still be changed is a promise that can still be withdrawn.

On pump.fun

Directed after the coin is created, not during. The create form has no fee-recipient field. Fee sharing is a separate screen on the coin, where a creator can split fees across up to ten wallets; add the GoLaunchMe treasury there at 100% and the token appears in its sharing config as a shareholder.

That config stays editable until its authority is revoked, so a token is detected but not payable until the revoke flag is set. Revoking is what makes it permanent.

When

After the coin exists, from fee sharing

What we watch

The Pump Fees sharing config, per mint

Made permanent by

Revoking the config's authority

On pons.family

Not live yet. This is how it will work once it is; nothing on pons is being funded today.

Directed at creation. The fee wallet is one of the fields set when the token is launched, alongside its name and image, so pointing it at the GoLaunchMe treasury is part of creating the coin rather than a second visit.

There is no separate revoke step, because the assignment is its own lock: pons' contract lets only the current recipient hand the fee wallet on. Once it is ours, the deployer cannot take it back.

When

At creation, as the fee wallet

What we watch

The creator fee recipient on the token

Made permanent by

Assignment itself. Only we can move it

On either venue there is no approval step and no queue. A token that meets both rules registers on its own.

Directing a token's creator fees to the GoLaunchMe treasury constitutes acceptance of the Terms of Use by the deployer.

The GoFundMe campaign that gets funded is read from the token's description. Put this line in it, with the link of the campaign you want funded:

Use the format exactly, substituting the campaign link you want funded, anywhere in the description. Write whatever else you like around it: the line is what we read, so the rest of the description is yours.

The wording matters more than it looks. A description can easily mention several links, and without a fixed line there is no way to tell which one is meant to be funded. “Fees to” and “via GoLaunchMe” bracket the campaign so only one reading is possible.

If the line is missing we fall back to the first GoFundMe link in the description, and then to the campaign the token's website points to. Both work, and neither is as reliable as the line.

Keep it inside the shorter of the two description limits. pons.family allows 256 characters and pump.fun allows considerably more, so a description written to fit pons will fit either.

The organiser does not need to agree, know in advance, or hold a wallet. That is the point of the design: a token can be launched for a cause, and the first the organiser hears of it is the donation arriving and a public post saying where it came from.

Every claim divides the same way. There is no discretion in it, no schedule to negotiate, and no tier that changes it.

To the campaign

80%, donated in dollars on GoFundMe

Protocol cut

20%, spent buying $GLM and burning it

Applied

Per claim, at claim time

Fees we add

None. The 20% is the whole of it

The one exception

$GLM itself does not split. All of its own fees are held as protocol treasury

Creator fees do not arrive continuously. They accrue to the project's own wallet as a token trades and sit there until they are claimed, which GoLaunchMe does on a schedule rather than on every trade. Claiming per trade would spend more in transaction fees than it collected on a quiet token.

Each claim is written to the ledger keyed on its own transaction signature, so a claim cannot be recorded twice and every obligation can be traced back to the on-chain event that created it. The campaign share and the protocol cut are both computed at that moment, from that claim, and neither is recalculated afterwards.

A claim can fail. Chains halt, RPC providers go down, and transactions revert. A failed claim creates no obligation and is retried; the fees stay accrued in the meantime and are not lost.

Donation milestones

Donations land at milestones. A campaign's share builds until it crosses $5 — then $10, $20, $50, $100, $250, $500, $1,000, and every $1,000 after. Each crossing sends the full balance.

Balances below a milestone keep building; nothing expires for an active campaign. If the campaign has closed or stopped accepting donations, the balance is held for 14 days in case it reopens. See Undeliverable donations.

If a token has named your campaign, the money is already headed to it. There is nothing to claim and no form to fill in. It is donated once the balance crosses a donation milestone, for as long as the campaign accepts donations.

1. 1

   A token names your campaign

   Somebody launches a token and points its creator fees at your GoFundMe campaign.
2. 2

   Fees accrue and are claimed

   Trading generates creator fees. We claim them on chain on a schedule.
3. 3

   80% is donated to it

   Donated on GoFundMe from a pre-funded float, so it does not wait on an off-ramp. It shows on your campaign's donor list under the token's name, and you withdraw it the way you withdraw any other donation.
4. 4

   A public post confirms it

   @gofundme_fun posts so you and your supporters can see where the money came from.

You are not required to do anything, acknowledge anything, or agree to anything. Receiving a donation does not make you a customer of GoLaunchMe or a promoter of the token that named your campaign.

Donations made through GoLaunchMe are treated by GoFundMe like any other donation, and how they are taxed depends on the campaign and where you live. GoLaunchMe does not issue tax documents, and nothing on this site is tax advice. If the amounts become meaningful, put them in front of someone who does taxes for a living. Where the law requires us to collect information before donating, the donation waits as a held balance until we have it.

Donations settle on GoFundMe, so the only requirement is a campaign that is live and accepting donations. That is controlled on GoFundMe, not here, and GoLaunchMe cannot open a campaign for you or change its settings.

Any public GoFundMe campaign can be named: medical, memorial, emergency, animal rescue, education, or a registered charity's own fundraiser. Where a campaign is accepting donations, a donation simply lands.

We check the campaign is live before every donation. When a balance crosses a milestone the donation is made, and if the campaign has been paused, closed or removed by GoFundMe the balance is held instead. GoFundMe sets its own rules on who can run a campaign and withdraw from it, and GoLaunchMe has no say in them. Section 9 covers what happens to a donation that cannot be delivered.

Any GoFundMe campaign can be named, and the donation is made for as long as it is accepting donations. If the campaign has been paused, has closed, or has been removed, the donation cannot be delivered and the balance is held.

A held balance waits 14 days. If the campaign reopens inside that window the donation is made, with nothing else to do. If it does not, the balance passes to the protocol treasury, where it funds the $GLM buyback the same way the protocol cut does. That is the only thing that ever happens to an undeliverable donation, and it is why the window is published rather than decided case by case. A campaign that has asked not to be funded is covered in section 13.

Who can be named

Any GoFundMe campaign

Hold window

14 days from the failed donation

If the campaign reopens in time

The donation is made

If it does not

Passes to the protocol treasury

Every donation is announced. @gofundme_fun posts the amount, the campaign and the token it came from, and the donation shows on the campaign's donor list, so the organiser and their supporters can both see it.

We do this so the organiser can find out at all. Most were not asked before their campaign was named, so the donation is usually the first they hear of it, and the post is what they and their supporters can check it against.

A token earns its fees on whatever chain it launched on. The donation rail and the $GLM market are not on all of those chains, so the treasury is where they meet. Fees are claimed on the chain that earned them and arrive at the treasury as one balance.

$GLM lives on Solana, so a protocol cut earned anywhere else has to cross before it can be spent. That crossing happens at the treasury, once, and it is the only bridge in the path.

Donations do not cross that bridge. The campaign share settles in dollars on GoFundMe from a pre-funded float, whichever chain the fee came from.

The protocol cut is spent buying $GLM on the open market and burning it. The protocol buys from the same market as everyone else, at whatever the price is when it buys, and the tokens are sent to a burn address. Both halves are on chain and can be checked by anyone.

$GLM gates nothing. Holding it does not change the split, does not change who can launch, and does not change which campaign gets funded. The $GLM page sets out the mechanism in full, and the disclosures page sets out what the token is not.

Whether a campaign accepts donations is a setting on GoFundMe. Pausing donations there stops GoLaunchMe donating, the same as it stops anyone else.

You can also ask us directly. Send a request with reasonable proof you organise the campaign to @gofundme_fun on X or to admin@golaunchme.fun. We honor removal within 7 days: your campaign comes off the site, it goes on a do-not-fund list, and we stop claiming the creator fees of tokens that name it, leaving those fees unclaimed on chain. A donation already made stays with the campaign. Any balance accrued for your campaign but not yet donated passes to the protocol treasury when your removal takes effect.

Registration is automatic, so a token that has not appeared has failed one of a short list of conditions. In rough order of how often each is the cause:

Not the whole fee

The sharing config gives GoLaunchMe a partial share. It has to be 100%.

Not yet permanent

On pump.fun, the sharing config's authority has not been revoked. The token is detected but not payable until it is.

Wrong treasury address

Fees are directed at an address that is not the GoLaunchMe treasury. Check it against the launch page.

No campaign in the description

Nothing in the description names a campaign, and the token's website is not a GoFundMe link either.

Too recent

The indexer reads the chain on a schedule. A token created moments ago has not been seen yet.

Creator fees

The fees a launchpad pays to a token's creator wallet in respect of trading in that token.

Fee sharing

pump.fun's screen for splitting creator fees across up to ten wallets. Where a pump.fun token directs fees to GoLaunchMe.

Fee wallet

pons.family's field for the address that receives creator fees. Set at creation.

Claim

An on-chain transaction in which GoLaunchMe collects accrued creator fees for a registered token.

Campaign share

80% of a claim, donated to the named GoFundMe campaign.

Protocol cut

20% of a claim, spent on $GLM buybacks.

Undeliverable donation

A donation that could not be made because the campaign is paused, closed or removed. Held for 14 days, then passes to the protocol treasury.

Held balance

A campaign share withheld under the reserved rights or taxes provisions of the Terms, held until that provision resolves it.

Float

The pre-funded dollar balance donations are made from, so a donation does not wait on an off-ramp.

Treasury

The address a token's creator fees are directed to, and where every chain's balance meets.