How it works

Three moves, one signer

A launch is an act of naming. Everything after it is a constant in a contract, except the one step that has to ask the platform who you are.

01 · Launch

Name them

Type a handle on X, TikTok or YouTube, a name and a ticker. The contract deploys the coin with the platform and handle written in, mints the whole supply to its own curve, and gives you nothing: no allocation, no cut, no admin. It costs gas.

02 · Trade

It trades

Buys and sells run against one constant product forever. There is no graduation and no pool to migrate to, so there is always a bid. One percent of every trade is the fee, and the same transaction splits it.

03 · Claim

They take it

Ninety percent of each fee is credited to the handle and waits with no expiry. The creator proves the handle, by signing in with the platform or by putting a six-letter code in their bio, names a wallet, and the contract releases everything it holds in one transaction.

Plainly

What the contract promises

  1. Anyone can launch for anyone. A launch makes no claim about the launcher, only about who should be paid, so there is nothing to forge and no gate.
  2. The launcher gets nothing. No allocation, no share of fees, no control. If you want the coin, you buy it like everyone else.
  3. The split is 90 / 5 / 5 and it is a constant. 90% of the fee to the creator, 5% spent on the coin's own curve and burned, 5% to the protocol. Nobody can change it after deployment.
  4. The buyback is inline. The burn share is spent on the curve in the same transaction as the trade that produced it, and the tokens it buys are destroyed. No keeper, no treasury, no discretion about when.
  5. The curve never graduates. A virtual reserve of 0.05 ETH seeds every curve and is never withdrawable, which is what keeps the last seller payable.
  6. Fees accrue to a handle, not an address. The escrow is keyed on keccak256(platform + ":" + handle). The creator has usually agreed to nothing and may never have held a wallet, and that is fine: the balance waits.
  7. Nobody can touch a curve or a handle balance. Not the owner, not the verifier. The owner can rotate the verifier and the vault, and withdraw the protocol's 5%, and that is the whole list.

The trust

The one thing you have to take on faith

Nothing on chain can check who owns a social account. So one key, the verifier, signs "this wallet has proved it owns this handle", and the contract will only release a balance to a wallet the verifier named.

What it can do

Say who you are

Sign an attestation after a sign-in with the platform, or after reading a code out of a public bio. Each one names one wallet, one nonce and a fifteen-minute deadline, and is good for exactly one claim.

What it cannot do

Move money

It has no function to call that moves a reserve, a balance or the protocol's share. If its key leaked, the worst case is a misdirected future claim, and the owner rotates it with one transaction.

Open problem

Renamed handles

Handles are keyed as text because text is all a launcher can know. A handle that is released and picked up by someone else is a real risk. The verifier remembers the account id it first saw behind a handle and refuses a different one afterwards.

Open problem

Consent

The person named never opted in. The fees are theirs whether they want them or not, and a coin with their name on it exists whether they like it or not. We state this rather than pretend it away.

Launch one

Pick a handle. The rest is the contract's problem.

Back to the pad