S16 E8: Alex Romanov on Beam, MimbleWimble & Privacy
The audio keeps playing while you browse the site.
Read the transcript17,789 words, every line links to the minute it was said
Ask this episode
In January 2019, Bitcoin turned ten and two privacy coins launched almost back to back on the same idea. Beam went live on January 3, the genesis block's anniversary. Grin followed on January 15. Both implemented Mimblewimble, a protocol described in 2016 by someone calling himself Tom Elvis Jedusor (Lord Voldemort's name in the French Harry Potter books), and for a few months Mimblewimble was the hottest thing in crypto, a design so elegant that people wondered aloud whether it threatened Bitcoin.
Six years later, most Bitcoiners remember two things about Mimblewimble, neither of them good: a heavily pre-mined token called MimbleWimbleCoin, and a November 2019 blog post claiming that Grin's privacy could be broken for 96% of transactions. So I invited Alex Romanov, the CTO of Beam, to explain what the protocol actually does, what that attack really showed, and why Beam now looks less like Grin and more like a private Ethereum.
I had downloaded the Beam desktop wallet and synced its built-in node the night before, so a good chunk of this livestream was me clicking around the interface on screen and asking Alex what each button does. It was the first podcast he had ever prepared written notes for, he told me, because it was going to be long enough to get past Mimblewimble 101.
An Accidental Crypto Career
Alex was not a crypto native. In 2018 he was simply looking for his next job in Israel, and his friend Guy Corem, who had been in crypto mining since around 2013, pitched him an idea. "I said, wait a second, I don't know absolutely anything about it," Alex recalled. "Actually, the first crypto I ever held was Beam that we launched."
Guy's idea was a better privacy coin than what existed in 2018, which mostly meant Monero and Zcash. Both had large blockchains that made new nodes slow to sync, and Zcash had "this huge amount of non-private transactions in the blockchain, which was a huge detriment to the entire privacy." Mimblewimble looked like a good compromise between privacy and scalability. The name, Alex explained, began as a joke on Grin: a grin is a smile, and a beam is a wider one.
Beam was VC funded and did not open its source code until about six months into development, which made it the villain next to community-run Grin. He remembers being called "scammers trying to hijack." It took time and published code to change minds. Today the situation has flipped in an unexpected way. "There is no money in this project for a long time already, so nobody's getting paid," Alex told me, when I asked what would happen if funding dried up. The project continues anyway.
How Mimblewimble Works
Alex's explanation of the protocol was the clearest I have heard on the show. Mimblewimble takes Bitcoin's UTXO model and replaces the script with a Pedersen commitment: the amount multiplied by one elliptic curve point, plus a secret blinding factor multiplied by another. The commitment is "both hiding and binding," so nobody can see the value and the owner cannot change it. Every transaction consists of inputs, outputs and kernels, and because they all look alike, a block "kind of looks like one big transaction with lots of inputs and lots of outputs and kernels."
Two properties follow. First, "there are absolutely no addresses whatsoever." The price is interactivity, since sender and receiver both have to sign. Second, intermediate outputs can be cut through and discarded. A new node needs only the block headers, the kernels and the current UTXO set to verify that nothing was printed out of thin air, which is why every Beam wallet ships with a full node inside.
Later, when a viewer asked whether Bitcoin's client-side pruning was the same thing, Alex pointed back to the opening of the original paper, which says Bitcoin Script has to be given up for this structure to work. He recommended reading the paper itself. "It's genius because it's just four pages of a white paper describing a very simple concept," he said.
The 96% Headline
I asked about the 2019 article by Ivan Bogatyy, "Breaking Mimblewimble's Privacy Model," which ran sniffer nodes on Grin and linked 96% of transactions. Alex admitted the team handled it badly. "We read it obviously, and we said, ah, yeah, whatever," he said, and that underestimation cost them. Many people took "basically the title of the article" and walked away from both projects.
His assessment of the substance was nuanced. The UTXO graph in Mimblewimble is real and visible to anyone running an archive node. An active attacker who sends a target many transactions can, over time, probabilistically link two wallets. "So yes, the problem is real." But amounts stay encrypted and identities are not revealed directly, and he thinks the article "hugely exaggerated" how easy and severe the attack is.
Beam already had defenses that Grin lacked at the time. Both coins use Dandelion, the stem-and-fluff relay that Reuben Yap also described on the show, but Beam merges transactions together during the stem phase so they "cannot be undone because it's just added scalar number." Beam nodes also add zero-value decoy inputs and outputs when traffic is low. Neither fully solved the problem, so Beam went looking for something stronger and found Lelantus.
Lelantus-MW and the Shielded Pool
What Beam runs today is Lelantus-MW, a Mimblewimble adaptation of the Lelantus protocol from Firo. You put a UTXO into a shielded pool, wait for the anonymity set to grow, and take out a new UTXO with no link to the old one, plus a proof that the values match. In Beam's design, Alex said, the pool's anonymity set is capped at a window of about 64,000 outputs, while Zcash in theory hides you among the entire chain.
His comparison of Monero, Zcash and Beam was refreshingly undogmatic. ZK is the strongest "if you take it to the extreme," but all three give solid results in practice, and the weakest link is usually the user. "It's very, very probable that your privacy will be, you know, lessened or breached, not because of the protocol design, but rather because of your behavior." Spending coins right after you receive them shrinks your effective anonymity set, so the Beam wallet tries to schedule spends to avoid that.
That explained a toggle I had found in the wallet's receive screen called maximum anonymity set. When you send into the pool on someone's behalf, you depend on the receiver not withdrawing too quickly. The max privacy mode is a meta-instruction to the receiver's wallet to wait until the target anonymity set is reached or 72 hours pass. The enormous Beam addresses I complained about have a similar explanation: they carry about 20 one-time vouchers so that even the sender cannot see when you spend.
A Private Ethereum With a Built-In Node
The wallet looks nothing like Grin. I found an NFT gallery, a DEX, DAO voting, a name service, bridges, an asset minter and a wrapped bitcoin called BBTC. Alex traced it all back to atomic swaps, the first feature Beam built with Mimblewimble's kernel extensions. Confidential assets came next. "By taking a new generator point," he explained, you can create a new coin "which will be as confidential as Beam itself." There is a confidential stablecoin called Nephrite, though he was honest that no services directly accept it yet.
He insists that Beam has "fully Turing-complete smart contracts" through a hybrid UTXO-to-account design, and that anything built on Ethereum can be built on Beam. The difference is where apps run. They live inside the wallet, distributed through IPFS and an on-chain app store, so no website front end can be censored. "In Beam, you can not only use applications anonymously, you can also distribute applications completely anonymously." As a proof of concept, the team built a decentralized, anonymous Git system called Sourc3. Nobody wanted to fund it, he said, but the code is still on GitHub.
There is also a messenger, which surprised me. The "addresses" in it are not on-chain at all. They belong to SBBS, the off-chain messaging layer Beam built to negotiate interactive transactions, implemented with distributed hash tables and a small proof-of-work against spam. Alex called the messenger itself "very, you know, proof of concept-ish." The comment field on the send screen, he added, is stored only locally.
Why Not Ethereum, Why Not Bitcoin
I asked why technology this capable has not caught on the way Ethereum or Solana has. His answer was half sociology. Bitcoin was marketed as untraceable, then turned out to be "very, very traceable." Crypto then split into gamblers, who just want fast and easy, and enterprises, who went to private ledgers. "Everybody says they want something, but nobody really wants to or like tries to get to it in a way." What is missing, in his view, is a social habit, "just like you lock your door when you go out of the house."
The roadmap for 2025 was Beam Warp, a layer 2 with EVM support and delegated proof of stake for fast finality, connected to the base chain with a native confidential bridge. The base layer would stay proof of work. "Beam itself is going to be forever proof of work," he said. It is mined on GPUs with BeamHash III, and he said some pools kept mining even when it was not the most profitable choice. Unlike Grin, whose emission runs at 60 coins a minute forever, Beam has a capped supply.
To the maximalist question of why Beam does not build on Bitcoin, Alex gave the shortest answer of the night. "Everybody would love to build on Bitcoin, but that's not as simple." He did mention that Beam's weekly Twitter Space had been discussing a bridge between Beam and Monero to put Monero liquidity to work in confidential DeFi.
Marketing, Tickers and Harry Potter
The episode ended on the problems engineers do not like to talk about. Alex admitted Beam's community has been "rightfully angry" for years about the team's marketing. "We really suck at everything related to marketing what we do," he said. It does not help that another, unrelated token took the Beam name and a bigger market cap, and that AI-written news sites mix up the two projects' price charts. If you go looking, the real one has the prism logo, like Pink Floyd's The Dark Side of the Moon.
He also praised David Burkett, who built Litecoin's MWEB: "I love this guy." He said he sees Grin as pioneers rather than rivals, and that he would help anyone in privacy if the field moves forward. We closed with the lore. Mimblewimble is the tongue-tying curse from Harry Potter, Grin is named after Gringotts, and Grin's anonymous founder went by Ignotus Peverell. Earlier in the show, Alex had called it "amazing" that, like Satoshi, the author of the Mimblewimble paper is still unknown today.
Near the end I told Alex that I enjoy covering the small share of projects outside Bitcoin that deserve a closer look, and Beam fits: technically ambitious, unfashionable, largely unpaid and still shipping. Alex did not try to sell me on price. He showed me the wallet, explained the trade-offs, and conceded the weaknesses. For Mimblewimble's other branches, see my conversations with Charlie Lee on MWEB and Marek Narozniak on Grin and quantum computing. Beam's code is on GitHub.
Listen to Alex Romanov on Spotify, Apple Podcasts, YouTube, and More
Time stamps:
- 00:00:24– Introducing Alex Romanov
- 00:00:50– Beam's Launch and MimbleWimble
- 00:03:01– Alex's Journey to Beam
- 00:04:25– Beam vs. Monero vs. Zcash
- 00:07:12– Technical Aspects of Mimblewimble
- 00:09:31– Unique Properties of Beam Transactions
- 00:12:15– Blockchain Analysis and Pruning
- 00:13:12– Misconceptions About Mimblewimble
- 00:14:21– Responding to Criticism
- 00:18:01– The Impact of the Ivan Bogatyy Incident
- 00:20:21– Discussion on UTXO Attacks
- 00:21:28– Dandelion Protocol and Transaction Origin Obfuscation
- 00:22:42– Decoy Inputs in Beam
- 00:23:46– Integration of Lelantus-based Solutions
- 00:24:42– Overview of Beam Wallet Features
- 00:28:20– Introduction to Beam's Smart Contracts
- 00:30:59– Confidential Stablecoin: Nephrite
- 00:33:35– Comparison of Privacy Protocols
- 00:38:23– User Experience and Usability in Privacy Coins
- 00:39:26– DAO Voting System
- 00:40:00– Staking and Layer 2 Development
- 00:40:41– Popularity of Privacy Coins
- 00:43:24– The Evolution of Privacy in Blockchain
- 00:46:20– Beam vs. Ethereum
- 00:48:17– User Need for Privacy
- 00:50:13– Social Shift Towards Privacy
- 00:51:19– Comparison of Beam and Grin
- 00:52:11– Decentralized GitHub on Beam
- 00:55:14– Beam's Smart Contracts vs. Ethereum
- 00:55:46– Beam Wallet Interface
- 00:56:22– Atomic Swaps & Asset Swaps Explained
- 00:57:51– Native Swapping with Bitcoin
- 00:59:01– Decentralization Concerns
- 01:00:50– Messaging Layer in Beam Wallet
- 01:03:53– Beam's Messaging System
- 01:10:47– Maximum Anonymity Set Feature
- 01:13:33– Exchange Withdrawal Addresses
- 01:14:29– Long Addresses in Beam
- 01:16:28– Roadmap Features
- 01:18:33– Confidential DeFi Article
- 01:22:01– Mining Beam with GPUs
- 01:23:01– Community and Mining Pools
- 01:24:10– Proof of Work vs. Proof of Stake
- 01:25:12– Investment Pitch for Beam
- 01:26:11– Funding Challenges in Privacy Projects
- 01:27:20– Collaboration in Privacy Space
- 01:29:30– Confusion Over Beam Tickers
- 01:33:36– Final Thoughts on Beam's Development
- 01:36:44– The Importance of Feedback
- 01:37:08– Beam and Monero Bridge Collaboration
- 01:38:06– Why not Build on Bitcoin
- 01:38:40– Pruning the Blockchain
- 01:39:51– Mimblewimble’s Harry Potter References
- 01:43:20– Marketing Challenges in Crypto
- 01:44:10– Price Action and Exchange Listings
- 01:46:27– Need for Deeper Analysis
- 01:46:37– The Scams Narrative
- 01:50:08– Innovation through Competition
- 01:52:50– Usability Challenges in Crypto
- 01:54:05– Positive Features of Beam Wallet
- 01:54:27– Local First Design in Beam
- 01:55:21– Ethereum Wallets and Features
- 01:55:53– Local Application Architecture
- 01:56:20– Hardware Wallet Integration
- 01:56:56– Decentralization Goals
- 01:57:08– Privacy vs. Usability Trade-off
Verify this episode
This is the SHA-256 fingerprint of the MP3 as published here, timestamped in the Bitcoin blockchain with OpenTimestamps. If one byte of the file changes, the fingerprint changes.
- SHA-256
7367dce8b3675e67a4a0ca1232c6670d17847592ceae7572af96dc69992478de- Proof
- 2025-02-18_s16_e8_alex_romanov_beam_mimblewimble_privacy_-_18.02.2025_01.06.mp3.ots · all episode hashes (proof)
- Status
- Anchored in Bitcoin block 974,312
- Timestamped
- After release. The episode came out on 18 Feb 2025, but this proof was made on 3 Nov 2026 and anchored in block 974,312, so it proves this exact file existed by 3 Nov 2026, not on the release date.
How to check it yourself
- Download the MP3 and the proof into the same folder.
- Run
sha256sum 2025-02-18_s16_e8_alex_romanov_beam_mimblewimble_privacy_-_18.02.2025_01.06.mp3(on a Mac:shasum -a 256 2025-02-18_s16_e8_alex_romanov_beam_mimblewimble_privacy_-_18.02.2025_01.06.mp3). The result must match the SHA-256 above. - Install the OpenTimestamps client (
pip install opentimestamps-client) and runots verify 2025-02-18_s16_e8_alex_romanov_beam_mimblewimble_privacy_-_18.02.2025_01.06.mp3.ots. It hashes the MP3 again and checks the proof against your own Bitcoin node, then prints the block and the date the file existed by. Without a node,ots info 2025-02-18_s16_e8_alex_romanov_beam_mimblewimble_privacy_-_18.02.2025_01.06.mp3.otsshows the block height to look up in any block explorer.
Related
S17 E45: Talking Tari with Naveen Jain, Fox & Marguerite de Courcelle
There are projects in this space that are famous for what they shipped. Tari used to be famous for what it has…
S11 E5: Charlie Lee on Mimble Wimble Extension Blocks (MWEB)
Mimble Wimble and Extension Blocks are two interesting Bitcoin proposals that were heavily discussed by Core developers, but…
S15 E59: David Burkett on MWEB, Litecoin Privacy & Why Drivechains Need a Use Case
David Burkett, the developer who built MWEB for Litecoin, explains MimbleWimble, stealth addresses, peg-out leaks, Grin's decline…
Comments
Comments run on my own server. No trackers, no tracking cookies.