retakepaired with $ttwo
HomeTokensUpdatesLaunchDocumentation
@retakettwo
Ctrl K
Launch
docsSolana · paired with $TTWO

The final GTA launchpad

Mutable metadata on Solana: a coin's name, ticker and image can be updated after launch.

Same mint, same supply, same balances. By default, holders vote on each update, so a GTA narrative can stay in one coin instead of splitting across many.

Launch a coinHow it works

01The problem#

GTA moves fast. A trailer drops, a character trends, a leak names a city, and within minutes there are ten coins for the same thing. Each one bets on a different name. Holders split across them, each camp shills its own ticker, and whoever picked the wrong name gets vamped.

A real one: the same narrative fought between AudaCity ($DacityCoin) and Dacity Coin ($Dacity). Same idea, two coins, two communities, and liquidity split in two.

AudaCity
AudaCity
$DacityCoin
vs
Dacity Coin
Dacity Coin
$Dacity

02Mutable metadata#

On Retake, a coin's identity is not locked at launch. Its name, ticker and image can be updated on-chain later, on the same mint. Nobody migrates, nobody claims, nobody sells one coin to buy another.

same coin · mint 7xKp…3FqAmetadata update
Before
AudaCity
AudaCity
$DacityCoin
name
AudaCity
ticker
$DacityCoin
image
audacity.png
↓one tx
After
Dacity Coin
Dacity Coin
$Dacity
name
Dacity Coin
ticker
$Dacity
image
dacity.png
mint · supply · balances · pool: unchanged

The name debate happens inside one coin. Holders propose names and vote, and the winner is written on-chain. If opinion changes later, a later vote can change it again. One coin follows the narrative instead of several competing for it.

Note
Every update is public. It is one on-chain transaction, logged on the Updates page with its signature.

03Holders choose or creator#

Who can update a coin's metadata is chosen at launch. There are two options.

Holders choosedefault · recommended
  • Rounds of 60 minutes by default.
  • Any holder proposes a name, ticker and image.
  • Votes are weighted by token balance.
  • One proposal and one vote per wallet per round, up to 20 proposals.
  • Free: a signed message, no transaction.
  • When the round closes, the winner goes on-chain.
Creatoryou decide
  • Only the wallet that launched the coin can update it.
  • From the coin page, any time.
  • Sign a message with the new name, ticker and image.
  • No fee. The launchpad submits the transaction.

04How holder votes work#

Most coins on Retake let holders choose. Voting runs in rounds, 60 minutes each by default. In each round, holders propose a name, ticker and image, and vote for one proposal. Votes are weighted by token balance at the moment the round closes, so moving tokens to a second wallet does not add weight. The winning proposal becomes the coin's new metadata.

Take the AudaCity vs Dacity Coin case. Launched once on Retake, both names would be proposals on the same coin. Holders pick one; if they later prefer the other, a later round switches it, and nobody has to sell or move.

  1. 1
    Propose
    During a round, any holder submits a name, ticker and image. Up to 20 proposals per round.
  2. 2
    Vote
    Each wallet votes once. Its weight is its token balance when the round closes.
  3. 3
    Close
    At the end of the round the keeper tallies the votes. The proposal with the most weight wins.
  4. 4
    Write
    The winner is written on-chain in one transaction and appears on the Updates page. The next round opens.

05What changes, what never does#

Can change
  • Name1 to 32 characters
  • Ticker1 to 10 letters or digits
  • Imagepinned on IPFS
  • Descriptionoptional
  • Metadata URIa new IPFS document per update
Never changes
  • Mint addresssame token, forever
  • Supply1,000,000,000, fixed
  • Balancesnothing to migrate or claim
  • Liquidity and poolcurve, then DAMM v2
  • Price historycharts follow the mint

One field is locked: the website in every coin's metadata always points to its page, retakepad.tech/coin/<mint>, so wallets and explorers link back to the current identity and its history.

06Paired with $TTWO#

Every curve on Retake trades against $TTWO: Take-Two Interactive, the company behind GTA, as a tokenized stock issued by Backpack Securities. GTA coins, quoted in GTA's publisher.

You still pay in SOL. Jupiter swaps SOL to TTWO inside the same approval as your launch or buy. When you sell, it comes back to you as SOL.

you pay
SOL
from your wallet
↓
swap
Jupiter
SOL → TTWO
↓
quote
$TTWO
Take-Two, tokenized
↓
buy
The curve
Meteora DBC

sells run the other way: curve → TTWO → Jupiter → SOL back in your wallet

Mint
TTWofwAge91oFhZs7kpQdyrVRkmevgM88xijGvQFbKo
Decimals
6
Issuer
Backpack Securities (tokenized Take-Two Interactive stock)

07Launch in 4 steps#

  1. 1
    Pick the identity
    Name, ticker, image, and your X link. The website is set to the coin's page for you.
  2. 2
    Choose who updates it
    Holders choose (default) or creator only. This is fixed at launch.
  3. 3
    Add a first buy
    Optional. Enter an amount in SOL; it is swapped to TTWO and bought on the curve in the same transaction.
  4. 4
    Approve once
    One wallet approval creates the mint, the metadata and the curve. The coin is live and tradable right away.
