Solana launchpad · Meteora DBC · 3% fee

Build your RIG

Hold more than 0.3 SOL of $RIG and a random PC part drops into your bench every 30 minutes. First holder to snap all six into place freezes the round, pitches the next token and, if holders say yes, launches it.

88:88--:-- NEXT DROP

Bench empty · connect a wallet

Ranks.exe Shelf My Rig Manual.txt Dice.exe Security Events.log

Live on the desk

What just happened, and what happens next.

SCHEDULER.EXE · Next events

Local time--:--:--

EVENTS.LOG · Live feed

…

loading…/api/feed

RIGVISION 14"

Parts bin

not connected

Recent drops

How it works

Five panels. No whitepaper.

Every 30 minutes the chute opens.

A keyboard. Again.

Hold > 0.3 SOL of $RIG and you get one random part per tick. Six parts, 1/6 each, dupes happen.

Dupes are currency.

Trade 2 identical parts for 1 you need. Any time, as often as you like.

FREEZE!

First full rig freezes the round. Every bench on the network resets to zero.

The builder pitches a token.

VOTE · 15:00

YES

weight = √hold

100× the bag, only 10× the voice.

Name, ticker, image, pitch. Holders vote for 15 minutes. Weight is the square root of your hold.

YES · or nobody voted

The builder launches on Meteora DBC with a dev-buy and keeps 0.5% of fees forever.

Rollback: everyone's parts come back, the builder's rig burns. After 4 no's in a row the 5th idea ships with no vote.

Current round

Press DEL to enter setup. Votes are signed messages, no transaction.

RIG BIOS SETUP UTILITY

↑↓ Move Enter: Yes Esc: No F10: Save & Exit

The chest

3% fee on every trade. Part of it charges the chest. Every hour it discharges.

RIG-PSU 3000

CHEST · AC 230V · DC $RIG

— SOL

pending —

next discharge in --:--

50%buyback & burn—

25%SOL to holders—

25%stays in chest—

Half of every hourly discharge buys $RIG off the curve and shreds it.

Market cap—

Price—

Fees claimed—

SOL bought back—

$RIG burned—

Rewards paid—

From child chests—

Children launched—

Installing $RIG to DAMM v2…—

Bonding curve migrates at 85 SOL.

The shelf

Every token born from a finished rig. Each has its own chest; 25% of it flows back to $RIG. Open the full catalog →

Fair dice log

Nobody picks your part. A blockhash does, and you can check it yourself. Open the full verifier →

C:\RIG\SEEDS.LOG

TICK	TIME UTC	SLOT	SEED	HOLDERS

Check a drop

seed = blockhash of the first slot after the tick moment. Published above.
Holders above 0.3 SOL are snapshotted on the tick.
Your part is:

item = u64_le( sha256(seed ‖ tick_u32_le ‖ wallet)[0..8] ) mod 6
0 CASE  1 MONITOR  2 KEYBOARD  3 MOUSE  4 PAD  5 HEADSET

User's manual

Read before overclocking. Tokenomics with diagrams →

Do I need to do anything to get parts?

No. Hold more than 0.3 SOL worth of $RIG (valued at the pool price on each tick). Every 30 minutes the backend snapshots holders and each eligible wallet gets one part. Connect a wallet here to see your bench.

What happens if I sell or my bag drops under 0.3 SOL?

On the next tick your bench is wiped. While you stay above the threshold your parts are safe, even if you skip ticks.

How does the 2 → 1 swap work?

Pick a part you have at least two of and the part you want. You sign a message (free, no transaction) and the swap is applied instantly. You cannot take the same part you give, and parts cannot be sent to other wallets.

Two people finish a rig on the same tick. Who wins?

The wallet with the lower sha256(seed ‖ wallet) wins. It is deterministic and checkable with the published seed.

How is the vote counted?

Holders above 0.3 SOL at the moment the idea is submitted can vote for 15 minutes. Weight is the square root of your $RIG balance: 100× the bag gives 10× the voice. Yes > No means approved. No votes at all also means approved. A tie is a rejection.

What if the idea is rejected?

Rollback. Everyone except the builder gets their frozen parts back plus anything that dropped during the vote. The builder's rig burns, so they cannot instantly re-trigger. After four rejections in a row, the fifth builder's idea launches with no vote.

Where do the fees go?

Every pool charges a flat 3% in SOL. Meteora keeps 20% of that. The rest is split by the program: on $RIG about 1% of volume to dev and about 1.4% to the chest; on child tokens about 0.5% to dev, 0.5% to the launcher forever, and about 1.4% to that token's chest.

What does the chest do every hour?

50% buys the token back on its own pool and burns it. 25% is paid out to holders above 0.3 SOL as SOL rewards. The last 25% stays in the chest for $RIG, or for a child token flows into the $RIG chest.

Who launches $RIG itself?

The dev wallet, once, with a button on this site. Child tokens can only be launched by the approved builder, within 60 minutes of approval.

MANUAL.TXT · Tokenomics

_×

1 The 3% fee

