Solana · twenty seats · every launch announced ahead
Launching is a privilege again.
Twenty vetted developers. Every launch announced ahead. Every developer vetted, ranked and on the record. No bundles, no dev dumps, no CA before launch. If a developer breaks trust, they are banned.
- Scarcity creates attention.
- Reputation builds trust.
- Competition drives quality.
The board · 20 seats
Why it works
Six rules that make a developer accountable
Every one of them is enforced by the pad or the program, not promised in a group chat. Together they turn a launch from a gamble on a stranger into a trade on a record.
Vetted developers
Three or more past launches checked on chain, a committee interview and 72 hours of public review. Nobody can buy a seat.
Launches, announced ahead
Booked 48 hours ahead at a time the developer picks, and public at once. Liquidity meets a few tickers, not two thousand.
Scored every day
Survival, holder outcome, peak and conduct. Inputs published with every write. Bottom two each season are open to challenge.
Insiders disclosed
Every team and insider wallet listed before launch. Dev allocation capped at 5% and vested over 30 days. LP locked or burned.
Break trust, get banned
Dev sells inside the vest or an undisclosed bundle: a permanent ban from the platform and the seat is vacated the same day.
Everything on the record
Decisions, votes, bans, fines and every score input, in a public log and open JSON feeds anyone can verify.
Compared
Open launchpad vs. Cadre
Same chain, same venues, same traders. A different set of rules for who may launch and what happens when they break trust.
| What a trader faces | Open launchpad | Cadre |
|---|---|---|
| Who can launch | Anyone, anonymously, any number of times | Twenty vetted developers, identity verified by a committee |
| Launches per day | Thousands, competing for the same liquidity | Two, announced 48 hours ahead |
| Dev wallet | Can sell at any time | ≤ 5%, vested 30 days, watched by the pad |
| Insider wallets | Unknown until they dump | Disclosed before launch, on the launch page |
| If the developer rugs | Nothing happens. They launch again tomorrow. | Permanent ban from the platform; seat vacated the same day |
| Track record | None. New wallet, clean slate. | Public score, every launch, every decision, forever |
| Cost to the trader | Free | Free. The pad charges seats and data customers, never traders. |
Built for
Trade the record, not the rumour
Every launch announced ahead, with a dossier, a score and a vetted developer behind each. CA at launch time, verified in one paste.
- Free scanner for any wallet or mint
- Alerts for launch times, launches and bans
- Public leaderboard, refreshed daily
A seat is worth more than a hundred launches
Attention you do not have to buy, a score that follows you, half the launch fees back through the seat pool, and a bench of challengers that keeps the seat honest.
- Free vetting, no deposit
- Verified badge on every launch
- Back to the bench with your record if replaced
The pad's data inside your product
Open JSON feeds for the roster, slots, launches and scores. A verification endpoint for badges and the public ban record. Free, no key, no account.
- Public feeds, no key, 60 s refresh
Roster
Twenty seats, all earned
Every seat is held by a developer who passed vetting and keeps it by performing. Open a seat for its score history, rank, launches and conduct record.
Leaderboard
Daily leaderboard
Seat score = 30% survival + 35% holder outcome + 20% peak performance + 15% conduct, recomputed daily from settled launches of the last two seasons. Holder outcome weighs most because a developer can prop up a market cap with their own money, but not what their holders walked away with. Bottom two at season close are on notice; under 40 at any time is on notice immediately.
| # | Seat | Developer | Score | 30 days | Δ season | Proj. close | Buffer | Survival | Holders ≥ entry | Median peak | Conduct | Challengers |
|---|
Season record
What happened at each close
Season recap card
Generated from the record · 1200 × 630
Launches
Launches, announced ahead
A seat holder books any time of day, at least 48 hours ahead, and it is public at once. A seat with a launch inside its first 14 days cannot book another. Launches are kept at least 2 hours apart.
Next seven days
Tickers are revealed at launch, never before
The pipe, seat by seat
Last 45 days and the week ahead · every seat is one row
Launch ledger
Open a row for the chart, checks and disclosed wallets
| Ticker | Seat | Launched | Launch cap | Now | Multiple | Peak | Holders | Reports | Status |
|---|
For traders
Trade a Twenty launch
The pad is the calendar and the record. Trading happens where it always does. Here is the whole workflow.
Read the dossier before the slot
Every launch is announced at least 48 hours ahead with the seat, its score, its last launches, rank and record. No ticker, no CA until launch time, so nothing can be sniped or front-run.
Get the CA at launch, verify it in seconds
The contract address drops here, on the seat page and on the alert channel at the slot time. Paste it into the scanner: a Twenty launch shows the seat, its rank and the four checks. Anything else is not ours.
Know what protects you, and what does not
Dev wallets are vested 30 days, insiders are disclosed, LP is locked or burned, and a trust break ends in a permanent ban. Price risk stays yours: a clean launch can still go to zero.
Public tool
Pre-check any developer
The same four checks the committee starts with, for any deployer wallet or token mint, free. Developers check themselves before they apply; holders check developers before they buy.
The preview engine returns deterministic sample results for any address. The live engine runs the identical checks against RPC transaction history: dev-wallet outflows inside the 30-day vest, first-block bundles from funding-linked wallets, LP lock or burn, and deployer clusters sharing a funding source.
Bench
Next in line
Developers who passed vetting and are waiting for a seat. Before the replacement window they can signal a challenge; inside it they file one with evidence. Applicants in review sit in a 72-hour public window: a valid flag with evidence earns a 2 SOL bounty from the treasury.
Committee
Decisions on the record
Five members, one-season terms, elected by the seat holders with one vote per seat. Every vetting, ban, fine and challenge is decided in public with the vote shown.
Integrity checks · weekly
Cross-seat wallet clustering and committee independence
Members
Recall needs 11 of 20 seats
Pending
Decided within 24 hours of filing
Decision log
Newest first
| Date | Type | Subject | Outcome | Vote |
|---|
Treasury
Fees and pools
There are no bonds and nothing is locked. Every launch pays a 3 SOL launch fee: half to the seat pool shared by all twenty seats by score, half to the treasury.
| Date | Entry | Amount | Where it went |
|---|
Protocol
How a ban works
No money is ever held. A seat is vetted, ranked every day and can be banned for malicious conduct: a ban needs three of five committee signatures within 24 hours, is decided on the public record and is permanent.
Public record
Pad log
Everything that happens on the pad, in order: launches, reports, bookings, signals, decisions and money. Entries you caused in this preview are highlighted.
Why twenty
The arithmetic of memeflation
Liquidity entering memecoins on a given day is finite. Spread across thousands of launches it buys nothing; concentrated into two it builds. Set your own assumptions.
Both inputs are assumptions you control, not measurements. The point is the ratio, which barely moves whatever you enter.
Liquidity per launch here vs. an open launchpad
—
Per launch · open launchpad
—
Per launch · Cadre (announced ahead)
—
Business
How the pad earns
Two streams, none of which sells a seat or a ranking, and no subscriptions. The model below runs on assumptions you set; the SOL price is the live one from the ticker.
Launch fees are the only stream that exists today. The treasury's 50% of each fee is what the pad itself keeps; the other half goes to the seat pool.
Annual run rate at these assumptions
—
Monthly revenue now
—
Valuation at 4× ARR
—
Pricing
Seats are never for sale · the tools are free
Scanner Live
Free
The four checks for any wallet or mint, one at a time, with a shareable card.
- Public pre-check
- Seat and launch pages
- Open JSON feeds, 60 s refresh
Seat By vetting
3 SOL/ launch · launch fee
The only thing a seat pays. Half of it comes back to the twenty through the seat pool.
- No deposit, no bond
- Any time of day, 48 h booking
- Verified badge on every launch
Status
What is real, what is in build, what is planned
Live in this previewclient
- Full product surface · roster, leaderboard, pipe, calendar, drawers, flows
- Rulebook §1–§11 · tiers, fees, tenure, collusion, bounty
- Scanner UI with preview engine and result cards
- Open feeds rendered client-side · same schema as the API
- Badges, deep links, share and recap cards
In build · repo scaffoldserver
- Scanner engine · four checks against Helius transaction history
- API · /v1 routes serving the feeds, Postgres schema, score cron
- Telegram bot · commands, per-seat alerts, daily digest
- Committee tools · 3-of-5 rulings, public log, daily score oracle
Plannedmainnet
- Audit and a devnet season with real rules
- Founding vetting round · 20 seats from the 148 applications
- Franchise kit · the pad on other chains under the same rulebook
Rules
How the pad works
Short, because they are enforced by the pad and the committee, not by goodwill.
§1
Twenty seats. Nothing else launches here.
Launch rights are a fixed supply of twenty seats. No seat, no launch. Seats are never sold; they are earned through vetting and kept through performance.
- Seats
- 20
- Launch times
- Any time · booked 48 h ahead · 2 h apart
- Booking lead time
- ≥ 48 h
- Lock after a launch
- 14 days per seat
- Hard ceiling per 30-day season
- 60 launches
§2
Vetting
Every applicant goes through the same three stages before a seat is offered.
- On-chain review. At least three prior launches with public wallets. No dev dumps, no undisclosed bundles, no linked-wallet sniping, no serial-deployer pattern across wallet clusters.
- Committee interview. Identity is verified privately with the committee and never published.
- Public review. 72 hours in which anyone can flag the applicant's history with evidence. Then the applicant joins the bench, ranked by pre-check score.
§3
No bond, one standard
Seats are earned through vetting and kept by ranking well on the public leaderboard. Nothing is locked and nothing is slashed. A developer who breaks the trust rules (§7) is banned from the platform for good, with every linked wallet.
- Vetting
- free
- Deposit or bond
- none
- Trust break
- permanent ban
A developer replaced for performance returns to the bench with the record intact.
§4
The seat score
Recomputed every day from settled launches of the last two seasons.
- Survival · launches above launch cap at day 30
- 30%
- Holder outcome · day-30 holders at or above entry
- 35%
- Peak performance · median peak multiple, 10× scores 100
- 20%
- Conduct · 100 clean, −25 per warning, 0 if banned
- 15%
§5
Seasons and replacement
A season lasts 30 days. In the last 72 hours the replacement window opens.
- The bottom two seats at season close are on notice, as is any seat under 40 at any time.
- Bench developers may signal a challenge at any time and file one inside the window with public evidence.
- Holders of the incumbent's last three launches cast a holder signal, weighted by position, that the committee must address on the record.
- The committee decides within 24 hours on the public record.
- A seat on notice at two consecutive season closes is vacated automatically.
§6
Launch standards
Checked by the pad before a launch goes live, not promised in a group chat.
- Dev allocation ≤ 5%, vested linearly over 30 days.
- All team and insider wallets disclosed before launch and shown on the launch page.
- No bundled buys in the first block from linked wallets.
- Liquidity locked or burned at launch.
- Slot booked ≥ 48 h ahead and shown on the calendar.
- Public reports on day 7 and day 30.
§7
Penalties
| Violation | Penalty | Seat |
|---|---|---|
| Dev wallet sells before the vest ends | Permanent ban from the platform | Removed immediately |
| Undisclosed bundle or linked-wallet sniping at launch | Permanent ban from the platform | Removed immediately |
| Abandoned launch: no day-7 or day-30 report, channels dark | Warning, 30-day suspension | On notice |
| Missed booked slot without 24 h notice | 5 SOL fine | Warning on record |
| Report late by more than 24 h | Warning | −25 conduct |
| Bottom two at season close, or score under 40 | None, back to the bench if replaced | On notice, open to challenge |
§8
Collusion
Twenty seats could trade liquidity among themselves. The pad treats that as a trust break, not a strategy.
- Weekly cross-seat clustering: seat wallets that share a funding source, or buy each other's launches in the first block, are flagged on the record.
- Two confirmed links between seats: both developers banned and their seats removed.
- Committee members may not hold any seat's launch above 0.1% of supply during their term.
- Recall: 11 of 20 seats can remove a committee member at any time; the bench's top developer may not fill a committee seat.
§9
Fees and the seat pool
Every launch pays a 3 SOL launch fee when the slot is booked. It is forfeited if the slot is missed.
- Seat pool · shared by all 20 seats pro rata by score at season close
- 50%
- Treasury · committee, bounties, infrastructure
- 50%
A seat that finishes the season on notice forfeits its pool share to the treasury.
§10
Tenure
Three consecutive seasons without a notice, warning or fine make a seat tenured: one extra launch per season and a longer record on the leaderboard. One warning resets the count.
§11
Public review bounty
During an applicant's 72-hour public review, anyone can file a flag with on-chain evidence. A flag the committee upholds pays a 2 SOL bounty from the treasury. Flags without evidence are discarded; three discarded flags from one wallet and that wallet can no longer file.
For holders
What you get that an open launchpad cannot give you
- A known developer with a public record behind every ticker.
- Every insider wallet disclosed before you buy.
- A permanent ban for any developer who breaks trust.
- Launches kept at least 2 hours apart, so each one gets its own attention.
- Day-7 and day-30 reports, or the seat goes on notice.
- A seat score that tells you how this developer's holders did before.
- A vote, weighted by your position, when a developer who let you down is challenged.
- A public daily leaderboard of all twenty developers.
Open data
Feeds and alerts
Everything on this page is a JSON feed. Bots and terminals read the same numbers holders see, with no login and no key. Everything here is free.
Alert preview
Example message
Rule
Media kit
Say it right
Logo, colours, banners and the lines we use. Take what you need for a post, a thread or a terminal integration. Please do not put the logo on a launch that is not on the roster.
Logo
Clear space: the height of the “20” on every side. Never recolour the monogram; on light backgrounds the brass darkens.
Colours · tap to copy
Type: Big Shoulders Display for headlines, IBM Plex Sans for text, IBM Plex Mono for numbers and labels.
X header · 1500 × 500
Avatar · 400 × 400
Lines we use · tap to copy
FAQ
Straight answers
Why exactly twenty?
Twenty seats, a 60-launch ceiling per 30-day season and at least 2 hours between launches keep the pad small. That is few enough for every launch to get attention and liquidity, and many enough that no single developer can hold the pad hostage. The number is a constant of the pad, not a target.
Where do I buy a Twenty launch?
Where it launches: pump.fun, Raydium or whichever venue the seat uses, through any wallet or terminal you already have. Cadre is the calendar, the vetting and the public record, not an exchange. Every launch page here links to the chart and the venue, and the contract address can be copied with one tap once the launch is live.
Can a seat be bought?
No. Seats are earned through vetting and kept through performance. There is no sale, lease or transfer. A developer who stops performing is replaced by the next developer on the bench.
What happens if the developer breaks trust?
The developer is banned from the platform for good and the seat is vacated the same day. A ban does not repay holders and the token keeps trading; the pad does not freeze or delist anything.
Is the developer's identity public?
No. Identity is verified privately with the committee and never published. What is public is everything that matters on chain: the deployer wallet, every insider wallet, the score, the rank and the full conduct record.
How is the seat score different from a vibe check?
It is arithmetic. 30% survival (launches above launch cap at day 30), 35% holder outcome (day-30 holders at or above their entry), 20% peak performance (median peak multiple) and 15% conduct. Holder outcome weighs most because it is the one number a developer cannot buy. It is recomputed every day and the breakdown is on every seat.
Does a developer put money down?
No. There is no bond. A developer's stake is the seat itself: a place among twenty, a public rank and the launch-fee share. Losing it, or being banned, is the cost of breaking trust. The Protocol section shows every state a seat can be in.
What do the twenty seats earn from the pad?
Half of every 3 SOL launch fee goes into a seat pool that is split among all twenty seats by score at season close. Every seat therefore earns from every other seat's launches, which is the point: the twenty have a shared interest in the pad's quality, not only in their own tickers.
What does a bench developer risk by challenging?
Only time and reputation. A challenge needs public evidence, with a 30-day cooldown on that seat if it fails. Signaling a challenge before the window costs nothing and is public.
Who controls the committee?
The seat holders, one vote per seat, electing five members for one season each. The committee cannot create seats, sell seats or change the score formula; it decides vetting, bans, fines and challenges on the public record.
What stops a developer from launching elsewhere at the same time?
Nothing technically, and the pad does not pretend otherwise. But every deployer wallet and cluster is on record, so a parallel launch from a linked wallet shows up in the next review as a serial-deployer pattern, which is a trust break.
Apply
Apply for a seat
Seats open only when one is vacated, so most applicants wait on the bench. Vetting is free and there is no deposit.
Your on-chain history is the application. Write less, link more.
- 01Identity and wallet. The handle we reach you on and the wallet you deploy from.
- 02Prior launches. At least three mint addresses. Your worst one counts as much as your best.
- 03Pre-check. The pad runs the same four checks the committee starts with, so you see what they will see.
- 04Commitments. Disclosure, vesting, conduct and private identity verification.
Application queued for on-chain review
Every launch you listed will be checked, along with the wallets around it. If the history is clean you will be contacted on the handle you gave for the committee interview.
Keep this reference. It is the only acknowledgement you will get until the review is done.
TW-—