Overview
Latch is a token launcher for Solana. It takes the idea of launching a token with no seed liquidity, instant trading and creator fees, and builds it on Solana from existing programs. Some parts are built and tested, and some are only designed. Each page says which.
Status. The libraries and programs behind the launch, fees, claim and token pages are built and tested on a local validator, including the fee-splitting vault, renames that wait in public and fee claims for an X account. The page components themselves, and the manage page, have no automated tests and have not been used with a real browser wallet. None of it has run on the live network, the vault is not deployed, and nothing has been audited. A separate indexer is not built. Read Roadmap for details.
How to read these docs
Every mechanism is tagged one of three ways.
| Tag | Meaning |
|---|---|
| Verified | Documented by the third party that runs it (Meteora, Metaplex, Solana). Still check the current docs before building, since these programs change. |
| Designed | Latch's own proposal. It is consistent with Solana's rules but has no code yet. |
| Open | Something we could not confirm and have not tested on the live network. Listed in Roadmap. |
The six moving parts
- Token mint. A plain SPL token with a fixed supply. The mint authority is revoked at launch, and no freeze authority is ever set. Verified, standard.
- Metadata. Name, symbol and image in a mutable metadata account, so a token can be renamed without changing its mint address. Verified.
- The pool. A Meteora DAMM v2 pool holding the entire supply as single-sided liquidity inside a chosen price range. Verified, with details to confirm.
- The locked position. The pool position is permanently locked. Nobody can withdraw liquidity, but trading fees remain claimable. Verified.
- The Latch vault program. Our own on-chain program that owns the position, splits fees between the creator and the treasury, holds the token's name behind a public wait if the creator chose that, and escrows an X-account launch's share. Built and tested locally, not deployed.
- The claim signer. A service on the Latch site that checks an X login and signs a permit the vault verifies. Built and tested with a stand-in login. It needs X credentials to run for real, and it is a real trust assumption.
What a launch produces
mint (fixed supply, mint authority revoked, no freeze authority)
└─ metadata (name, symbol, uri; update authority = creator wallet, the vault if a rename wait was chosen, or none if frozen)
pool (DAMM v2, TOKEN / quote, price range [Pa, Pb], 100% supply deposited)
└─ position NFT (owned by the vault launch PDA, or the creator wallet if the vault is not used; permanently locked)
launch state (vault PDA, only with the vault: creator, recipient, fee split)
fee escrow (vault PDA: the creator share for an X-account launch, claimable with a permit)
Why Solana can do this
Solana programs are upgradeable by default, so "upgradeable logic" is the native state of things rather than a special feature. Positions are NFTs that a program can own. Concentrated, single-sided liquidity exists in production AMMs. And Jupiter already routes across pools, which is how a buyer can pay with a stock token without any special support. See Stock pairs.
What Solana cannot do
Solana has no equivalent of Uniswap v4 hooks, where a pool calls arbitrary code on every swap. We do not pretend otherwise. Latch gets programmability by wrapping the pool in its own program instead. That has real limits, covered in Upgradeability.