Yumi
Launch

slot —launch 0.03 SOLbots outside 900

One deployer, one private bundle per coin. The mint stays secret until it exists, so nobody can aim at block zero. A 2% tripwire is sold into the first sniper's buy, and look-alike tickers are rejected at the form.

Launch a coin See live coins

Block zero

Nothing lands
before you.

The deployer signs the create and the tripwire as one atomic Jito bundle: same block, both or neither. Nobody sees the mint address before it exists on chain, so there is nothing to point a bot at. Each coin page proves it with the block itself.

  1. Block 0Create · tripwire 2%yours alone
  2. Block 1Snipers
  3. Block 2Tripwire sells
  4. Block 3Buys
  5. Block 4Buys, a sell
  6. Block 5Buys
  7. Block 6Buys

Tripwire

The first sniper
buys our 2%.

Bots that miss block zero pile into block one. By then the deployer already holds 2% of supply, bought at the curve's opening price inside the launch bundle, and it unloads all of it into the first outside buy. No sniper within about 2.5 seconds? It sells anyway. It never sits on the bag.

  1. 01Deployer buys 2%in the launch bundle
  2. 02A sniper buysin block one
  3. 03Tripwire sellsinto that buy

The tripwire runs on Yumi's SOL, not yours. Block one stays open: a bot can still buy there, it just pays our 2% for the privilege. 0 snipers tripped · tripwire on every launch

Clone check

Clones bounce.

Every ticker and name is normalized while you type: letter case, spacing, look-alike Cyrillic and Greek letters and leetspeak map to one canonical string, which is matched against every coin Yumi has launched. Names within one letter of an existing one are rejected, and pictures are compared by perceptual hash, so a resized or recoloured copy still matches.

If $PEPE is on Yumi, all four are refused:

  • $P3PELeetspeakPEPE
  • $pepeCasePEPE
  • $PЕPECyrillic ЕPEPE
  • $P E P ESpacesPEPE
$

Type a ticker to see the form it folds to.

Dev grades

Earn your black.

Grades live on the dev's wallet and darken one shade per clean coin that bonds on Yumi. Selling half the bag inside the first hour, bundling through linked wallets or a holder flag turns it to Flagged, and it stays that way until the coin drops out of the dev's last five. New wallets start at White: there is no reset button.

Dev buys wait for the tripwire to clear, so a dev is never in block zero, and Yumi won't build one that puts a dev over 10% of supply while the coin is on its curve.

Bag check

Every bag
in the open.

Every coin page pulls its holder list from the chain and breaks it down: the dev's share against the 10% cap, the top ten, the first blocks' buyers, and clusters of wallets whose first SOL came from one address. Exchange hot wallets are skipped, since they fund half of Solana.

Dev Pale
3.1% of 10% max
Top 10 holders
27%
Blocks 0 to 3
5 wallets 7% bought
Wallet clusters
1 cluster 8%

Holders vote with their bags: one flag per wallet per coin, weighted by tokens held for at least 15 minutes. Five holders with 5% of supply between them flag the coin, and the dev's grade turns to Flagged. No bag, no vote.

Live

Launched alone.

All coins
  • 0Coins live
  • 0Launched today
  • 0Snipers tripped
  • 0Outside buys in block zero
No coins yet.The first one lands alone. It could be yours.Launch a coin
0.03 SOLflat, per launch. Covers the create, the private bundle and the tripwire's 2%.
Creator feesThe deployer is every coin's creator; its share is swept every 5 minutes and funds the tripwire.
Refunds4 failed tries or 10 minutes, and the fee returns to the wallet that paid it. No ticket needed.

The fine print, plainly.

Can a bot still buy in block one?

Yes, block one stays open to everyone. The difference is what it buys: the tripwire's 2%, sold into that first buy at the top of the move.

Who holds the deployer's key?

The Yumi server. It needs the key to sign each create and each tripwire sale. For a launch your wallet signs a single SOL transfer to the deployer, and the amount in that transfer is the fee shown on the page.

What if my launch doesn't land?

Yumi retries with fresh bundles. After 4 failed tries or 10 minutes the fee is sent back to the paying wallet on its own, and the ticker and name are released. The refund waits until every bundle sent for that launch has expired, so a live coin and a refund never both happen.

What stops a copy launched straight on pump.fun?

Nothing on pump.fun itself. But every Yumi coin is created by the deployer, so the original is easy to prove on chain, and the clone check keeps copies off Yumi.

Where do the creator fees go?

The deployer is the creator of record on every coin, so pump.fun's creator share lands in its vault. One claim every 5 minutes sweeps all of it; that income funds the tripwire and keeps the fee low. The one thing outside Yumi's hands: pump.fun's takeover admin can move any coin's creator fees.

Is the 10% dev cap enforced on chain?

No. Yumi simply won't build a dev buy past 10% while the coin is on its curve. Your keys are yours, so the bag check is where the truth shows.

Which wallets work?

Phantom, Solflare, Backpack. Or spin up a browser wallet: the key stays on your device, locked with your passcode (AES-GCM, 310,000 PBKDF2 rounds).