Every buy and sell on every pool pays a flat 3% fee in SOL, from the first block. No fee scheduler, no dynamic fee. Meteora keeps 20% of it (0.6% of volume). The other 2.4% is the partner share and goes to a program PDA, which is the fee claimer and creator of every pool. The program splits each claim on-chain:

Meteora 0.6% protocol cut, 20% of the fee.
Dev ≈1% on $RIG, 0.5% on child tokens.
Launcher 0.5% on child tokens, paid to the builder for as long as the pool trades.
Chest ≈1.4% per token, discharged every hour (see below).

2 The chest, every hour

Each token has its own chest, a program PDA holding SOL. At most once per hour the keeper calls chest_tick; the interval is enforced by the program, not by the keeper. One discharge splits the free balance like this:

50% buyback and burn. The chest buys its own token on its own pool and the bought tokens are burned. The minimum output is set from the keeper's price with a 3% tolerance, so a sandwich cannot take the buyback.
25% rewards. Paid in SOL to holders whose bag is worth more than 0.3 SOL, pro-rata to the hold. The keeper publishes a merkle root; the keeper pays in batches and anyone can claim their own leaf with pay_reward. Unclaimed SOL returns to the chest after 7 days.
25% remainder. On $RIG it stays in the chest for the next hour. On a child token it moves to the $RIG chest, so every child keeps feeding $RIG.

3 Migration at 85 SOL

Every token starts on a Meteora DBC bonding curve. When the curve collects 85 SOL, it migrates to a DAMM v2 pool with 20% of the supply. The new pool also charges 3% in SOL, the program claims those fees and splits them exactly the same way. 100% of the partner LP is locked forever.

4 Voting rules

Votes are signed messages, never transactions. Only holders above 0.3 SOL at the moment the idea is submitted can vote; buying in after the pitch does not add weight.

Weight = √(your $RIG). 100× the bag gives 10× the voice.
Snapshot of eligible holders is taken when the idea is submitted.
15 minutes of voting. Parts keep dropping meanwhile.
Yes > No → approved. Nobody voted → approved.
Tie → rejected. Rejected means rollback: everyone else gets their parts back, the builder's rig burns.
After 4 rejections in a row, the 5th idea launches with no vote.
No pitch in 30 minutes → expired, streak unchanged. Approved but not launched in 60 minutes → forfeit.

5 Spec sheet

Supply	1,000,000,000 per token, 6 decimals
Mint authority	none, token authority is immutable
Pool	Meteora DBC, quote WSOL, activation by time
Fee	3% fixed, in SOL, on the curve and after migration
Migration	85 SOL → DAMM v2, 20% of supply, 100% partner LP locked forever
Drop tick	every 30 min, holders worth > 0.3 SOL, 1 random part, 1/6 each
Swap	2 identical parts → 1 part of your choice, signed message
Chest tick	every 60 min: 50% burn · 25% rewards · 25% remainder
Rewards	merkle epochs, unclaimed SOL back to the chest after 7 days
Dev-buy	in the same transaction as pool creation

Parts have no value outside this game and cannot be transferred. Memecoins are volatile; assume you can lose everything you put in.

5 sectionsMANUAL.TXT

DICE.EXE · Provably fair

_×

Recompute a drop in your browser

item = u64_le( sha256( seed ‖ tick_u32_le ‖ wallet_utf8 )[0..8] ) mod 6
0 CASE  1 MONITOR  2 KEYBOARD  3 MOUSE  4 PAD  5 HEADSET

seed is the blockhash of the first slot after the tick moment, published in the table below.
Holders worth more than 0.3 SOL are snapshotted on the tick.
The browser concatenates the seed bytes, the tick number as 4 bytes little-endian and your address as UTF-8 text.
It hashes them with SHA-256, reads the first 8 bytes as a little-endian u64 and takes it mod 6.
The result is compared with the server log at /api/drops/:tick.

Seed log

C:\RIG\SEEDS.LOG

TICK	TIME UTC	SLOT	SEED (hex)	HOLDERS

Ready/api/ticks · /api/drops/:tick

SECURITY.TXT · Trust model

_×

ID Program

Every $RIG and child pool is created by one on-chain program. Its PDA is the creator and the fee claimer of each pool, so fees can only move the way the program splits them.

PROGRAM ID RiGDZCX2chW6HN9v4RzU9jXTwcwwHG9gzkq3qB7UWXY Solscan ↗

? Who can do what

ADMIN one key

Can

Change the admin, keeper and dev addresses.
Change the chest interval, within 1 minute to 24 hours.
Pause new launches and chest ticks.
While paused: shut a token down. Its chest and open reward epochs are closed and that SOL goes to the admin wallet. This is the emergency switch; you trust the admin not to abuse it.
Upgrade the program: the program was initialized by its upgrade authority. Check the current authority on Solscan.

Cannot

Mint more tokens. Mint authority is gone.
Pull the locked LP after migration.
Change the 3% fee or its split without a program upgrade.

KEEPER the bot

Can

Run the 30 min part drops, swaps and votes. These live in the backend database, not on-chain.
Approve one wallet to launch a child token, after the vote.
Call the hourly chest tick, which the program rate-limits.
Publish the reward list (merkle root) for each epoch.
Close an epoch after 7 days: unpaid SOL goes back to the chest.