> For the complete documentation index, see [llms.txt](https://docs.kumbaya.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kumbaya.xyz/launchpad/unclaimed-tokens.md).

# If your token shows as Unclaimed

When you visit a token's page on Kumbaya, the name might appear in italics with an **Unclaimed** badge near the creator's row, and the description reads *"No description - token launched directly from contract"*. This page explains what that means, why it happens, and how to fix it.

![An unclaimed token's detail page - the italicized name and "Unclaimed" badge are visible to everyone; a green Claim button additionally appears in the header for the on-chain creator wallet only.](/files/FTRsPe7z98GnfzvSCLqI)

## What "Unclaimed" actually means

There are two layers of identity for a launched token:

1. **The on-chain creator.** This is whoever called `ignite()` to deploy the token. It's set permanently in the smart contract - Kumbaya can't change it.
2. **The Kumbaya account that "owns" the listing.** This is what controls the token's metadata on the website (name display, image, prompt, socials), and it's what links the token to a creator profile.

When those two are linked, your token is **claimed** - it shows your real name, your image, your description, and the Claim Fees / Withdraw / Release Vested buttons all work normally.

When they're *not* linked yet, your token is **unclaimed**: everyone sees the italicized name and an **Unclaimed** badge, with no real description, image, or social links. **The green Claim button only appears in the header for the wallet that's the on-chain creator** - other visitors don't see it.

## Why this happens

A Kumbaya launch is two steps: an on-chain `ignite()` transaction that deploys the token, and a follow-up call to Kumbaya's backend that finalizes the listing with your description, image, and socials. A token shows up as Unclaimed when step one happened but step two didn't. The two ways that occurs:

* **Your launch via the website was interrupted before it finalized.** The `ignite()` transaction confirmed on-chain, but the launchpad UI didn't get a chance to register the metadata afterwards - most often because the tab was closed, the connection dropped, or the page refreshed between the on-chain confirmation and the final submit step. The token exists, but Kumbaya's backend never received the "yes, this is mine, here's the description" call that closes the loop.
* **You launched directly via the contracts**, not through Kumbaya's launchpad UI. If you called `ignite()` from a script or an external integrator, you skipped the launchpad UI entirely, so there's no associated metadata or social profile on the Kumbaya side.

## How to claim

If the wallet you're signed in with **is** the on-chain creator (i.e. it's the address that originally called `ignite`), you can claim the listing in a couple of clicks:

1. Go to your token's page (`kumbaya.xyz/#/launch/<token-address>`).
2. Click the green **Claim** button in the header.
3. The Claim modal opens.
4. Fill in / confirm the metadata:
   * **Description** (1–500 characters) - the prompt people will reply to in the token's thread.
   * **Category** - Meme or Dare.
   * **Website** *(optional)*.
   * **X handle** *(optional)*.
   * **Telegram group** *(optional)*.
5. **Sign the message** when prompted in your wallet. This is a free signature (no gas) that proves you control the on-chain creator address. Your wallet will show a structured "Kumbaya Token Claim" message with the token address, chain, timestamp, and a one-time nonce - signing this is what proves your wallet matches the on-chain creator.
6. Submit. The page refreshes and your token now shows your name, your prompt, and your creator controls.

> ⏱ The signature expires in **1 hour**. If you sign and don't submit within an hour, you'll be asked to sign again.

You can optionally upload an image as a separate step on the same flow.

## What if you don't recognize the wallet that launched it?

The on-chain creator is the wallet that signed the `ignite` transaction. If you can't sign messages from that wallet, you can't claim the token - Kumbaya cannot help reassign creator status, because the assignment is on-chain and not under platform control.

If you used **a Privy social login**, try signing in to Kumbaya again with the same login method (email / Google / X / Discord / GitHub / Telegram) you used originally - Privy will give you back the same embedded wallet. The "different wallet" is often just a different login choice in disguise.

## Common questions

**Can I claim someone else's token?** No. The signature has to come from the on-chain creator address. Kumbaya verifies the signature server-side against the creator that's recorded on the contract.

**Does claiming change anything on-chain?** No. Claiming is purely about metadata association - your name, image, social links. It doesn't move tokens, doesn't update the contract, and doesn't cost gas. Just a wallet signature.

**I claimed but my Claim Fees / Withdraw / Vesting buttons still aren't visible.** Refresh the page. If the buttons still don't appear, double-check that the wallet you signed with is the same one you're now logged in with. Mismatch is the usual culprit.

**Is there a deadline to claim?** There's no on-chain deadline for claiming the *listing*. The on-chain timer worth knowing about is the **Tip Jar burn countdown** that starts at graduation: it only affects *user-side* credits that were never tipped to creators (those get burned after the countdown). Tips already received by creators are protected by separate accounting and are not at risk.

## Where to next

* [**Creator fees: how you earn →**](/launchpad/creator-fees.md)
* [**Launching your own token →**](/launchpad/launch-a-token.md)
* [**Connecting your wallet →**](/getting-started/connect-your-wallet.md) - if you want to switch login methods