UNIQ documentation

What UNIQ is

UNIQ is a Solana launchpad for tokens that can evolve after launch. A normal memecoin is frozen at birth: its name, ticker and image never change. On UNIQ, holders can propose and vote on changes to their token's identity (name, ticker, image, banner, description, links), its primary trading pair and its governance settings. Passed identity changes are written on-chain into the token itself, so every wallet, explorer and terminal sees them. Pair switches and governance-setting changes are recorded by UNIQ.

Under the hood UNIQ is built on audited Meteora programs plus one small UNIQ program:

• Meteora Dynamic Bonding Curve (DBC) runs the launch: price discovery on a curve, fee collection and automatic graduation.
• Meteora DAMM v2 receives the liquidity when the curve completes. That liquidity is permanently locked.
• Token-2022 is the token standard. Its metadata extension stores name, symbol and URI inside the mint account, which is what makes on-chain updates possible.
• UNIQ launch guard is a transfer hook, on every launch from the Launch page, that rejects every buy for the first 6 slots (except the creator's capped dev buy).

UNIQ's own backend indexes launches, holds the governance records, builds transactions for you to sign and runs the execution worker. It never holds your keys and never moves your funds.

Getting started

1. Connect a wallet

Click Connect and pick any Solana wallet that supports the Wallet Standard (Phantom, Solflare, Backpack…). UNIQ runs on Solana mainnet: every action costs real SOL.

2. Sign in

Actions that are tied to you (launching, trading on UNIQ, proposing, voting, chatting, claiming fees, editing your profile) need a session. Signing in asks your wallet to sign a Sign-In With Solana message: domain, your address, a one-time nonce, chain ID and an expiry. It is a message, not a transaction, so it costs nothing and cannot move funds. The session is a token stored in this browser for this site, valid 7 days. There is no password: your wallet is your login.

3. Sign each action

Two kinds of signatures exist on UNIQ:

• Transactions (launch, buy, sell, claim, create a configuration, apply metadata): your wallet shows the balance changes before you approve. UNIQ builds the transaction, you sign it, UNIQ checks it is the transaction it prepared (the only wallet additions accepted are harmless ones: compute budget or read-only instructions), then broadcasts it.
• Action messages (propose, vote): free signed messages that bind your wallet to the exact content hash, so nobody can submit a vote in your name or alter it.

Glossary

Mint

The token's address. It identifies the token everywhere.

Quote token

What the token is priced and bought in: SOL, USDC, a tokenized stock, etc.

Bonding curve

A formula that sets the price from how many tokens have been sold. Buying raises the price, selling lowers it.

Graduation / migration

When the curve has collected its target, liquidity moves to a regular AMM pool (DAMM v2) and the curve closes.

Configuration

A reusable on-chain Meteora DBC config that fixes the curve, fees, quote token, liquidity locks and protection for every token launched with it.

Partner

UNIQ's wallet registered in the configuration: it receives the partner share of fees and is the metadata update authority.

Slot

Solana's unit of time, about 0.4–0.5 s.

Snapshot

A frozen record of every holder's balance at the moment a vote opens. Voting weight comes from it.

Timelock

A waiting period between a vote passing and its execution, so anyone can react.

bps

Basis points. 100 bps = 1%.

Launching a token

Go to Launch. Everything you enter is validated by the server before any transaction is built, and the review step shows the full disclosure of the configuration you are about to use.

Fields

What happens when you click Launch

1. If the configuration for your pair does not exist yet, your wallet first signs its creation (one-time, about 0.006 SOL of rent). Anyone launching after you reuses it.
2. Your image and metadata JSON are uploaded. The JSON is versioned: v1, v2, … each new version is a new immutable file.
3. UNIQ builds one transaction that creates the mint, writes name/ticker/URI into it, creates the DBC pool and, if you chose it, the dev buy and the launch guard. A fresh mint keypair co-signs it.
4. You approve it in your wallet. It lands in a single slot: the token and its pool exist atomically or not at all.
5. UNIQ verifies the result on-chain (mint, pool, mint/freeze/update authorities, metadata URI, hook and guard), indexes the token and opens its page.

What is fixed at birth

• Supply: 1,000,000,000 tokens, 6 decimals. Mint authority is revoked in the launch transaction: nobody can ever mint more.
• Freeze authority: none. Nobody can freeze holders.
• The quote token and the pool. A pool's pair can never change (see pair switching for what can).

Costs

A launch costs network rent for the mint, pool and accounts plus a priority fee, typically well under 0.05 SOL, plus UNIQ's 0.02 SOL launch fee, plus the dev buy if any (a measured mainnet launch cost about 0.01 SOL before the launch fee). New token addresses start with U. Creating a missing configuration adds about 0.006 SOL once.

Launch configurations

Every token is launched with a configuration: an on-chain Meteora DBC account that fixes the economics for all tokens that use it. UNIQ defines them server-side, so creators cannot be tricked into hidden parameters, and every token page shows the configuration's full disclosure.

Shared by all default configurations:

• Trading fee 1.25% plus a volatility-based dynamic fee (configurations created before 2026-10-27: 1%).
• 50% of the trading fees (after Meteora's protocol share) go to the creator.
• After graduation: 100% of the liquidity permanently locked (50% in UNIQ's position, 50% in the creator's), 0% unlocked.
• Post-graduation pool fee: 1% on DAMM v2.
• Metadata update authority: the UNIQ executor key, a server key that applies passed proposals automatically. It holds no funds: the partner fees it can claim are sent straight to the UNIQ treasury, automatically, every 10 minutes.

Bonding curve & graduation

While on the curve, the token trades only against its DBC pool. Each buy pays the quote token into the pool and receives tokens out of it; each sell does the reverse. The price follows the curve from the initial market cap to the migration market cap.

When the pool has collected enough quote token to reach the migration market cap, it is complete: no more curve trades. Meteora then migrates the liquidity to a DAMM v2 pool (migration is a permissionless instruction, normally triggered by Meteora's migration service). The LP positions are created and permanently locked according to the configuration, and trading continues there.

Dev buy

You can buy your own token inside the launch transaction, before anyone else can. To keep this fair, UNIQ caps it at 2% of the supply (20,000,000 tokens). The form quotes the exact cost on the curve, including fees.

• The dev buy is a normal curve buy, paid from your wallet, at the curve's opening price.
• It is disclosed: anyone can see it is the first trade in the creation transaction.
• With launch protection (always on): your dev buy is the only buy the guard lets through before trading opens. The guard itself enforces the cap: tokens must go from the pool into the creator's own associated token account, which may hold at most 2% of the supply, counted cumulatively. You cannot sell or move those tokens until trading opens. See Launch protection.

Team allocation

Not offered on the Launch page while launch protection is always on (protected configurations have no team allocation). The UNIQ SOL · team 10% configuration reserves 10% of the supply for the creator, locked in Meteora's vesting:

• Nothing is released before graduation.
• After graduation: a 30-day cliff, then 6 equal releases 30 days apart (180 days in total).
• Locked team tokens never vote (the vesting escrow is excluded from snapshots). Released tokens vote like any others.

The rest of the supply sits on the curve. Launch protection is not offered on this configuration.

Launch protection (anti-snipe)

Snipers buy a new token in the same block it is created, often by bundling their buy right behind the creation transaction. Launch protection makes that impossible on-chain. It is always on for launches from the Launch page (there is no switch), and the token page shows a protection badge with the opening slot.

How it works

1. A protected token is created as Token-2022 with a transfer hook pointing to the UNIQ launch guard, program Go8w4svvr4HRiThVuqroQFSDX9EqwLxXh9QEDmBnub4r. Token-2022 calls the hook on every transfer of the token, no exception.
2. In the same transaction as the pool creation, the guard records the creation slot and computes the opening slot: creation slot + 6 (about 2–3 seconds). It refuses to initialize unless the pool is the real Meteora pool of this mint created in this exact slot.
3. Every buy moves tokens out of the pool, which is a transfer, so it runs the hook. Before the opening slot the buy fails with TradingNotOpen, whatever the route: UNIQ, Jupiter, Axiom, Meteora directly, a Jito bundle or a custom program. The check lives in the token, not in UNIQ's website.
4. From the opening slot on, the guard accepts every transfer.
5. When the curve completes, Meteora revokes the hook. After graduation the token is a plain Token-2022 token.

The one exception: the creator's dev buy

Inside the protected window the guard lets exactly one kind of buy through: tokens going from the pool into the creator's own associated token account, which may hold at most 2% of the supply. The cap is enforced on-chain and is cumulative, so splitting the buy does not get around it. Before opening, the creator cannot sell or move those tokens either. See Dev buy.

What it does not do

• It does not slow anyone down after opening. At slot +6 the race starts for everyone and bots are still fast. It removes the block-0 / bundle advantage, it does not make bots slow.
• No team allocation on protected configurations.
• Durations are in slots, so seconds are an estimate.

Trust & review

• The guard has no admin, no pause and no allowlist: as deployed, it accepts every transfer after opening.
• The program is upgradeable. Its upgrade authority is the UNIQ treasury wallet 7EvuC7mQ65DyKqpn42TPSCNNMFUtKYAXFSV9euyhb8a, so an upgrade could change its behaviour until Meteora revokes the hook at curve completion. It was upgraded on 2026-10-27 to add the capped creator buy.
• It is tested on a local validator against the real Meteora program and has been reviewed internally, but it has not been externally audited.

Creator fee recipient

By default the creator share of trading fees goes to the wallet that launches the token. Under Creator fees go to on the Launch page you can send it somewhere else instead. Only one recipient per token: splitting fees across several wallets is not available.

Sending fees to a GitHub account

• If the account has already proven a wallet on UNIQ, that wallet is the pool creator from the start, exactly like Another wallet.
• Otherwise the fees accumulate inside the Meteora pool, held for the account. The UNIQ executor key (Ksgm5VaFMKcVfi5dUvakL8LJTZHHrEar1sQD98CHuES) holds the pool-creator role meanwhile, but the fees stay in the pool: they are not claimed or moved.
• On claim, the creator role, and every fee accrued so far, moves to the proven wallet. If the token graduated before the claim, the creator's locked LP position is kept for the account and handed over on claim too.

How a GitHub account claims

1. Open uniq.fun/claim, enter the GitHub username and see the tokens and amounts waiting.
2. Connect and sign in with the wallet that should receive the fees.
3. Publish a public gist on gist.github.com from that account containing exactly UNIQ fee claim: <your wallet address>.
4. Click Verify. UNIQ finds the gist, links the account to the wallet and transfers the creator role of every waiting token to it. From then on, new launches for that account pay the wallet directly, and the fees are claimed like any creator fees (see Fees & claiming).

Pairs: SOL, USDC, stocks, custom

SOL and USDC are always accepted. Under Stocks, Crypto and Memes you can pick another quote token, or paste any mint under Custom. UNIQ then checks the mint live and refuses it unless all of these hold:

• It is an SPL token, or a Token-2022 token whose extensions Meteora accepts without review, or one Meteora has badged for both DBC and DAMM v2.
• No active transfer hook (a foreign hook could block your token's trades).
• No live transfer fee.
• New accounts are not frozen by default and transfers are not paused.
• Jupiter lists it as verified and has a USD price for it.

All 17 xStocks in the picker (tokenized equities and ETFs such as TSLAx, NVDAx, SPYx, GLDx…) pass. Their curve is sized from their USD price to run about $5k → $70k of market cap. Powers the issuer of the quote token keeps (for example, xStocks' issuer can freeze or pause its own token) are listed in the disclosure, because they can affect your pool.

Fees & claiming

On the curve

• Every trade pays 1.25% plus a dynamic fee that rises with volatility (1% on configurations created before 2026-10-27). Fees are taken in the quote token.
• Meteora keeps 20% (0.25% of each trade). The rest is split 50% creator / 50% UNIQ partner: 0.5% of each trade each.
• Launch fee: 0.02 SOL paid by the creator to UNIQ, inside the launch transaction and shown before signing.
• Fees accumulate inside the pool until claimed. Nobody can claim someone else's share.

After graduation

• The DAMM v2 pool charges 1% per trade to liquidity providers.
• The creator's and UNIQ's locked positions keep earning those fees forever, claimable by each position's owner. The liquidity itself never unlocks.

How to claim

On a token page whose creator fees go to your wallet, Your creator fees shows the unclaimed amount. Click Claim, approve the transaction, and the fees land in the wallet that signed. The claim transaction is built for your wallet only: the server checks you are the fee recipient (the Meteora pool creator), the fee claimer or the position owner before building it. If the launcher chose another wallet or a GitHub account as recipient, only that recipient can claim (see Creator fee recipient).

Trading

The token page has a Buy / Sell panel that trades against the token's primary pool.

1. Enter an amount: UNIQ simulates the trade on the current pool state and shows what you get.
2. The minimum received allows 1% slippage. If the price moves more before your trade lands, it fails instead of filling worse.
3. Approve in your wallet. UNIQ checks the signed transaction matches what it quoted, broadcasts and confirms it.

You can also trade UNIQ tokens anywhere else (Jupiter, Axiom, Photon…): the pools are standard Meteora pools. UNIQ does not take an extra fee on its own panel.

Evolving metadata

What is where

Each update writes a new versioned JSON (v2, v3…) and an on-chain transaction that sets the new name, ticker and URI on the mint. Old JSON versions stay online, so history is auditable.

Who can update

The update authority is the configuration's partner (Meteora's "partner update authority" option): the UNIQ executor key for tokens launched from 2026-10-28, the UNIQ treasury wallet for older ones. UNIQ's policy is to use it only to apply proposals that passed governance. An audited admin update path also exists; any change made through it is labelled "admin" in the token's History. Every change, either way, is a public transaction visible on Solscan.

The "Updated" badge

When a token's metadata changed on-chain, its page shows Updated next to the name and a banner with the previous name and ticker, the time, the slot and a link to the exact transaction on Solscan: the on-chain proof. If an update has been pre-approved, an Update scheduled banner shows when it will execute if the vote passes.

Other apps (Axiom, Phantom, Jupiter…)

They read the same on-chain fields, so they show the new name and ticker after the transaction, but each app caches metadata. Updates usually appear within minutes to hours; some apps refresh images only when their cache expires. UNIQ cannot force another app's cache.

Governance

Each UNIQ token has its own governance, created at launch with these defaults:

Proposal types

• Name, ticker, image, banner, description or social links change, or several at once (metadata update).
• Primary pair switch (recorded by UNIQ, see below).
• Community configuration change: voting period (1 h–14 d), quorum (1–100%), approval (>50%–100%), timelock (0–14 d), cooldowns (0–30 d).

Who votes

When voting opens, UNIQ takes a snapshot of every holder's balance from the chain. Buying after the snapshot gives no votes; selling after it does not remove them. Excluded from the snapshot: the bonding-curve reserves, the DAMM v2 pool reserves and the locked team vesting escrow, so pool-held tokens can never vote. Eligible supply is what remains.

Votes

FOR, AGAINST or ABSTAIN. A vote is a free signed message bound to the proposal and your choice. Each wallet votes once per proposal and a vote cannot be changed. All tallies use exact integer arithmetic.

Proposal lifecycle

Example: a metadata proposal opens Monday 15:00. If the 25th voter arrives Monday 18:00 with ≥ 60% FOR, the name changes on-chain within seconds. Other proposals close after 48 h and wait the 24 h timelock.

Execution & pre-approval

Tokens launched from 2026-10-28 have the UNIQ executor key as metadata update authority. UNIQ's worker signs with it the moment a metadata proposal passes, so nothing waits for a human. This is a server key: if UNIQ's server were compromised, an attacker could rename those tokens (not move funds; the key holds none). Older tokens keep the treasury wallet as authority and use the pre-approval flow below:

1. During the vote or after it passed, the authority reviews the proposal in UNIQ's admin and clicks Validate. Its wallet signs, once, the exact metadata transaction. The transaction uses a durable nonce, so it does not expire.
2. That signature alone is not enough: the transaction also needs UNIQ's execution co-signer. The worker adds that second signature only if the proposal reached QUEUED, its timelock has ended and the metadata cooldown has passed.
3. The worker sends it and records the result. The token page switches to Updated with the transaction link.
4. If the token's metadata or authority changed in the meantime, the approval is void and must be redone. If the proposal is defeated, expires or is cancelled, the pre-signed transaction is discarded. It could not run anyway without the co-signer, and once its nonce account is reused the nonce advances, which invalidates it permanently.

Primary pair switching

A pool's quote token is part of its address and can never change. "Switching pair" means changing which existing pool UNIQ treats as primary (used by the trade panel, prices and charts).

• The target must be an existing Meteora DAMM v2 pool for the same token, paired with SOL (at least 5 SOL on the quote side) or USDC (at least 500 USDC).
• It goes through a normal governance vote with an execution deadline.
• The switch only changes UNIQ's primary-pool record. No liquidity is moved, old pools keep trading and stay listed.

The token page

Header

Ticker, name, image, version, Updated badge, holders, pair, network, protection badge. The curve progress card sits below.

Trade panel

Buy / Sell against the primary pool.

Proposals

Active and past proposals with live tallies, token logo and proposed logo.

Propose an evolution

Right-hand column: a form (title, reason, new name / ticker / image / banner / description / links) that becomes a governance proposal if you hold enough.

Chat

Any signed-in wallet can post (up to 1000 characters).

History

Every metadata version with its JSON and transaction.

Pools

Every pool of the token with protocol, lifecycle, the PRIMARY tag and address, plus a form to propose a pair switch.

Holders

Top 20 holders, team allocations, and heuristic clusters (3+ wallets buying in the same slot, the creator wallet) with a confidence level.

Your creator fees

For the creator fee recipient: unclaimed fees and the Claim button.

Disclosures

The configuration's full terms: fees, curve, liquidity, authorities, protection, quote-token risks.

Explore, Analytics, Profiles

• Explore lists only tokens launched on UNIQ, with market cap and 24 h volume in USD.
• Feed (sidebar) gathers every proposal across all UNIQ tokens: Active, Queued, Past.
• Profiles: every wallet has a public page (avatar menu → View profile) with its live SOL, USDC and UNIQ-token balances, tokens launched, proposals and votes. Signed-in owners can set a display name, bio and avatar.
• Contact sends a message to the UNIQ team, with a screenshot if you are signed in.
• Analytics shows UNIQ's own metrics from its index: volume, trades, traders, lifetime curve fees (read from Meteora), launches, votes and top tokens. USD values use current quote prices.

Trust model & security

What nobody can do

• Mint more tokens (mint authority revoked at launch).
• Freeze holders (no freeze authority).
• Withdraw graduated liquidity (100% permanently locked).
• Claim someone else's fees. Creator fees held for a GitHub account stay in the Meteora pool until that account claims them.
• Block trading on a protected token after its opening slot, short of upgrading the guard program (see below).

What UNIQ can do, and how it is limited

• Update metadata (name, ticker, URI) through the executor key (new tokens) or the treasury wallet (older tokens). Policy: only to apply passed proposals. An audited admin path exists and its changes are labelled "admin" in History. Every update is a public, linked transaction.
• Claim the partner share of fees and the fees of its own locked positions. For new tokens the executor key claims them automatically and sends them straight to the treasury; anything else it receives (LP position NFTs after graduation, SOL above a 0.05 SOL reserve) is forwarded to the treasury too.
• Upgrade the launch guard program (its upgrade authority is the treasury wallet) until the hook of a token is revoked at curve completion.
• Hold creator fees for a GitHub account: while the account has not claimed, the executor key is the pool creator. Policy: it never claims those fees; it only transfers the creator role (and a graduated token's locked LP position) to the wallet the account proves.
• Run governance: snapshots, tallies and execution are operated by UNIQ (Mode A, see above).

How UNIQ handles keys

• The treasury wallet's key is never on UNIQ's servers. Every action it takes is signed in a wallet by a human.
• The server holds the executor key (metadata authority of new tokens, so passed proposals apply instantly) and the execution co-signer. The executor key holds no funds; if the server were compromised, it could rename new tokens and claim pending partner fees, plus creator fees still waiting for a GitHub account to claim them (the only creator role it holds), but not touch holders' tokens, other creator fees or liquidity.
• Every transaction you sign is built by the server, then compared to what was prepared before broadcasting. Wallet changes that add writes are refused.
• UNIQ will never ask for your seed phrase or private key.
• Sign-in and action signatures use one-time nonces bound to the domain and content, so they cannot be replayed.

Audits

Meteora publishes audits for DBC and DAMM v2. The UNIQ launch guard and the UNIQ backend have not been externally audited.

Programs & addresses

FAQ & troubleshooting