
Private launches on Solana from a stealth deployer no wallet ever funded. Built on Helius Privacy Rings. $SHADE: 12bTtDLSegj1rw2oxXWYm63Rxw5QxkVSXDHCEvRShaDe
Joined November 2026
- Tweets160
- Following7
- Followers169
- Likes14
Pinned Tweet
Privacy Rings made private payments native to Solana.
We used them to fix the oldest problem in memecoins: every launch leads straight back to the dev's wallet.
Introducing Shade. Launch a coin with no wallet trail.
The problem
Every Solana launch is a public map. Fund a deployer and anyone can follow the SOL back to you: bubble maps, sniper bots, copy-traders. Hiding it meant CEX hops and burner chains, and those still leave a trail.
How Shade fixes it
1. Shield SOL into Helius Privacy Rings, where amounts are hidden
2. Pay for a launch pass from your shielded balance
3. The pass is blind-signed, so not even Shade can tell which payment bought it
4. A fresh deployer no wallet ever funded creates your coin
On-chain, your coin's creator has no funding source. Shade's relay pays the rent and makes your dev buy in the same transaction as the launch, so nobody can buy before you. No transaction connects your wallet to the token, its pool or its dev bag.
After launch, your stealth deployer still never needs SOL. Shade sponsors its sells and creator-fee claims, and you can recycle the proceeds into a pass for your next launch, unlinked from this one.
And it's fast. One page, one button: shielding, pass and launch run in under 30 seconds. You set the trading fee, 2% to 10%, and keep about half of it.
Every step is checkable: Shade's explorer shows what a launch reveals on-chain, and what it doesn't.
Private launches are finally possible on Solana, at Solana speed.
Built on Helius Privacy Rings and Meteora.
shadesol.fun
Holder rewards on Shade.
Launched a token here? Open its page with your vault unlocked and press Reward holders. Share SOL from your stealth deployer with your top 50 holders, split by how much each one holds.
→ every share is paid privately, so the chain shows neither the total nor any one share
→ holders claim on the token page by signing a message, not a transaction, and need no SOL
→ claim into a Shade vault to keep the amount hidden; a claim to a public wallet shows it
→ sold after the snapshot? You keep your share
→ 30 days to claim, counted from a block time the chain sets
→ then the creator reclaims what's left into their vault
Only the token's own deployer can announce a reward, so nobody can fake one for your token.
Until a share is claimed, it sits with keys Shade's server derives. The docs say exactly what that means.
1
51
Private airdrops on Shade.
Paste a list, one address and amount per line, and pay your team, KOLs or early supporters SOL or a Shade token from your vault's private balance.
→ every amount is encrypted on chain
→ a Shade shielded address is paid straight into its vault, nothing to claim
→ a wallet address gets a one-time claim link, and claiming needs no SOL
→ one proof per batch of up to 13 outputs
→ a closed tab or a failed batch resumes from the chain alone
→ unclaimed links can be reclaimed into your vault any time
The list never goes to our servers. It stays sealed in your browser.
Public: who your vault paid. A link claimed to a public wallet shows its amount, so where it matters, ask for a shielded address. Links work like cash: send each one privately.
1
79
Dark OTC on Shade: a private deal by link.
Agree a deal with someone, say two million of a token for three SOL. Your vault makes an offer link. Send it to your buyer and they take it from their own vault.
→ one transaction, two Privacy Rings transfers: the tokens to the buyer's vault, the SOL to yours
→ both happen or neither does
→ which token, how many and the price stay encrypted on chain
→ no order book, no database: your vault rebuilds every offer from your wallet signature
→ cancel any time before it's taken, even after the link expires
Before the relay co-signs a take, it checks your signed terms, the expiry, and that the payment opens to you for at least the price.
Public: that the two vaults traded. Anyone holding the link can take the deal, so send it only to your buyer.
62
Three new features on Shade, live now.
Dark OTC
Sell a shielded token for SOL by link. The tokens and the SOL change hands in one transaction, and the token, the amounts and the price stay encrypted on chain.
Private airdrops
Pay a pasted list SOL or a Shade token from your vault. Every amount is encrypted, so nobody watching can tell who got the big allocation.
Holder rewards
Share SOL from your stealth deployer with your top 50 holders, split by holdings. Each share is paid privately and claimed with a wallet signature, no SOL needed.
All three run on Helius Privacy Rings. Who paid whom stays public; the amounts stay encrypted unless they're withdrawn to a public wallet.
OTC and airdrops are in your vault. Rewards are on your token page.
shadesol.fun/app
3
100
Shade's docs run to 18 sections. Where to start depends on why you're here.
Read these three whoever you are:
→ 1. What links a launch to a person
→ 9. Trust assumptions: who still sees what
→ 18. Check it yourself: verify it from the chain, not from us
Then by what you're doing:
→ Launching: 2 The vault, 4 Passes, 5 The relay, 6 Stealth deployers, 10 Fees, 11 Dev-buy locks
→ Holding: 3 Privacy Rings, 12 Born shielded
→ Giving: 7 Gifting a launch, 13 Mystery bags
→ Buying: 14 Ghost buys
→ Proving: 8 Creator aliases, 15 Glass Keys
→ Before you post about it: 16 Timing advice
17 covers what isn't live yet, so you know where the edges are.
shadesol.fun/app/docs
4
214
Shade has no on-chain program of its own. Every Shade transaction runs on programs that were already on Solana:
→ Meteora Dynamic Bonding Curve: the launch, every buy and sell, fee claims, graduation
→ Meteora DAMM v2: the pool a token moves to when it graduates
→ Token-2022: every Shade token is a Token-2022 mint with its metadata on the mint
→ Privacy Rings: deposits, private transfers, withdrawals
→ Jupiter Lock: dev buys locked at launch
→ System and Compute Budget: new accounts, SOL, priority fees
What Shade adds lives off chain: the vault in your browser, blind-signed passes, and a relay that pays.
So there's no Shade contract to upgrade, and nothing we ship later can change the terms of a token that's already live. Those are fixed on chain the moment its pool is created.
Builder note: why a Shade launch sometimes stops to ask you a question.
Passes come back from your seed on any device. Gift links don't: a gift exists only as a link, and it leaves no trace outside the browser that made it.
Say you sent a friend a gift link from your laptop, then launch from your phone. Your phone recovers the pass behind that link and has no way to know it's spoken for. Launch with it, and your friend's link stops working.
So when the only passes of your tier are ones this browser recovered, the review step asks:
→ Use a recovered pass: none of them is a gift
→ Buy a new pass for this launch
Or paste the links you sent on the vault page first, so they're marked.
A gift link works like cash. We'd rather ask once than spend someone else's.
Everything happening on Shade, live, in one place: shadesol.fun/app/explorer
The feed picks up every transaction that touches a Shade curve config and names it in plain words: launch with its dev buy, buy, sell, fee claim, graduation. New ones flash in on top every 5 seconds, and you can page back through older ones.
Above it: launches all time, plus trades and volume across the events it has scanned.
Paste a signature to open the transaction, or an address to open its page. Every program in a transaction is named, with a line on what it does, from Meteora's curve to Privacy Rings.
No account, no wallet, nothing to connect. It reads Solana directly.
3
129
Your Shade vault keeps a history only you can read.
Open the vault and every private move is listed with its amount:
→ Shielded
→ Received privately
→ Paid privately
→ Unshielded
→ Moved between notes
It's decrypted in your browser with your vault's viewing key. That key is derived from your unlock signature in the tab and never sent, so Shade can't build this list, and neither can an explorer.
What an explorer sees instead: your deposits and withdrawals with their amounts, and every private transfer with who sent it and who got it, but no amount.
You get a statement. Everyone else gets the who, with the numbers blacked out.
1
4
125
What happens after you press Launch on Shade. The checklist ticks off each step as it runs:
1. Uploading the picture and details
2. Sending SOL from your wallet to your vault
3. Moving it into your private balance
4. Buying a pass privately
5. Waiting for the relay's blind signature
6. Preparing the launch from a fresh stealth deployer
7. Signing in this tab and launching
Steps 2 to 5 only show up when they run. Vault already funded, pass already bought: they're skipped. Launching from a gift link: only 1, 6 and 7 run.
With a creator alias, the upload moves after the pass, because the alias signs the token's mint and that's only known at that point.
Picked a shielded dev bag? One more step runs at the end: the bag goes into your deployer's private balance.
1
5
196
The candles on a Shade token page don't come from a data vendor. They're built from the chain.
Each trade on a Shade pool is fetched and decoded once, then kept: a transaction never changes, so it's never read twice. Every candle opens where the last one closed, at the pool's price after each trade, so there are no gaps between bars.
→ Market cap in dollars, or price in SOL
→ Six resolutions: 1m, 5m, 15m, 1h, 4h, 1d
→ It opens on one that suits the token's age: 1m for the first three hours, 5m to day two, 1h to day fourteen, then 4h
→ Hover for open, high, low and close
→ Refreshes every 5 seconds, with the latest trades under it
Dollar figures use SOL's price from Jupiter, with a backup source. If prices go dark, only the dollar figures hide. The SOL chart keeps going.
2
137
The Shade launch form shows you two things while you type.
Your card on the board: picture, name, ticker, description, dev buy, and the badges buyers will see. Private launch and Stealth deployer on every card, plus your pair or alias if you chose one.
And what the chain will show:
→ Creator: a fresh stealth deployer
→ Its funding: none, ever
→ Rent and fees: paid by Shade's relay
→ Dev buy: the tier's amount, and whether it goes to a lock
→ Your wallet: not involved
Add a website, X or Telegram link and the card counts it in amber, and the chain list prints it in full. Of everything on that list, a link is the likeliest to point back at you, so the preview makes sure you see it.
1
3
258
On Shade, every cost of a trade is on screen before your wallet opens.
The quote updates as you type, worked out in your browser from the pool's live state:
→ You receive
→ At least: your minimum after slippage
→ Price impact
→ The fee, as a rate and in SOL
The fee line follows the live schedule. Buy in a token's first minute and you see the higher opening fee before you sign, not after.
Slippage goes from 0.5% to 10%, 5% by default, and this browser remembers your pick. Quick amounts: 0.1, 0.5, 1 or 2 SOL to buy, 25% to All to sell. Max keeps 0.01 SOL back for fees.
One approval, then a status line with a Solscan link once it lands.
A trade from your connected wallet is public. To buy without your wallet on the record, use a ghost buy.
Launched a token on Shade? Open its page with your vault unlocked.
A panel appears that nobody else gets: "Your stealth launch". Your vault re-derives your deployer keys in your browser and checks them against the token's creator, so the match happens on your device.
From that panel you can:
→ claim your creator fees
→ sell the dev bag
→ unlock it once its lock ends
→ see what the deployer holds
The relay pays the network fee each time, so the deployer never needs SOL.
It also names the one thing to avoid: proceeds stay on the deployer, and sending them straight to your wallet links you to the token. Shield them and move them to your vault from Portfolio instead.
Everyone else sees the public page. You see your controls.
7
177
You don't have to be anonymous to need privacy
Plenty of teams launch with their names on it. Public founders, doxxed devs, brands. They still have things that shouldn't be public: their personal wallets, what they've paid whom, how much the project holds and where it moves. A public face shouldn't come with a public bank statement
Shade separates the two on purpose:
→ The launch can be public about who's behind it. Sign it with a creator alias and post the alias proof from your official account. Buyers can verify the launch is yours, and see every other launch signed by that alias
→ Your personal wallet stays out of it. The token was created by a stealth deployer nobody funded, so there's no line on chain from the project to the wallet you live out of
→ Commitment can be proven, not just promised. Lock the dev buy in a Jupiter Lock escrow anyone can read
→ Team and vendor payments hide their amounts. Pay with receipt from your vault, and hand each receipt to whoever needs to see it
→ Treasury questions get answers without a statement dump. A Glass watch link for the community or an auditor shows one scope's balance and payments, and nothing else
Being known is a choice about your name. Privacy is a choice about your money. You can make both
shadesol.fun/app/launch
7
207
The list of apps on Privacy Rings keeps growing. The useful part isn't any single app. It's that they share one ring
On the Default Ring a shielded address is a shielded address, whichever app made it. That's why Shade's vault doesn't have to be an island:
→ Pay with receipt takes any shielded address, or any wallet registered with Privacy Rings, as the recipient. Not just other Shade users
→ The receipt is checked against the chain in the viewer's own browser, so the person you paid doesn't need a Shade account to verify it. There are no Shade accounts anyway
→ Shade tokens get their interface in the Privacy Rings program itself, one per mint, so their private side isn't tied to our site either
What a shared ring doesn't change: on the Default Ring every private transfer shows its sender and recipient, whichever apps they use. Paying someone from your vault links your vault to them. The amount is what stays hidden
And what more apps can change, over time: the more people hold private balances, the more ordinary a deposit into Privacy Rings looks. Privacy is a team sport. Every wallet that switches on a private mode makes "this address uses Privacy Rings" a little less interesting on its own
shadesol.fun/app
teapawt.net/CryptosR_Us/status/212…
MASSIVE: 🔒 Solana now has built-in privacy!
Helius just launched Solana Privacy Rings on mainnet, letting users hide transfer amounts and balances using zero-knowledge proofs. 🛡️
Decrypt, ORE and Aurora are already live, with Jupiter, Backpack and Squads working on integrations. ⚡
Public by default, private by choice. $SOL 🟣
6
169
Every move of a dev bag is a headline
Trackers set alerts on dev wallets. The moment the creator's tokens move, a bot posts it: "dev transferred 3% of supply". It doesn't matter whether the dev was paying a designer, funding a giveaway or splitting the bag between two of their own wallets. The alert lands first, the panic follows, and the explanation never catches up
On Shade, a dev can keep the bag where alerts can't read the details:
→ At launch, switch on "Shield dev bag". Once the launch lands, the stealth deployer deposits the whole dev buy into its shielded balance. The dev buy itself was public on the curve, like any buy
→ From there, a private send hides which token moved and how much. The chain shows that the deployer's key sent a private transfer, and to whom. Not "3% of supply"
→ The token page shows how much of the supply is shielded, read from chain, so holders can always see the total that's out of public view
Two honest trade-offs:
→ Shielding and locking are a choice. A lock's escrow holds the tokens in public so anyone can check it, and the launch form makes you pick one. Want to prove commitment? Lock. Want to move tokens without headlines? Shield
→ Selling isn't hidden. Selling from shielded withdraws and sells in one transaction, and that sale is as public as any trade. Shielding hides where a bag goes and in what amounts, not that a dev sold
Privacy for the person, transparency for the market. Holders can still see every sale
shadesol.fun/app/launch
1
3
117
Encrypted balances and tokens, in a wallet people already use. One thing worth knowing about the tokens part: a token can only go private once it has a Privacy Rings interface
An interface is two accounts in the Privacy Rings program for that mint: a registry entry, and a token vault that holds the shielded supply. Until someone creates it, there's no way to shield that token at all. Creating one is permissionless, costs about 0.0024 SOL in rent, and can't be undone
On Shade nobody has to think about it. Every new token gets its interface within about a minute of going live, and Shade's relay pays for it. So a Shade token can be held privately from its first day, not whenever someone gets round to it
The interface belongs to the Privacy Rings program, one per mint, not to Shade. It isn't tied to our site, and it stays on chain whatever happens to us. That's the point of building on shared infrastructure: the private side of a token isn't a walled garden
What private mode shows, honestly: shielding is a public deposit, and a token's total shielded supply is public, right on its page. What it hides is each holder's shielded balance, and the token and amount of each private transfer. The sender and the recipient stay visible
Early on, a new token's shielded supply is mostly the dev bag, if the dev chose "Shield dev bag" at launch. As holders shield, that total stops pointing at anyone in particular
shadesol.fun/app
teapawt.net/solflare/status/212206…
Today, we are taking one of those leaps that change how crypto functions.
Introducing Solflare Private Mode, powered by @helius.
> Encrypted balances & tokens
> Private payments & transactions
> All at Solana speed
You can now encrypt your money within Solflare.
Live now in your wallet 👇
3
118
Your wallet tells people when you sleep
Line up a wallet's transactions by hour and a pattern falls out. Nothing between 2am and 9am, a burst after lunch, quiet on Sundays. That's a time zone, a work schedule, sometimes a country. Lay it over the hours a certain X account posts, and two "unrelated" identities start to look like one person. No hacking involved, just timestamps that every block keeps forever
On a launchpad, timing is the leak that's left after the cryptography does its job. Shade hides amounts and breaks the link between a pass payment and a launch. It can't hide when things happen. What it can do is let you pull the steps apart in time, and it's built so you can:
→ Passes keep. Buy one on Sunday, launch with it on Thursday. Passes are rebuilt from your seed on any device, so they don't depend on the browser you bought them in
→ Chips keep too. Buy them in a quiet hour, spend them when the trade comes. A chip doesn't expire
→ Mystery Bag links work until they're opened, or until you reclaim them. Fund a drop today, hand the links out next week
→ Sponsored sells and claims mean you never top a deployer up first, so there's no tell-tale funding transfer minutes before the action
Habits that help:
→ Don't buy a pass and launch in the same sitting
→ Don't announce from your known account the minute a token goes live
→ Launch when others are launching. A crowd hides a timestamp better than anything we can build
The chain will always know when. Make sure "when" doesn't point at you
shadesol.fun/app/docs
3
108
"Developers can use encrypted onchain balances to build..." We took that literally and shipped four things on it. Some notes from building, for anyone starting now
1. Design around what the Default Ring shows. Amounts and assets are hidden, the sender and the recipient aren't. If your app's privacy depends on hiding who paid whom, it needs another tool. Ours is blind signatures
2. Every spend needs the owner's signature on the Solana transaction, so the keys have to live where the user is. We derive every key in the browser from one wallet signature, and nothing that can spend ever reaches our server
3. Change leaks. A transaction's viewing key opens every output, including what came back to the payer. If you're going to show someone a payment, split off a note of the exact amount first so there's no change to show
4. A relay can pay and be repaid in the same transaction. That's how a Mystery Bag claim works from a wallet holding 0 SOL: the relay fronts the fee, the bag repays it, and the relay simulates first and refuses unless its own balance comes out no lower
5. Indexers run a few seconds behind the chain. A link checker that doesn't know that will call honest data tampered. We look the transaction up on Solana itself: unknown there means altered, known means wait for the indexer
6. Composability is the point. Withdraw and sell in one transaction. Mark a chip spent and buy in one transaction. All of it, or none of it
None of this needed a new chain, a bridge or our own circuits. That's what made it possible to ship it fast
shadesol.fun/app/docs
teapawt.net/SolanaFloor/status/212…
BREAKING: @Helius launches @Solana Privacy Rings on mainnet, enabling encrypted balances and private transfers for $SOL and Solana tokens on the Layer1.
Developers can use encrypted onchain balances to build private swaps, staking and yield products, borrowing and lending, and conditional payments without leaving Solana.
3
301


























