What a token here is

A memecoin with an Instagram handle attached. It does not represent that account, their business, their following or their income. They did not endorse it, and may not know it exists. If you are buying one because you think it makes you a stakeholder in somebody's channel: it does not, and you should not.

Where the money actually is

The supply. A launch mints it all at once and divides it: 95% liquidity, 5% vesting. The pool share is locked with no withdraw path. The vesting share is released to the wallet the launchpad is configured with, in 12 steps of 30 days. None of the supply goes to the account — that is not how they are paid.

The fees, which is how they are paid. Two contracts in sequence: the launchpad sends 90% of trading fees to whoever created the coin, and every coin launched here is created by the vault; the vault then records 80% of that against the handle. The account's share of every fee the pool earns is 72%, for as long as the coin trades. The protocol's cut is capped in the bytecode, so the account can never fall below 63%.

That balance sits in the vault. Until a wallet is bound to the handle, there is no function in the contract that can move it — not for the launcher, not for the owner of the vault, not for us. That is why this site says unclaimed and never sent.

Fees do not move on their own

A pool holds the fees it earns until somebody pulls them out. Until that happens a handle's balance reads zero even though the coin has been trading — which looks like the site is broken, and is the commonest reason to think it is.

The call is harvest, and anyone may make it. It pulls a token's fees out of the launchpad and records the account's share. The destination is already decided by the handle, so there is nothing to gain by being the one who calls it — and a harvest only we could trigger would make us a gatekeeper of somebody else's money. Run it from the fee flow page.

Proving the account is yours

You place a one-time code in your bio. We read the profile, see the code, and write your wallet into the vault. It is a single write and it cannot be repeated for that handle — so even if our verification key were stolen tomorrow, an account that is already bound cannot be redirected.

Opting out

Prove the handle the same way and refuse it. No new token can be launched against it afterwards. Tokens that already exist keep existing — they are on a public chain and nobody can delete them — but their earmarked share stays claimable only by you, forever, and the protocol never gains a path to it.

The contracts

Everything above is a claim about code. These are the addresses it runs at, read from this site's own config so they cannot drift from what it actually talks to. Check them before you trust a word of it.

Robinhood Chain, chain 4663. The vault's share of fees is 18% today, and the ceiling written into the bytecode means the account can never fall below 63%.

What can go wrong

Most tokens on any launchpad go to zero, and one with a famous name on it goes to zero faster, because the name is the only reason anyone showed up. The fee share does not change that.

A thin pool can also mean the fees earmarked for an account are worth very little in practice. The number on the ledger is what the contract holds; what it is worth is whatever the market says that day.