The catalogue
Conditions of sale, in full
Rename Pad launches coins whose name can be bought. Anyone can rename a coin; every new name costs 1.1x the last one; the previous namer is paid 40%, half of the price buys the coin back and burns it. Every number on this page is read from the program.
- 01How a rename works
- 02A worked example
- 03The price ladder
- 04Where the money goes
- 05The burn
- 06The house (moderation)
- 07A coin's life
- 08Parameters
- 09Accounts and seeds
- 10Instructions
- 11Errors
- 12Verify on chain
- 13Admin can / cannot
- 14Risks and the honest compromise
- 15FAQ
1. How a rename works
- Type a name (1-32 bytes) and a ticker (1-10 letters or digits). The house checks it as you type.
- Hammer it. The site pins a new metadata file (same picture, new name), asks the house for its signature, and builds one transaction: the house's Ed25519 approval, the
renameinstruction, and the largest buyback the program accepts right now. - You sign once. The program pays the previous namer, the house and the coin's burn pot, rewrites the Token-2022 metadata of the coin (name, ticker, link) and records the new name in the coin's history for good.
- The new name is protected for 1 h. After that the next name costs 1.1x.
2. A worked example
A coin launched with the base price 0.050 SOL. Three people rename it in turn:
| rename | price | to the previous namer (40%) | house (10%) | burn pot (50%) |
|---|---|---|---|---|
| No. 1 | 0.050 | 0.020 to the creator | 0.005 | 0.025 |
| No. 2 | 0.055 | 0.022 to namer 1 | 0.0055 | 0.0275 |
| No. 3 | 0.0605 | 0.0242 to namer 2 | 0.00605 | 0.03025 |
Namer 1 paid 0.050 and got 0.022 back when namer 2 arrived. Renaming your own coin to farm the 40% loses at least 60% of the price every time.
3. The price ladder
price_0 = ceil_1000(base), price_n = ceil_1000(price_(n-1) x (10000 + step_bps) / 10000), with step_bps = 1000 (+10%). ceil_1000 rounds up to 1000 lamports (0.000001 SOL). The step, the split and the protection time are copied into each coin when it launches; a later settings change never touches an existing coin.
4. Where the money goes
Rename price
40% to the previous namer (the creator for the first rename), 10% to the pad treasury, 50% (the remainder, including rounding) into the coin's burn pot. The transfers happen inside the rename instruction: nobody has to claim anything.
Trading fees
Coins trade on a Meteora bonding curve with a 1% fee, then on a Meteora DAMM v2 pool. The pad's share of the fees is collected by anyone (collect_fees, collect_amm_fees) and split per coin: 50% for the coin's creator, 20% into the burn pot, 30% to the treasury.
Launch
A flat 0.020 SOL plus 2.5% of the creator's optional first buy. The first buy happens in the launch instruction itself, before anyone else can trade.
5. The burn
The burn pot is spent by buyback_curve (on the bonding curve) or buyback_amm (after the move to DAMM v2): the pad buys the coin and burns every token bought in the same instruction. The site adds the largest acceptable buyback to your rename transaction; the keeper spends the rest in steps. Each buyback may move the price by at most 1% (on the pool after the move, less when outside liquidity providers share the fees) and runs at most once every 60 s, and it must not sit next to a swap in its transaction: a sandwich around it costs more in fees than it can take. Anyone can run a buyback.
6. The house (moderation)
Every launch name and every rename needs the house's Ed25519 signature. The house refuses brands, the names and tickers of established coins, slurs (including leet and look-alike spellings), stylised or invisible letters, words that mix Latin with look-alike letters of another alphabet, names on the on-chain stop-list, and metadata whose name does not match. It also checks the chain: the coin, the rename number, the protection time and your wallet.
The signed message is 44 bytes: "renamepad:v1" || sha256(mint || index u64 LE || namer || valid_until i64 LE || sha256(name || 0 || ticker || 0 || uri)). It is bound to one coin, one rename number and one wallet, and expires within 600 s. A copied approval is useless to anyone else. The house's key: -.
On chain there is also a hash stop-list (Blocked accounts) the admin maintains. The history of a coin can never be erased: the stop-list only stops new names.
7. A coin's life
| stage | what happens |
|---|---|
| Consigned | Meteora bonding curve created by the program; the coin's metadata authority is the pad's partner PDA; History No. 0 = the launch name. The launch name is protected for the protection time too. |
| On the curve | Trading in SOL, 1B supply (Token-2022, 6 decimals, no mint or freeze authority). Renames and buybacks on the curve. |
| Curve full (12 SOL) | Anyone migrates it to a DAMM v2 pool; 100% of that liquidity is locked to the pad for good. Renames keep working; buybacks switch to the pool. |
8. Parameters (live)
| First rename (base price) | - |
| Every next name | - |
| To the previous namer | - |
| To the house | - |
| Into the burn pot | - |
| Protection after a rename | - |
| Launch fee | - + - of the first buy |
| Trading fee | - |
| Fee share: creator / burn / treasury | - / - / - |
| Buyback price impact cap | - |
| Buyback spacing | - |
| House approval lifetime | - |
| Curve size before the DEX pool | - |
| Paused | - |
| Coins / renames so far | - / - |
9. Accounts and seeds
| account | seeds | holds |
|---|---|---|
| Config | ["config"] | admin, treasury, house key, Meteora config, parameters, counters |
| partner | ["partner"] | no data; metadata authority of every coin, fee claimer, owner of the locked DEX liquidity |
| Coin | ["coin", mint] | current name, ticker, link, rename count, next price, last namer, parameters copied at launch, pot, totals |
| vault | ["vault", mint] | SOL of the burn pot and the creator's fee share |
| History | ["hist", mint, n u64 LE] | name No. n: name, ticker, link, namer, previous namer, price, paid to the previous namer, time |
| Blocked | ["blk", sha256("renamepad:blk" || normalised text)] | stop-list entry: kind, who, when |
10. Instructions
Launch and rename need the house's approval; buybacks, fee collection, the move to DAMM v2 and the creator payout can be run by anyone.
| instruction | arguments |
|---|
11. Errors
| code | name | what it means |
|---|
12. Verify on chain
- Program: -. Config: -.
- Read a coin's mint: its Token-2022 metadata update authority is the partner PDA -; the mint has no mint or freeze authority.
- Read
History ["hist", mint, 0..n]: n + 1 entries, eachprev_namerequals the previous entry'snamer. - Every rename transaction shows three system transfers (previous namer, treasury, vault) that add up to the price.
- Every buyback transaction burns exactly the tokens it bought: the mint supply is 1B minus the burned total.
- The house's key in Config (-) is the only key whose approvals the program accepts.
13. Admin can / cannot
| the admin can | the admin cannot |
|---|---|
| pause new launches and renames (buybacks, fees and payouts keep working) | move a burn pot, a creator's share or anyone's SOL |
| change parameters for coins launched from then on | change the price, split or protection of an existing coin, or raise a launch fee under a dev who is consigning: the launch carries the first price, the flat fee and the dev-buy % the page showed, and fails if any of them changed |
| add or remove stop-list entries; rotate the house key | rename a coin or erase a name from its history |
| set the treasury; hand the admin role over in two steps | mint tokens or freeze anyone's tokens |
Wind-down: pausing stops new money coming in; everything already in pots keeps being burned by anyone, creators keep being paid.
14. Risks and the honest compromise
- Wallets cache names. Some wallets show a new name within minutes, some within a day; lists such as Jupiter's can take 1-3 days. Helius DAS re-reads the metadata when it changes (every rename writes a new link for that reason); Phantom has no public refresh; DexScreener, Birdeye and Solscan use their own caches. This site reads the chain and is the source of truth.
- Mutable metadata. Rugcheck shows "Mutable metadata" as a mild warning. That is the product: only the pad's program can change it, and only through a paid, attested rename.
- The house is a trust point. It can refuse a name, and a leaked key could approve a bad one (still paying full price). The admin can rotate the key; the on-chain stop-list is the backstop.
- Ugly but legal names. Renaming is open by design; the 1-hour protection and the +10% ladder make each hold more expensive.
- Unofficial coins. Meteora lets anyone open a pool on the pad's bonding-curve config. Such a coin names the pad's partner PDA as its metadata authority, so an explorer or a terminal may show it as a Rename Pad coin, but it was never launched here: no house approval, no launch fee, no fee split, no burn pot, and the pad never renames it. It is never listed on this site, and its address opened here (
/lot/<mint>, share links, cards) is marked UNOFFICIAL. Only coins with aCoin ["coin", mint]account are lots. - Old wallets. Rename transactions use a lookup table (v0 transactions); a wallet without v0 support cannot rename.
15. FAQ
Do I get paid when someone renames after me?
Yes: 40% of their price goes straight to your wallet in their transaction. Nothing to claim.
Can two people buy the same name slot?
No. The rename carries the rename number you saw; the second transaction fails with "someone renamed it first" and costs nothing.
Does the picture change?
No. The site pins new metadata with the same picture; only the name and ticker change.
What if the house refuses my name?
Nothing is sent and nothing is paid. The refusal says why.
Is the coin a pump.fun coin?
No. pump.fun metadata cannot change, so Rename Pad coins launch on a Meteora bonding curve and move to a Meteora DAMM v2 pool. They trade on Jupiter and any router that reads those pools.