Maya arrived at the hackspace the next afternoon with three hours of sleep, a cold cup of coffee, and the USB drive clutched so tightly in her palm that its edges left marks.
Dex was already at his whiteboard. He’d erased yesterday’s diagrams and drawn something new—a flow chart that looked like a maze of boxes and arrows, each one labeled with terms she didn’t understand. Ephemeral key pair. Diffie-Hellman. Shared secret. One-time address.
“You look terrible,” he said without looking up.
“Thanks.” Maya dropped into the folding chair. “I didn’t sleep. Every time I closed my eyes, I saw that transaction graph. All those lines connecting everything to everything.”
Dex turned around. His expression was softer than his words. “That’s good. Fear means you understand the stakes. Now let me show you how the protocol actually works—so you can stop being afraid of the technology and start using it.”
He tapped the whiteboard. “Stealth addresses. You’ve been using them for months without understanding them. That ends today.”
Scene 1: How Stealth Addresses Work
Dex picked up a blue marker and drew a large circle in the center of the board. “This is your public meta-address. Think of it as a mail slot on a wall. Anyone can see the slot. Anyone can drop a letter through it. But the slot doesn’t lead directly to your apartment.”
He drew a smaller circle inside the first. “Your meta-address is actually a mathematical formula. When a donor wants to send you coins, their wallet takes your meta-address and generates a one-time stealth address—completely unique, completely random-looking, and completely unlinkable to your meta-address without a special key.”
Maya frowned. “So every donor gets a different address to send to?”
“Exactly.” Dex drew arrows from the big circle to several smaller boxes labeled Stealth Address 1, Stealth Address 2, Stealth Address 3. “Donor A gets Address 1. Donor B gets Address 2. Donor C gets Address 3. None of these addresses look like they belong to the same person. In fact, they look like they belong to completely different people—or no one at all.”
He put down the blue marker and picked up a red one. “Here’s the magic part. Only you can tell that these addresses belong to you. Because when your wallet scans the blockchain, it uses a scanning key—derived from your private key—to check each address it sees. If the address was generated from your meta-address, your wallet recognizes it. If not, it ignores it.”
Maya watched the diagram take shape. “So the blockchain sees a bunch of random addresses receiving money. But my wallet sees all of them as… me.”
“Yes.” Dex drew a dotted line connecting all three stealth addresses back to a single box labeled Maya’s Wallet. “That’s the stealth protocol in a nutshell. The recipient publishes one public meta-address. Donors generate unique one-time addresses from it. Only the recipient can detect those addresses. To everyone else, each transaction looks like it went to a different, unrelated person.”
He stepped back. “Any questions?”
Maya had a thousand. “How does the donor know which address to send to? If it’s generated automatically, do they need special software?”
“Yes. Not all wallets support stealth addresses. The Safe House DAO only accepts donations from wallets that do. That limits our donor pool, but it’s worth it for the privacy.”
“And what prevents someone from generating a stealth address pretending to be me? Could someone trick a donor into sending money to a fake address?”
Dex shook his head. “The math prevents it. The stealth address is derived from your meta-address and the donor’s random data. Only the combination of both produces a valid address that you can detect. A fake address wouldn’t be recognized by your scanning key—so you’d never see the money, but the donor would think they sent it to you.”
Maya’s stomach dropped. “That’s terrifying. Donors could be sending money into a black hole and I’d never know.”
“That’s why we use wallets with built-in verification,” Dex said. “When a donor generates a stealth address, their wallet also generates a proof that the address is valid. You can verify that proof without revealing your keys. It’s complicated, but it works.”
He erased the diagram and started a new one. “Now let me show you how you actually use this.”
Scene 2: Maya Scans for Donations
Dex pulled up the wallet software on his laptop—the same one Maya had on hers, but configured with additional tools she hadn’t explored. “You’ve been using the basic interface. That only shows transactions to addresses you’ve explicitly created. But with the scanning tool, you can find all stealth addresses generated from your meta-address—even ones you didn’t know existed.”
He plugged the USB drive into his laptop. “This contains your scanning key. Watch.”
He clicked a button labeled Scan for Incoming Payments. A progress bar appeared. For three seconds, nothing happened. Then the screen populated with a list.
Found 7 stealth addresses with unspent funds.
Total value: 14.7000 coins (~$51,450.00 USD).
Maya’s mouth fell open. “Seven? I only knew about three.”
Dex scrolled through the list. Each entry showed a stealth address, an amount, a timestamp, and a donor address. Some of the donations were months old—from before she’d even joined the DAO.
“These are donations that arrived while you were using the basic wallet,” Dex explained. “The software received them, but your interface didn’t display them because you hadn’t told it to scan for stealth addresses. They’ve just been sitting there. Untouched.”
Maya felt like she’d been punched. “Fifty thousand dollars? We’ve had fifty thousand dollars this whole time and I didn’t know?”
“You didn’t know because you didn’t scan. That’s why I gave you the scanning tool three months ago.” Dex’s voice was gentle but pointed. “Privacy tools only work if you use them correctly. A stealth address that you never scan for is the same as a donation that never arrived.”
Maya buried her face in her hands. All those desperate fundraising emails. All those sleepless nights worrying about the landlord. All that time, the money had been there—hidden in plain sight on the blockchain, waiting for her to claim it.
“I’m an idiot,” she muttered.
“You’re not an idiot. You’re overwhelmed. There’s a difference.” Dex unplugged the USB drive and handed it to her. “Now you know. From now on, scan every week. Set a calendar reminder. Don’t let donations pile up.”
Maya took the drive and slipped it into her backpack. “Fifty thousand dollars,” she said again, almost to herself. “We can fund the safe house for a year. We can hire staff. We can—”
“We can also attract attention,” Dex interrupted. “Large, infrequent donations are easier to trace than small, frequent ones. A single donor sending ten thousand coins looks very different from ten donors sending one thousand each. Your ex—the Analyst—he’ll be watching for spikes. A sudden influx of fifty thousand dollars will light up his alerts like a Christmas tree.”
Maya’s excitement curdled into dread. “So what do I do? Not spend it?”
“You spend it carefully. Slowly. Through ring signatures and decoys—which we’ll cover next time. But first, there’s something else you need to understand about your keys.”
Scene 3: The View Key Vulnerability
Dex drew a new diagram on the whiteboard. This one showed three keys arranged in a hierarchy.
Private Key (Full Control)
- Can spend funds
- Can see all incoming transactions
- Can generate new stealth addresses
- NEVER SHARE
Scanning Key (Detection Only)
- Can see all incoming transactions
- Cannot spend funds
- SHARE ONLY WITH TRUSTED AUDITORS
View Key (Read-Only)
- Can see all incoming transactions (same as scanning key)
- Cannot spend funds
- Derived from private key, but less sensitive than scanning key
- STILL SENSITIVE—DO NOT SHARE WIDELY
“You already have your scanning key,” Dex said. “That’s what we used to find the donations. But there’s another key—the view key—that does almost the same thing. The difference is subtle but important.”
He turned to face her. “The scanning key is tied to your meta-address. It allows you to detect stealth addresses. The view key allows you to view the balances of those addresses once they’ve been detected. In practice, they’re often used together. But the view key is more dangerous to share, because it doesn’t require scanning—it just shows everything.”
Maya thought of the USB drive he’d given her yesterday, labeled VIEW. “So the drive you gave me yesterday…”
“Contains your view key. Not your scanning key. Your scanning key is still on your laptop—never on removable media.” Dex’s expression was serious. “If someone gets your view key, they can see every donation you’ve ever received. Every timestamp. Every amount. Every donor address. They can watch your balance grow in real time. They can’t spend your money, but they can know.”
Maya’s mind raced. “Could the Analyst get my view key?”
“Only if you give it to him, or if someone steals it from you. It’s not on the blockchain. It’s not broadcast anywhere. It’s just a file—like a password. Keep it safe. Keep it offline. Don’t email it to anyone. Don’t upload it to the cloud. Don’t even say it out loud near a device with a microphone.”
“Paranoid much?”
“The Analyst works for a chain surveillance firm. He has access to tools that can correlate voice recordings with blockchain activity. Yes, I’m paranoid. So should you be.”
Maya tucked the USB drive deeper into her backpack. “Okay. So view key is sacred. Scanning key is sacred-adjacent. Private key is never spoken of. Got it.”
“Good.” Dex glanced at the clock. “We have time for one more thing before you go. I want to show you what the Analyst is doing right now.”
Scene 4: The Analyst’s Move
Dex turned his laptop so Maya could see the screen. He’d pulled up a simulation of a chain surveillance dashboard—the kind the Analyst would use at his firm. The interface was cold and corporate: dark blue backgrounds, crisp white text, charts that tracked transaction volumes over time.
“I’ve built a model of his likely workflow,” Dex said. “Based on公开 information about how these tools work. Watch.”
He entered a search query: Safe House DAO. The dashboard returned zero results—no wallet addresses, no transactions, nothing. “That’s good. The DAO’s name isn’t on the blockchain. But donors sometimes include memos. Memos are visible to everyone.”
He clicked over to a different tab: Memo Search. He typed emergency housing. The screen populated with thirty-seven transactions, each one containing that phrase in the memo field.
“See these?” Dex pointed at the list. “These are all donations where the donor wrote ‘emergency housing’ or something similar. Anyone can search for memos. Anyone can build a list of addresses that receive donations for emergency housing.”
Maya felt sick. “So every donor who wrote a kind message—everyone who said ‘stay safe’ or ‘hope this helps’—they basically tagged our wallet for him?”
“Yes. That’s why I tell donors to leave memos blank. But not everyone listens.” Dex clicked on one of the transactions. It led to a stealth address—one of Maya’s. “He doesn’t know this is your address. But he knows it received a donation for emergency housing. And if he sees five more donations to the same address—or to addresses that cluster with it—he’ll start building a profile.”
He pulled up another screen. This one showed a list of donor addresses—people who had given to multiple “emergency housing” wallets. “He’ll look for donors who give frequently. Then he’ll look at their other donations. Then he’ll build a web. Eventually, he’ll find the safe house cluster.”
Maya’s voice was barely a whisper. “How do we stop him?”
“You can’t stop him from searching. But you can make his search results useless.” Dex closed the dashboard. “By the time we’re done, every transaction in your cluster will look identical to every other transaction on the blockchain. No patterns. No memos. No easy links. He’ll have to work for every scrap of information—and eventually, he’ll run out of time or money.”
He stood up. “But that’s for next week. For now, I need you to do something for me.”
“What?”
“Go home. Scan your wallet every day. Write down every stealth address you find. And for the love of cryptography, do not spend anything until I teach you how to do it safely.”
Maya nodded. She stood up, slung her backpack over her shoulder, and headed for the door.
Scene 5: Maya’s Mistake
The walk back to her apartment took forty minutes. Maya spent every one of them thinking about the fifty thousand dollars sitting in her wallet, untouchable, like a treasure chest at the bottom of the ocean.
The landlord needs money by Friday. The security system is outdated. The families need winter coats.
She knew what Dex had said. Do not spend anything. But Dex wasn’t the one getting eviction notices. Dex wasn’t the one watching the temperature drop and the heating bill rise.
When she got back to her apartment, she sat on the mattress and pulled out her laptop. She opened the wallet software—the basic interface, not the scanning tool—and looked at her main address balance.
$347.22.
The safe house’s actual operating account, the one she used for daily expenses, was almost empty. The stealth addresses held fifty thousand dollars, but she couldn’t touch them without Dex’s help. Or could she?
She pulled up a tutorial online: How to spend from a stealth address. The instructions seemed simple enough. Copy the stealth address. Paste it into the “send from” field. Enter the recipient’s address. Sign the transaction.
It can’t be that hard, she thought. It’s just a transaction.
She selected one of the smaller stealth addresses—the one with 0.5 coins, about $1,750—and pasted it into the send field. She entered the landlord’s wallet address. She typed the amount: 0.5 coins.
Her finger hovered over the “Confirm” button.
Dex said not to.
Dex isn’t the one who’ll be homeless if we miss this payment.
She clicked “Confirm.”
The wallet asked for her private key. She entered it. The transaction broadcast.
For a moment, nothing happened. Then the wallet refreshed. The 0.5 coins were gone. The landlord’s address showed a pending transaction.
Maya exhaled. That wasn’t so hard. She’d spent from a stealth address. She’d paid the rent. Everything was fine.
Then she looked at the transaction details on the blockchain explorer.
Sender: sv1qqpz7h4l8k3n2m9x6w5v4u3t2s1r0q9p8o7i6u5y4t3r2e1w (the stealth address)
Recipient: The landlord’s address (clearly labeled as a property management company)
Change: sv1q2w3e4r5t6y7u8i9o0p1a2s3d4f5g6h7j8k9l0z1x2c3v4b (a new address, automatically created)
Maya stared at the change address. She didn’t control it—not consciously. But the wallet had created it automatically, and the blockchain showed that whoever controlled the stealth address also controlled this new address.
She’d just created a link. A permanent, unbreakable link between her stealth address and a brand new address that she now owned.
And anyone watching the landlord’s address—anyone who knew that the landlord managed properties for survivors—could see that someone had paid the rent. Someone who used a stealth address. Someone who was trying to hide.
Her phone buzzed.
You spent something, Dex’s message read. I saw the transaction. We need to talk. Now.
Maya’s hands trembled as she typed back: I’m sorry. I had to pay the rent.
A long pause. Then: Come to the hackspace. Bring your laptop. We’re doing ring signatures tonight.
Before she could respond, another message appeared—from a number she didn’t recognize.
I see you, Maya. I see your change address. You just made a mistake.
The Analyst.
Maya dropped the phone like it was on fire. It clattered against the floor and slid under the bed. She didn’t pick it up. She didn’t have to. She already knew what it said.
He didn’t know her name. Not yet. But he knew someone had made a mistake. And he would follow that mistake all the way to her door.
Table of contents:
Introduction
Chapter 1: The Public Ledger
Chapter 2: A Glass House
Chapter 3: The Stealth Protocol
Chapter 4: The View Key <<<<<< NEXT
Chapter 5: The Linkability Flaw
Chapter 6: The Stalker’s Trace
Chapter 7: The Ring Signature
Chapter 8: A Decoy Mix
Chapter 9: The Tracing Resistance
Chapter 10: Anonymous, Not Invisible
