Docs

A launchpad for tokens named after real places — a coffee shop, a barber, a bakery, a gym. You pick a business off a map, give the token a name and a picture, and it trades on Solana a few seconds later.

Two things make it different from a generic token launcher:

1. Every token points at a real business, and its page says which one.
2. Most of the trading fee is set aside for that business — whether or not the business has ever heard of the token. It waits in a ledger until the owner turns up and proves who they are.

Launching a token for a business does not involve that business.

Anyone can launch a token for any business. The business did not create it, did not approve it, does not control it, and usually does not know about it. Several people can launch several different tokens for the same shop, and all of them are equally unofficial.

This is on every token page, in the token’s own on-chain metadata, and in the disclaimer any wallet or explorer reads. It is not a disclaimer we bury — it is the product.

The single exception: if the real owner claims the business, verifies it, and launches a token themselves, that one token carries an Owner badge. Everything else on the page stays exactly as unofficial as it was.

Install Phantom, Solflare or Backpack — always from the official site or your browser’s extension store, never from a link somebody sent you. Setting one up takes about a minute.

It will show you a recovery phrase of twelve or twenty-four words. Write it down on paper and keep it somewhere safe. That phrase is the only way back into the wallet: nobody can reset it for you — not the wallet maker, and not us. Anybody who has it has your money, so never type it into a website and never send it to anyone, including anybody claiming to be support.

Claiming your business costs nothing. Signing in is a signature, not a transaction, and submitting a claim never touches the chain — so you can claim and collect without ever buying SOL. You only need SOL if you want to launch a token yourself.

Five minutes, three screens.

Search by name, or pan the map and click a pin. You can also paste a Google Maps or OpenStreetMap link, or let the browser use your location.

Search runs on OpenStreetMap, which is free and open but does not know every small shop. If your place is genuinely missing, drop a pin: click the map, name it, launch on it. Those records are labelled "Added by a user" everywhere they appear, because nothing about them has been checked against an outside source.

By default, SOL. That is what almost everybody wants and you can skip this entirely.

A token can instead be priced in a tokenised share or commodity — 83 are offered, from tokenised index funds and company shares to gold and oil. A token priced in one of them holds its reserve in that asset and pays its fees in it, which means the business behind it earns shares rather than SOL.

Two things worth knowing if you do:

• Buyers are unaffected. Every trading terminal routes from whatever they hold, so somebody paying in SOL never learns the pool is quoted in something else.
• It costs about 0.006 SOL more, because such a launch needs its own pool configuration.

Optional. If you want to hold some of your own token, type an amount and it is bought inside the same transaction that creates the pool — so nothing can get between the token existing and your buy. No bot can front-run you.

The amount is always in SOL, even when the token is priced in something else. If it is, your SOL is swapped into that asset first, automatically, before the launch. You do not choose this and do not need to think about it: you type an amount of SOL, the way you would anywhere else.

There is a ceiling. An opening buy cannot be so large that it pushes the token past its own starting valuation — the form tells you if you go over.

The review screen shows the finished token exactly as it will appear, and what you are about to pay. Your wallet then asks you to approve, once.

Depending on the launch, that single prompt may cover up to three transactions:

Every token starts on a bonding curve — a formula, not an order book. Nobody has to provide liquidity and there is nothing to match: the price follows how much has been bought.

Every trade pays 1.2%. Here is all of it:

A graduated token has not stopped earning — the trading has moved. Fees keep being credited to the same business, read from the migrated pool instead of the curve. The migrated pool charges 1.2%.

Worth knowing before you sign, because no support ticket fixes any of these:

• The name and symbol. Burned into the token at creation.
• The total supply. No more can be minted, by anyone.
• The fee, and where it goes. Set on the pool configuration, which cannot be edited once it exists.
• The locked liquidity after graduation.
• The token’s published website, which is always its page here.

What you can change: the description, the image, and your social links. Those live in our database and remain yours to edit.

You do not have to buy here. Every token is an ordinary Solana token from the moment it exists, and each token page links out to Axiom, Padre and GMGN alongside the Solana explorer. Jupiter and every other aggregator can route to it too.

Nothing about a token is locked to this platform. That is the point of building on a public program rather than a private contract of our own.

You do not need to launch anything to collect the fees. Those two things are entirely separate.

Open the business page and choose Claim. You will be asked to show the place is yours, in one of six ways:

It does: put a verified badge on the business page, make the accrued fees payable to you, and — where the feature is switched on — let you launch one token carrying the Owner badge.

It does not: give you any control over tokens other people launched, remove or hide them, or make any of them official.

Verifying gates the payout, not the earning. The money was always being counted for you; it was simply not payable to anybody yet.

Once you are verified, an administrator approves the accrued balance and sends it. Payouts always go to the wallet you verified with — that is not something a request can override.

You can record how you would rather be paid: in SOL, or in one of the tokenised shares or commodities. That is a preference, not an instruction — it tells whoever settles it what you want, it does not move money by itself. Automatic execution covers SOL today; anything else is settled by hand.

True things you would rather read here than discover later:

• Fees appear when the indexer runs, not instantly. It sweeps on a schedule. Nothing is lost by waiting — it compares lifetime totals, so a missed run catches up completely on the next one.
• Nothing has graduated yet, on any network.
• Tokenised shares can be frozen by their issuer. Those mints carry permissions that allow the issuer to pause transfers. None are armed today, but the ability exists, and a business paid in one of them holds something a third party can freeze.
• Weekend prices drift. Tokenised shares and commodities keep trading on chain while the real market is shut, so a token priced then opens slightly off target.
• A dropped pin has been checked by nobody. Where a place was added by a user the label says so. Treat it accordingly.

Base URL is this deployment: https://coinit.fun. Every response is JSON. Success is wrapped, so a payload can never be confused for an error:

Three steps. The server never verifies a message the client supplied — it rebuilds the expected text from its own stored nonce, which is what stops a signature harvested elsewhere being replayed here.

Two calls, with a wallet signature between them. The server builds the transaction; it never asks for or holds a private key, and no launch is believed until the chain is read back.

/api/metadata/{id} is the URI baked into the mint at creation. Because it is immutable on chain, that address has to answer for the life of the token. It sends CORS * and is safe to read from a browser.

It is the standard shape wallets and explorers expect — name, symbol, description, image, extensions, attributes, properties — plus one namespaced block of our own:

None of this needs us. Tokens are created by Meteora’s public Dynamic Bonding Curve program and, after graduation, live in DAMM v2 pools. There is no custom contract in this project — not a line of it — so anything the site shows, you can read yourself with Meteora’s SDK or by decoding the accounts.

GET /api/launches/{id} hands you tokenMint, poolAddress and configAddress to start from. Pool state — reserves, curve progress, lifetime fee counters, and whether it has migrated — is on the pool account and is the same source this site reads.

Fee counters on the curve are cumulative and monotonic, which is why our indexer diffs them rather than replaying transactions. They freeze at migration; after that the equivalent totals live on the migrated pool’s positions.

Limits are per wallet where you are signed in, and per client otherwise. Exceeding one returns 429 with RATE_LIMITED and a Retry-After header.