Launch a coin

08Fees and curve#

ParameterValue
Supply1,000,000,000, 6 decimals, fixed
CurveMeteora Dynamic Bonding Curve, quoted in TTWO
Starting market cap≈ 30 SOL (≈ $2.5k)
Graduation≈ 550 SOL market cap (≈ $46.5k)
After graduationMigrates to a Meteora DAMM v2 pool; LP permanently locked
Curve trading fee1% flat on every trade
DAMM v2 pool fee1%
Updating metadataFree for holders and creators
Note
Curve thresholds are set in TTWO when the config is created, so their SOL and dollar values move with the TTWO and SOL prices.

09On-chain details#

For developers, wallets and explorers.

Partner update authority#

Every coin launches from a Meteora DBC config with tokenUpdateAuthority = PartnerUpdateAuthority. The launchpad's partner key stays the Metaplex metadata update authority, and the metadata account stays mutable. The mint authority is revoked at creation, so the supply can never change.

The update transaction#

An update is a single transaction: a Metaplex UpdateMetadataAccountV2 with the new name, symbol and a new metadata URI pinned on IPFS, plus a memo. Fields that aren't meant to change are read from the current account and written back as they are.

update transaction
one transaction, signed by the partner key
  1. Token Metadata · UpdateMetadataAccountV2
       metadata          PDA("metadata", METAPLEX, mint)
       update_authority  partner key (signer)
       data  DataV2 {
         name, symbol, uri        ← the new identity
         royalties, creators      ← carried over unchanged
       }
  2. Memo  · tags the update and its sequence number

unchanged: mint · supply · decimals · balances · pool

Signed messages#

Proposals, votes and creator updates are authorized by a plain-text wallet signature, not a transaction. The server rebuilds the message from the request, checks the signer, and rejects anything older than a few minutes so a signature can't be replayed.

holder · propose
Retake: propose the next identity
token: 7xKp…3FqA
name: Dacity Coin
symbol: Dacity
image: https://…/ipfs/bafy…
round: 29817342
issued: 1794480000000
holder · vote
Retake: vote on the next identity
token: 7xKp…3FqA
proposal: 1842
round: 29817342
issued: 1794480000000
creator · update
Retake: update my token's metadata
token: 7xKp…3FqA
name: AudaCity
symbol: DacityCoin
image: https://…/ipfs/bafy…
issued: 1794480000000

The keeper#

The keeper is the launchpad process that closes finished rounds. About every 30 seconds it checks for rounds that have ended, tallies the balance-weighted votes, and writes the winner on-chain with the partner key. Only one update per coin can run at a time; if a transaction fails, nothing is recorded and the coin keeps its identity.

Metadata JSON#

The URI points to a standard token metadata document on IPFS, in the format wallets already read. Each update pins a new one.

metadata.json
{
  "name": "Dacity Coin",
  "symbol": "Dacity",
  "image": "https://…/ipfs/bafy…",
  "description": "…",
  "twitter": "https://x.com/…",
  "website": "https://retakepad.tech/coin/<mint>",
  "createdOn": "https://retakepad.tech"
}

Indexers should re-read a coin's metadata account when they see a transaction from the partner key on its metadata, and not cache a Retake coin's name forever.

10FAQ#

Do I need to do anything when a coin I hold is updated?+

No. Same mint, same balance. Your wallet shows the new name, ticker and image the next time it refreshes the token.

My wallet still shows the old name. Why?+

Wallets and explorers cache metadata, sometimes for hours. The coin page on Retake always shows the current identity, so check there.

Can an update move my tokens or the liquidity?+

No. An update only rewrites name, ticker and the metadata URI. Minting, balances and the pool are outside what the update authority controls.

Can I vote twice by moving tokens to another wallet?+

It doesn't help. Weight is each wallet's balance when the round closes, so tokens moved to a second wallet stop counting for the first.

Does voting cost anything?+

No. Proposing and voting are signed wallet messages, not transactions. The update itself is paid by the launchpad.

What if nobody votes in a round?+

Nothing changes. The coin keeps its current identity until a round closes with a winner.

Is anything hidden?+

No. Every update is public on-chain and listed on the Updates page with its transaction. A coin's full history is on its page.

What's the risk with $TTWO?+

TTWO is a tokenized stock issued by Backpack Securities. Its issuer can pause or freeze it, which would affect trading on curves quoted in it.

Launch a coinBrowse tokensFollow @retakettwo

Retake is not affiliated with Rockstar Games or Take-Two Interactive.

On this page7 min · 0%
  1. 01The problem
  2. 02Mutable metadata
  3. 03Holders choose or creator
  4. 04How holder votes work
  5. 05What changes, what never does
  6. 06Paired with $TTWO
  7. 07Launch in 4 steps
  8. 08Fees and curve
  9. 09On-chain details
    1. Partner update authority
    2. The update transaction
    3. Signed messages
    4. The keeper
    5. Metadata JSON
  10. 10FAQ