Shade (@_shadesol) header
Shade (@_shadesol) profile picture

Private launches, Ghost Buys, Dark OTC, airdrops, Mystery Bags, Glass Keys, rewards. On Helius Privacy Rings $SHADE 12bTtDLSegj1rw2oxXWYm63Rxw5QxkVSXDHCEvRShaDe

Joined November 2026
Photo by Shade (@_shadesol)Photo by Shade (@_shadesol)Photo by Shade (@_shadesol)Photo by Shade (@_shadesol)Photo by Shade (@_shadesol)Photo by Shade (@_shadesol)Photo by Shade (@_shadesol)Photo by Shade (@_shadesol)Photo by Shade (@_shadesol)Photo by Shade (@_shadesol)
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
Today, Solana changes forever Introducing Solana Privacy Rings - encryption at the speed of Solana Rings are programmable, onchain environments for encrypting money, markets, and finance - without ever leaving Solana Now live on mainnet.
30
11
5
66
7,078
You asked for a Telegram community, so we made one. Over the past ten days the same requests kept landing in our replies and DMs: somewhere to ask how a private launch works before you buy a pass, somewhere to say "this doesn't look right" without posting it in public, and somewhere to talk with the team and with each other in real time. X is good for announcements. It isn't built for a conversation that goes back and forth. What the group is for → Questions about using Shade: passes, the vault, Ghost Buys and the private buy, Dark OTC, airdrops, Mystery Bags, Glass Keys → Help when something looks off, answered by the people who built it → Talking through what ships and what should come next on the roadmap → Feedback that changes the product A few house rules, because privacy is the point → Shade will never ask for your seed phrase, a wallet signature or a claim link. Anyone who does isn't us → Don't post claim links, bag links, OTC links or vault details in the group. A link is cash to whoever opens it first → Security reports still go privately, by DM to @_shadesol Join here: t.me/+BH5tIGl3uGw1OTRk
1
2
33
Recorded on shadesol.fun: a minute on the new Updates page. What you'll see: - The top line: every change since the first launch on 10 Nov, with the minute it reached mainnet in UTC. 39 releases so far. - The Security page entry at 00:35 UTC on 21 Nov, then the private buy at 00:14 UTC, where we open the list of what was released with it: outside tokens through Jupiter, Buy more privately on a launch's success screen, the private buy link on token pages, and per-visitor limits on buys, sells and quotes. - Copy link on that entry, for pointing someone at exactly one release. - The Fix filter: 10 releases, from the stronger relay protections down to the clearer advice for anyone selling a dev bag, which now says to keep the SOL on the deployer. - The Feature filter, scrolled all the way back to 10 Nov and the release that started it all: private launches from a never-funded stealth deployer. We built this page so the question of whether something is live always has a precise answer, and so a change in advice can't slip past unnoticed. When something on the roadmap ships, it gets an entry of its own on this page. shadesol.fun/app/updates
1
26
The private buy can buy tokens Shade didn't launch, through Jupiter. That raises a fair question: what stops a bad route from costing you or the relay? Shade treats Jupiter's instructions as untrusted input. Before the relay signs a chip's buy, it checks that: - the transaction uses only the programs a swap needs - exactly the chip's SOL is wrapped and spent, from the relay's own wrapped-SOL account - the swap pays the ghost wallet, and carries no platform fee - the on-chain floor is no lower than the minimum you set Then it simulates the signed transaction, and refuses unless the ghost receives at least your minimum, the relay spends no more than the chip's price and keeps its reserve, and none of the relay's own token accounts loses anything. If the quote slips beyond your slippage setting, nothing executes: the transaction fails on chain, and the chip is still yours for another try. On the token itself: Shade doesn't vet tokens it didn't launch. What it does is show you a mint's freeze authority, permanent delegate, transfer fee or transfer hook before you buy, and refuse mints a ghost could never sell. One more party to know about: Jupiter sees each of these swaps, the ghost's address and the amount. It doesn't see your wallet, your vault, or which vault a ghost belongs to. shadesol.fun/app/buy
1
2
44
Selling out of a private buy without walking the SOL back to your wallet. Same setup as the buy before it: a local dev server and Shade's dev-only 0.01 SOL test chip, with real mainnet transactions, picked up right where that video ended. What you see: - The private buy page lists Your ghost wallets for $BORN. Ghost #2 holds the 324,775.8 BORN it bought. - Sell all. Each ghost sells with its own key, signed in the tab. The relay fronts the network fee and the sale pays it back in the same transaction. The BORN goes for about 0.00948 SOL, which now sits on the ghost in public. - Keep it private offers three ways on: shield and recycle into chips, only shield, or send it to your wallet, which comes with a warning that it ties the ghosts to you. - We press Only shield. Ghost #1 still held SOL from an earlier test sale, so two ghosts deposit into Privacy Rings, each signing its own: 0.00748 SOL and 0.00747 SOL, now private inside each ghost. 0.002 SOL stays public on each. Why not move it to the vault? Because on today's Privacy Rings both ends of a transfer are visible, and a ghost paying your vault would pair the two on chain for good. Leaving it in the ghosts, or spending it later as chips for the next buy, keeps it away from the wallet you started from. shadesol.fun/app/buy
3
112
Before you press Buy on Shade's private buy, a panel tells you exactly what the chain will show for that buy. Here it is in general form. Public: - The SOL your wallet sends to your vault, and the vault's deposit into Privacy Rings. Both show the address and the amount. Putting SOL in from a public wallet is always visible. - One Privacy Rings payment per chip, from your vault to Shade's relay, the address every chip and pass buyer pays. How much, and what it buys, stay private; who paid whom does not. - Each ghost buy. The relay buys a fixed chip size of the token for a new address that nobody ever funded. Each ghost is recognisable as one, because the relay paid. Hidden: - The link between any chip payment and any buy, and which vault the ghosts belong to. The relay signed blinded chips, so not even Shade can match a chip it sees spent to the payment that bought it. Can still link them: - Timing and amounts. A 1 SOL top-up followed by 1 SOL of ghost buys a moment later tells its own story. - Your IP address. Shade's server sees where each request comes from. What helps: keep SOL in your private balance instead of topping up for each buy, buy chips in common sizes well before you spend them (more people holding a size makes a bigger crowd), spread the buys over time, and use a VPN or Tor. shadesol.fun/app/buy
3
8
173
New page: Roadmap. What Shade runs today, and what it doesn't yet. A few rules we set for it: - No dates. Each item says what it is and what it waits on, never when. - Nothing appears on it until Shade has already said it in public, in the docs or a post. - Nothing moves to live until it has been tested on mainnet. Four stages: Being built: work under way. Empty today. Lined up: decided, not started. Two items: Dark OTC offers to buy, and refunding an unspent Ghost Buys chip. Waiting on others: Shade's part depends on a partner shipping something first. Two items, both waiting on Helius Custom Rings reaching mainnet: paying for a launch with no public hop, and bringing a launch's proceeds home privately. Live on mainnet: all 39 releases so far, grouped by product (private launches, Ghost Buys and Dark OTC, vault and payments, Glass Keys, explorer, and changes across Shade), each linking to its note on the Updates page. The items that aren't live each carry a How it would work link into the docs, so you can see what is public today and what would change, rather than taking a promise on faith. shadesol.fun/app/roadmap
1
1
1
6
167
Any token Jupiter can route, bought from fresh wallets. Here's the whole review you'd see before pressing Buy, recorded on shadesol.fun. In the video: - Paste a mint. We used JUP, which Shade didn't launch, so the page labels it Any token, bought through Jupiter, and shows a notice: Shade doesn't vet it, the relay buys it through Jupiter with your chip in one transaction, and refuses any route it can't check. - Type 2.6 SOL and raise the ghost wallets to five. The split becomes 1 + 1 + 0.25 + 0.25 + 0.1, one chip per wallet, with a quote per wallet and Shade's fee of 5 x 0.005 SOL. - Choose 30 minutes under Timing. The chain panel follows: the relay now buys at random times over the next 30 minutes instead of within about a minute. - Read What the chain sees. The SOL leaving your wallet, and the vault depositing it, are public with amounts. Five chip payments from the vault to the relay are public, amounts hidden. The relay's buys for five new addresses are public. Which vault paid is hidden. - The closing lines: Shade's server sees the IP address of each request, so it could tell the buys came from one visitor. A VPN or Tor keeps that address from being yours. We stopped with the cursor resting on Buy privately. Nothing was bought, and no third-party token was bought for this video. shadesol.fun/app/buy
1
2
3
119
New page: Updates. Every change to Shade, with the minute it reached mainnet. The list runs back to the first launch on 10 Nov. 39 releases so far: 21 features, 10 fixes, 8 site changes. Each entry has: - the date and the minute, in UTC, that it went live on mainnet, not when it was written - a tag (feature, fix or site), with a filter at the top to show only one kind - a Copy link button, so you can point someone at a single release instead of a whole page - where it applies, a short list of the smaller changes released with it, behind a button - a link straight to the thing itself, or to the part of How it works that explains it Why bother: privacy software asks for a lot of trust, and part of earning it is being exact about what is running right now. If someone asks when the private buy went live, the answer is 00:14 UTC on 21 Nov, and there's a link for it. If a fix changed advice you had been following, the change is listed with the time it happened. The roadmap feeds into this page too. Once something on it ships, it leaves the roadmap's waiting list and points to its own entry here. shadesol.fun/app/updates
1
1
3
84
Shipped: stronger protections on Shade's relay. The relay is the part of Shade that fronts network fees, so your stealth deployer and your ghost wallets never need funding from you. That makes it the piece most worth protecting, and this release closes the high-severity findings from Shade's internal review. What changed, in plain terms: - Every launch, sell and claim the relay signs is simulated first, and refused if it would leave the relay worse off. - A pass funds at most one pair, and the relay buys the pair's asset only once that is settled. - A sponsored claim repays, in the same transaction, any account rent the relay fronts. - Each visitor now has their own request limits, including limits on private buys, sells and quotes, so one busy client can't use up an allowance meant for everyone. - The request proxy forwards only the methods the app uses, within a per-visitor allowance. - Lookups of addresses with nothing on them are cached for a few seconds. Why this matters to you and not only to us: a relay that can be drained is a relay that stops sponsoring sells and claims. Keeping it whole is what keeps a never-funded deployer workable for every creator on Shade. Each finding sits on the Security page with its severity and status. On the Updates page this release is stamped 00:35 UTC on 21 Nov, next to the Security page that went out with it. shadesol.fun/app/security
1
3
90
Watch a real private buy, start to finish, on Solana mainnet. Recorded on a local dev server running Shade's live code with the development-only 0.01 SOL test chip, so we could show a full buy with test funds. That chip doesn't exist on shadesol.fun, where the smallest chip is 0.1 SOL. Every transaction in the video is real. What happens: - We paste the mint of BORN, a test token Shade launched, and the page recognises it as a Shade token on its bonding curve. - We type 0.01. The card on the right shows the split: one ghost wallet, Shade's fee of 0.005 per chip, what the wallet sends and what is already in the private balance. - Before pressing anything we read What the chain sees. The top-up is public. The chip payment from the vault to Shade's relay is public, its amount hidden. The relay's buy for a fresh address is public. Which vault paid is hidden. And in yellow, the honest part: done in one go, a top-up followed by buys moments later can be tied together by timing. - Buy privately. One transfer approved, then the checklist runs: SOL to the vault, into the private balance, the chip paid for privately, the relay's blind signature, the ghost buy. The wait is sped up. - Done: 324,775.8 BORN on ghost #2, a wallet nobody funded. The vault was unlocked just before recording, which is the other of the two wallet prompts. shadesol.fun/app/buy
1
1
5
121
New page: Security. What has been checked on Shade, and by whom. Every launch, trade, claim and private payment on Shade runs through on-chain programs other teams wrote. The new page lists each one, what Shade uses it for, and the audits its makers published, with a link to every report: Meteora Dynamic Bonding Curve: Offside Labs, Zenith, Code4rena, OtterSec Meteora DAMM v2: Offside Labs, Zenith, OtterSec Helius Privacy Rings: Certora, zkSecurity Jupiter Lock: OtterSec, Sec3 Jupiter Aggregator v6: Offside Labs Token-2022 and SPL Token: Zellic, Asymmetric Research, Trail of Bits, Neodyme, Kudelski That's 7 of the 8 programs. For the eighth, the Associated Token Account program, no published audit was found, and the page says so instead of leaving a gap. Then the part we want to be just as clear about. No outside firm has reviewed Shade's own code yet: the relay, the API routes and the browser cryptography. What the page shows instead is Shade's internal review, finished on 21 Nov: 13 findings, each with its severity, 11 of them fixed and named by the commit that fixed them. The two still open are informational. The page calls it what it is: an internal review, not an audit. The last section points to How it works for what Shade can and can't see, because a code audit answers whether the code does what it should, not what the operator can observe. shadesol.fun/app/security
3
117
New on Shade: the private buy. Type one amount, and Shade buys a token for you across up to eight fresh wallets that no wallet ever funded. It's live on mainnet now, under Buy in the app header. How it runs: 1. Pick a token: one of your own launches, or paste any mint Jupiter can route. 2. Type an amount in SOL. Shade splits it into chips in four fixed sizes (0.1, 0.25, 0.5 or 1 SOL, with a 0.005 SOL fee on top of every chip) and spreads them over ghost wallets. 3. Press Buy privately. Your wallet shows at most two prompts: a message to unlock your vault, and one transfer if your private balance is short. Everything after that is signed in your tab by keys derived from your vault. 4. Shade's relay buys for each ghost. Each chip carries a blind signature, so Shade itself can't pair a spent chip with the payment that bought it. 5. When you're done, Sell all brings it back in one press, and Keep it private shields the SOL inside the ghosts instead of sending it home. What stays public, said plainly: your top-up and the vault's deposit into Privacy Rings, your vault paying Shade's relay, and each ghost buy with its size. What's hidden: which payment paid for which buy, and which vault owns the ghosts. Timing can still connect them, so the page can spread the buys over 10, 30 or 60 minutes. Beside the button, a panel called What the chain sees spells all of this out for the exact buy you typed, before you press anything. shadesol.fun/app/buy
1
3
107
Who Shade isn't for, yet. Better to say it here than have you find out after you've used it. → If you need to hide who you paid. On the Default Ring both ends of every private transfer show; only what moved, and how much, is encrypted. Helius has announced rings that hide the parties as well, and Shade plans to use them once they ship → If you need a big crowd today. A ghost buy or a pass blends you in with others who bought that same size. Early on that's a small number of people, and timing can narrow it further → If you want to bring launch proceeds home privately. What a stealth deployer earns is public, and so is wherever it goes next. For now the private option is to leave it where it is → If you can't keep a link to yourself. Bag links, airdrop links, gift links and Dark OTC offers are bearer links. Whoever opens one first can use it → If you never want a service holding your value. Shade's relay holds what you've prepaid until you use it, and reward shares sit with keys Shade's server can derive until they're claimed → If you want to change your mind after launch. The fee, the metadata, an alias signature and a lock are all fixed on chain once the token exists → If you want rewards on tokens you keep shielded. Rewards follow public balances What it is for: hiding how much moves, cutting the funding trail from a person to a launch, buying and selling without a wallet history, paying people without publishing what each got, and proving one thing without showing the rest. shadesol.fun/app/docs#threat…
2
2
85
Before you sign anything on Shade, the dialog tells you what will be public. Here are eight of those lines, as they appear in the app. Funding your vault: "This transfer is public. Anyone can see that your wallet sent this amount to the vault, so the vault is linked to you." Shielding: "Public: the vault deposited this amount into Privacy Rings. Hidden: everything it does with that SOL afterwards, including which passes or transfers it pays for." A private airdrop: "Public on chain: your vault paid each recipient or link key, and when. Hidden: every amount, and which token." Mystery Bags: "Public on chain: your vault paid this many fresh keys, and when. Hidden: every amount, and whether it's SOL or a token." Funding a Glass scope: "Whoever gets this scope's link learns its address, so they can see your vault funded it." Pay with receipt: "Reveals: This one payment: who was paid and how much." Then, in amber: "A link can't be revoked." A holder reward: "Public: the deployer shielded some SOL, paid 3 fresh keys privately, and announced reward #4 with a memo. Hidden: each share and the total." Claiming an airdrop link: "Until it's claimed, anyone holding this link can claim it anywhere, so claim it now." Why put it there and not only in the docs: the moment before you sign is the only moment the line can change what you do. A privacy tool that only lists its limits on another page is asking you to remember them at the worst time. The launch form goes furthest. Its "What the chain will show" panel stays on screen the whole time and rewrites itself as you choose a fee, a dev buy, a lock or an alias. shadesol.fun/app/vault
1
2
142
Everything you can do on Shade without connecting a wallet at all. Look → The board, every token page, its chart, trades and holders, read from chain → The explorer: the live feed of every launch, trade, claim and graduation, and any address or signature explained in plain words, including whether a creator was ever funded before its launch → The docs, end to end, including what each tool leaves public Check → A creator alias proof, on the verify page, in your own browser. The check is a plain Ed25519 signature anyone can redo → A Glass watch link, unspent proof or receipt. One static page does the checking in your browser, and the part after the # never reaches a server Receive → An airdrop link. It shows your allocation and claims to the wallet it names, and you don't have to connect that wallet. The fee comes out of the link → A Mystery Bag. Opening it needs no signature. Claim it to any address you paste, with no SOL of your own, and the bag covers its fee Where a wallet does come in → Claiming into a Shade vault: your wallet signs one message to unlock it, and that signature opens the vault, nothing else → Launching, buying, shielding, and anything else that moves your own money That split is deliberate. The parts that only read or verify run without an account and without asking who you are. The parts that spend need your signature, and nobody else's. shadesol.fun/app/explorer
1
104
What a token can do on Shade without ever leaving the ring. Every Shade token gets a Privacy Rings interface right after it launches, so it can be shielded from its first minutes. Once tokens sit in a shielded balance, most of what you'd want to do with them happens without unshielding. Still private the whole way → Send privately to any shielded address. What moved and how much stays encrypted, while both keys and the time show → Sell by Dark OTC. An offer sells shielded tokens for SOL, and the take settles in one transaction with what was sold, how much and for what all encrypted → Airdrop it. A private airdrop can pay a list in a Shade token, and a token claim link carries 0.0025 SOL so the person claiming needs none → Drop it in Mystery Bags. A token bag also gets 0.0025 SOL for its own claim fee and token account, and what's left goes to whoever opens it → Sell from shielded, on the curve of a token paired with SOL. A single transaction withdraws and sells, and the relay's fee comes out of the proceeds. Public like any trade from that key: amount, price, proceeds What needs the tokens public first → A dev-buy lock. A lock's escrow holds tokens in the open, so a launch can lock its dev bag or shield it, not both → Holder rewards. Shares follow public balances, and shielded tokens sit in a program-owned vault, so they earn none → Selling after graduation, or on a non-SOL pair. Unshield, then sell as usual The shield itself is always public: the depositing key, the token and the amount. What it buys you is everything after. shadesol.fun/app/docs#born-s…
3
6
350
Questions people ask before their first private payment, answered in plain words. Do I need a new wallet? No. Any Solana wallet works. It signs one message to open your vault, which isn't a transaction and costs nothing, and later it tops the vault up. That's all it's asked to do. Is the vault one more thing to back up? No. It comes back from that same signature, on any device. The catch is the other way round: anyone who gets that signature gets the vault, so only sign it on shadesol.fun. Why does my vault keep some SOL public? To pay network fees and rent. Shielding leaves 0.002 SOL public for that, and everything above it can go private. Can Shade move my money? Not your vault's. Nothing leaves it without a signature from your vault key, and that key exists only in your browser. Shade does hold value you've prepaid until you use it: passes you haven't launched with, chips you haven't spent, and reward shares nobody has claimed yet. Can I pay someone who doesn't use Shade? Yes. A private airdrop sends them a claim link they can use with an empty wallet, and a Mystery Bag link works the same way for a one-off gift. Claimed to their own wallet, that one amount shows, since a withdrawal is public. Claimed into a Shade vault, it stays private. What does the person I pay see? That your vault paid them, and how much. Anyone else sees that your vault paid them, and not how much. What if a transfer fails halfway? A private transfer either lands as a whole or doesn't land, and nothing is spent when it doesn't. shadesol.fun/app/docs#vault
1
1
6
191
Keeping your own records when your balance is encrypted. Privacy shouldn't mean you can't show your numbers to the people who need them. What you can produce, and for whom → Your private history. Every shield, payment and receipt, decrypted in your browser with the vault's viewing key. It's rebuilt from chain, so unlocking on another device brings it back → A receipt for one payment. Pick any payment in the Receipts list and make its link. Whoever opens it sees that transaction alone: who was paid and how much, plus your own change if the note was bigger than the payment. Pay with receipt sidesteps that by paying from an exact-size note → A watch link for one scope. Give an accountant or a partner a Glass scope's watch link and they can follow that scope's balance and its payments, including ones you haven't made yet. Not your vault, not your other scopes → An unspent proof. Show that one note of a set size is still there, checked live against the chain What doesn't exist, on purpose → An account history on Shade's side. There's no database of your activity, so there's no list for anyone to ask us for, and none we could hand you either → A way to revoke a link. Whoever has a watch link keeps it, so fund a scope for that audience and move funds out if the relationship ends Habits that make it easy → One scope per audience, labelled in your browser → Pay with receipt for anything you might need to prove later → Keep airdrop lists yourself. They stay sealed in the browser that sent them; on another device, paste the list again to see which link was whose shadesol.fun/app/docs#glass
1
3
99
EXAMPLE: one creator alias across a year, and what it adds up to. January. The first launch goes out with no alias. Nothing public ties it to anything else, which is the default. March. The second launch gets a new alias, a key the browser derives from the vault seed. It signs the line shade-alias:v1 plus the mint plus a name, "duskworks". That signature is written into the token's Arweave metadata, which is permanent. The board starts listing the token under that alias, but only because the signature checks out for that exact mint. June. A third launch under the same alias, this time named "dusk". The alias page now shows "dusk", the name its newest launch signed, and lists all its launches with live market data. Names are public and not unique, so buyers who care compare the key and its coloured dot, not the name. August. Someone asks if they're really behind it. They sign a proof message as the alias on its page, naming the place and the date, and anyone can check it on the verify page in their own browser. Proofs use a different prefix, so a message they're talked into signing can't pass as a launch claim. October. They want a clean slate, so they start a second alias. Nothing links it to the first unless they link it themselves, for example by announcing both from one account. What the year cost them: every launch under the first alias is tied to the others for good. Habits across them compound, and tracing any one of them traces the rest. What it never touched: their wallet, their vault, and the January launch. shadesol.fun/app/docs#aliase…
1
2
94
Follow one private payment from your click to the other person's screen, and who gets to see what along the way. 1 → Your browser syncs your notes. It asks Helius's Rings indexer for them directly, so Helius sees your IP and which tags it's asked about, the way any wallet sync works. It never gets a key that opens them 2 → It builds the proof. The inputs go to Helius's prover, which runs in an AWS Nitro enclave with attestation, and the Rings client checks that attestation against Helius's signed policy before it sends anything. The prover sees the amount and the nullifier key it needs. Not your spending or viewing keys 3 → It signs. Your vault key, derived in this tab from one wallet signature, signs the Solana transaction. Your wallet app isn't asked 4 → It sends. The transaction goes through Shade's RPC relay, so Shade's server sees your IP and the transaction, and the RPC provider sees Shade's server rather than you 5 → It lands. Anyone reading Solana now sees that your vault paid that vault, and when. What moved, and how much, is encrypted 6 → The other side opens it. Their browser finds the new note with their own keys and decrypts it, along with any memo you attached Three things worth doing with that map → Use a VPN or Tor. Steps 1 and 4 are where an IP shows, and it's the easiest thing to correlate → Guard the unlock signature as you would a seed phrase. Everything in step 3 comes from it → Remember step 5 is public by design. The amount is what's private, not the edge shadesol.fun/app/docs#trust
1
1
97