Claiming creator fees with GitHub

Anyone can launch a token for a GitHub account. The account's owner claims the fees by logging in with GitHub on xend.to/claim. They never need a wallet at launch time, and they don't sign anything to claim.

At launch: the fees are tied to the account's permanent ID

1. The launcher types a GitHub username or profile link (octocat or github.com/octocat).
2. Xend looks the username up on GitHub and records the account's permanent numeric user ID (for octocat, 583231).
3. The token's creator fees are routed to an escrow vault on Solana that belongs to that ID, not to the username.

Because the vault is keyed by the permanent ID, renaming the GitHub account, or someone later taking over the old username, never redirects the fees.

Every creator fee is split on-chain at launch and can't be changed afterwards:

Claiming

1. Go to xend.to/claim and choose Log in with GitHub.
2. GitHub asks you to approve Xend. Xend only requests read:user, the public profile. It can't see private repositories, email, or anything else, and it can't post.
3. Back on Xend, you see every token launched for your account:
   • the SOL and USDC ready to claim;
   • fees still waiting inside pump.fun;
   • the days left before unclaimed fees expire (see below).
4. Choose where to send the money: your connected wallet, or any Solana address you paste.
5. Press Claim. Xend first collects any of your fees still sitting in pump.fun, then pays out the whole vault in one transaction.

You don't sign anything, and Xend pays the network fees.

You can link more than one account (for example GitHub and X) and claim each one from the same page. A login lasts 7 days.

What happens behind the scenes

• Login: a standard GitHub OAuth login with PKCE. Xend's server learns your GitHub user ID from GitHub itself, so nobody can claim by typing your username.
• Matching: the vault is released only to the account whose permanent ID it was launched for.
• Authorization: Xend's claim service signs a short-lived approval (valid for 2 minutes) that names the vault, your GitHub ID, the destination address and a one-time number. The escrow program on Solana checks that approval before paying out. An approval can't be replayed.
• Binding: the first claim permanently binds the vault to your GitHub ID on-chain.
• Payout: SOL fees (pump.fun pays creator fees in SOL) and any USDC in the vault go to the address you chose.
  • If that wallet has no USDC account yet, USDC below 4 waits in your vault until it reaches 4. Add a USDC account to your wallet to take it sooner.
  • Planned: convert SOL to USDC in the same claim transaction.
  • Planned: pay out to other chains.

The 90-day rule

• The clock starts when the first fee reaches your vault.
• If a vault has never been claimed 90 days after that, its fees go to $XEND buyback and burn.
• Once you have claimed at least once, the vault never expires. New fees keep collecting until your next claim.
• The clock for a platform only runs once that platform's login is live on Xend.

If something goes wrong

• "Log in with GitHub as @name to claim": you're logged in with a different GitHub account than the one the token was launched for.
• "Nothing to claim yet": no fees have arrived yet. Fees arrive as people trade the token.
• "GitHub isn't answering right now": GitHub is rate-limiting lookups. Wait a minute and try again.