user flow.
what shipping a launch actually looks like. concrete enough to match the ui you'll see.
1. connect a wallet
phantom, backpack, solflare. anything that signs solana transactions. we read your address. that's it. no email, no signup form, no captcha.
your address sits in the topbar as 7xKX…3hQq. that's your session.
2. start a launch
one button: launch. opens a form. four fields plus optional description.
- name: 1 to 50 chars. what people see in the feed.
- ticker: 1 to 10 chars, uppercase.
DWIF,MEG, whatever. - image: required. 512×512 minimum. png, jpg, or webp. shows up everywhere the token does.
- description: optional. one line. lands on the pool page.
no supply slider, no anti-snipe knobs, no bonding-curve sliders. the params are sane defaults so people don't fork themselves into a corner.
3. pick a fee claimer
four options as a segmented control: X handle, github user, github repo, none. pick one, an input appears with the right prefix.
- X →
x.com/@then your handle. - github user →
github.com/then the username. - github repo →
owner/repo. no prefix, you type the slug. - none → no input. fees burn.
below the input, one toggle: verify at launch.
flip it on if you're the owner of the named identity and you want to prove it now. submit triggers an oauth handshake against the handle. token mints with verified ✓ baked into metadata. covered in detail in verified launches.
leave it off if you're crediting someone else's handle, or if the account isn't handy. the launch still goes through. fees still route correctly. no badge.
4. review fees
a small panel shows the split. claimer gets the big slice. protocol gets a small cut. exact percent tbd before mainnet.
if you picked none, the claimer slice burns. if you picked an identity and skipped verification, the slice flows to a sealed escrow that the real owner can claim later (see claimable escrow).
5. confirm and sign
a preview card lays out the final state. name, ticker, image, claimer, badge if verified, supply, fee split.
one button: launch token. clicking signs a single transaction. if you toggled verify, the same step opens an oauth window first, then builds and signs the tx.
backend handles the rest:
- mints the SPL token with your metadata.
- creates the pool with our standard params.
- if verified: claimer field on the pool is set to your wallet directly.
- if named but unverified: backend generates an escrow keypair, encrypts the private key under kms, sets the claimer field to the escrow pubkey, publishes the
identity → pubkeymapping. - if claimer is none: claimer field points at a burn address.
6. live in the feed
token lands in the public feed. anyone can trade. fees flow per the pool config without further action.
verified launches carry a small verified ✓ next to the claimer in every surface that pulls our metadata (our feed, dexes, trackers). unverified-but-claimable launches show the identity with no badge, plus a hint that fees are sitting in escrow.
7. claim, if it's yours
if someone launched a coin crediting your handle and you want the fees, you don't need to start over.
visit gud.tek, oauth with X or github against the credited identity, connect any solana wallet you control, click claim. backend decrypts the escrow key, signs a transfer of the accumulated balance to your wallet, rotates the pool's claimer field to your wallet directly. from then on, fees route straight to you.