Research
Timechain
Search Donate
Sponsors
Cake Wallet, private Bitcoin and Monero walletSideShift.ai, no-signup crypto exchangeOrangeRock, non-custodial bitcoin spot and perps tradingBraiins Hashpower, buy and sell Bitcoin hashrateLayer Two Labs, drivechains for Bitcoin
S12 · E1 · 56:51

Thomas Voegtlin on Electrum and Lightning Trampoline Nodes (S12 E1 Full Article)

1 Oct 2022 · by Vlad Costea · 7 min read
Published at block 756,539
Cover art for S12 E1, Thomas Voegtlin on Electrum Wallet & Lightning Trampoline Nodes
MP3 (78 MB)

The audio keeps playing while you browse the site.

Read the transcript7,757 words, every line links to the minute it was said

Ask this episode

Embed this episode

Paste this on your site or blog. It is a small player that streams from here: no trackers, no cookies, no ads.

Preview the player

Electrum is one of my favorite Bitcoin wallets, and I got to sit down with the person who made it. I met Thomas Voegtlin at Mallorca Blockchain Days in July 2022, the day after his presentation. OGs still use Electrum every day, but I had a feeling the class of 2020 didn't know how much it does. So this episode was my way of fixing that.

We talked about how Electrum started, Electrum servers and privacy, multisig before PSBT, Lightning without being online all the time, trampoline routing, a few unpopular opinions and what's next. The original show notes have the short version.

Born After a Wallet Website Stole Coins

"Electrum was created in 2011 by me," Thomas said. "I was just toying with Bitcoin in order to learn how it works." He'd heard about Bitcoin in 2010 on Slashdot, from "an article mentioning that the market cap of Bitcoin had reached $1 million."

What pushed him to build a wallet was a disaster. mybitcoin.com "was a wallet website that stole bitcoins of their users." Bitcoin was small then, so it isn't remembered like Mt. Gox, "but at the time, compared to the size of the Bitcoin economy, it was something big."

Long before Bitcoin, he had wondered about digital money. Around 2000, on a peer-to-peer mailing list, he "raised the question: can we create a currency" on top of a distributed hash table. "Of course, I had no idea how to solve the double spend problem."

The name has two meanings. Electrum is a gold and silver alloy, and it hints at electronic money. The old logo also showed "a smaller Bitcoin orbiting around the larger one, as the client orbiting around the server."

What an Electrum Server Actually Is

People often confuse an Electrum server with a full node. Thomas cleared it up. "An Electrum server is a full Bitcoin node with some extra indexing capabilities. So it's able to answer to requests about the history of a Bitcoin address."

By default, the wallet connects to a random server, "because we don't want users who have no idea about which server they want to use to be bothered." You can pin your own, and you can route through Tor.

He doesn't write the server code anymore. ElectrumX replaced his version, and "I'm very happy that I don't have to develop this myself anymore." He likes the variety: "I think diversity is good."

On privacy, his answer was simple. "If you want privacy, nothing beats a full node, and Electrum can be used in the context of a full node." Electrum is also for beginners who don't want to wait, because "it's also an important aspect of money that you don't need to wait to download the full blockchain."

Multisig Before PSBT Existed

Newer users reach for other wallets for multisig, but Electrum did it first. "Before PSBT was officially a spec, we had our own PSBT, our own format, and we developed that format in order to be able to be the first to propose multisig."

Once PSBT became the standard, they dropped their format, "because we don't want the code to become too complex." The early start is why Electrum became the default for multisig. "Before PSBT there was no way to do multisig using different wallets, because they had no way to communicate, except if you used Electrum."

He also admitted they don't market much. "In the recent years, we mostly focus on Lightning, so... and we don't take much time to advertise what we do."

Lightning for a Wallet, Not a Node

Thomas drew a clear line between a routing node and a wallet. LND "is designed to be a public node." A wallet "is online only for a very short time. I mean, people open their wallet, they do a payment, they expect the payment to work instantly and they close the application."

That creates problems. You need someone to watch your channels, "so this is the role of a watchtower." And you need to find routes without downloading a graph that keeps changing.

That's where trampoline comes in. "It has been invented by the developers of Eclair, so the ACINQ company." With it, you "delegate the route finding to a trampoline node." Electrum went further than Phoenix: "the route can have multiple trampolines for privacy." With only one, "the trampoline knows about both the sender and the recipient, so it gives them too much information."

He sees it as the same story as SPV. Both "are technologies that are designed to reduce the amount of data that you have to download and that make it possible to pay instantly when you turn on your device."

SPV, Bloom Filters and Neutrino

I asked whether Electrum's SPV matches the white paper. He explained that some claimed SPV meant Bloom filters, which he rejected. "The white paper from Satoshi does not say anything about how you should receive the Merkle proof."

Neutrino, BIP 157 and 158, is different. "It's much better than the Bloom filter." It's "more private, more efficient," and if it had existed back then, "it would have changed my mind." Electrum doesn't use it, though.

A Simpler Electrum

I said Electrum keeps adding features without changing its interface. "Well, that's not true," he said. The next version would have "a single button that will create invoices both for on-chain and Lightning."

His goal is "to abstract the payment from the payment layer. So users should not have to know whether they use on-chain or Lightning." If you need to rebalance, open a channel or do a submarine swap, Electrum "will suggest it and automatically select the relevant channels and the amount." The only things users see are delays and fees.

The Android app was being rebuilt too. The old one, based on Kivy, was "not responsive. It's slow." A new developer was "rewriting it from scratch using Qt."

Some Unpopular Opinions

I asked for an unpopular opinion, and he warned me it might hurt. "I'm not sure if the block reward going to zero is a good thing." He'd "feel more comfortable if the miners had a constant block reward at some point," but that's a hard fork, and "we don't know how the game theory of mining and rewards is going to work."

On proof of stake, he'd oppose a switch "just because it's untested." On DeFi, his point was cultural. Smart contract builders "have no inhibition towards complexity," and "the surprise comes later."

On hard forks: "If we have to hard fork over a pressing issue, the hard fork should only fix that issue." And on big blocks, his objection was the context. He wasn't "against larger blocks, absolutely," but the Bitcoin Cash push came with "division in the community," and "there was a smarter way to go about that, and that's Lightning."

What Excites Him and Who He Recommends

"I think still Lightning." He mentioned Taro (later renamed Taproot Assets), other assets and discreet log contracts as things worth watching.

For another Lightning wallet, he named Phoenix. "I think the best Lightning wallet in terms of user experience is Phoenix." Electrum borrows from it, but won't depend on one node. "Our philosophy is no single point of failure, no trust, or as little trust as possible."

He isn't on Twitter personally. "If I started to post personal opinions on a personal account, I would waste a lot of time." Announcements go on the Electrum account, and bugs go on GitHub. "GitHub is not a free teaching course, right? It's again a question of how we spend our time."

What Makes This Episode Worth Listening To

You get the history of one of Bitcoin's oldest wallets from the person who built it, and a clear explanation of why a wallet's needs differ from a node's. Thomas is precise, modest and honest about what he doesn't follow. If you've never tried Electrum, this is a good reason to.

You can read the full transcript, the original show notes, or visit Thomas Voegtlin's guest page.

Listen to Thomas Voegtlin on Spotify, Apple Podcasts, and More

Time stamps:

  1. 00:01:47– Creating Electrum in 2011
  2. 00:02:39– The mybitcoin.com theft
  3. 00:03:12– Hearing about Bitcoin on Slashdot
  4. 00:03:44– What the name means
  5. 00:04:32– Electrum server vs full node
  6. 00:05:09– Random servers by default
  7. 00:05:54– ElectrumX and diversity
  8. 00:07:38– Nothing beats a full node
  9. 00:09:35– Beginners and privacy
  10. 00:10:53– Not much advertising
  11. 00:11:44– Multisig before PSBT
  12. 00:17:33– A wallet is not a node
  13. 00:18:16– Watchtowers and route finding
  14. 00:19:57– Multiple trampolines for privacy
  15. 00:21:23– Same story as SPV
  16. 00:22:42– SPV and the white paper
  17. 00:24:02– Neutrino
  18. 00:25:22– One button for on-chain and Lightning
  19. 00:27:08– A currency idea around 2000
  20. 00:29:11– A zero block subsidy
  21. 00:30:18– Proof of stake
  22. 00:32:34– DeFi and complexity
  23. 00:35:05– Hard forks should fix one thing
  24. 00:35:49– Big blocks
  25. 00:38:36– Still Lightning
  26. 00:43:40– Abstracting Lightning
  27. 00:45:33– Rebuilding the Android app
  28. 00:46:18– Phoenix
  29. 00:50:05– Not on Twitter
  30. 00:51:52– GitHub is not a free course

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
68da889054b80db4a73a00d688923bace34f37e06e2a4fecb877b57d08cc2780
Proof
2022-09-24_s12_e1_thomas_voegtlin_on_electrum_wallet__lightning_tr_oline_nodes.mp3.ots · all episode hashes (proof)
Status
Anchored in Bitcoin block 974,312
Timestamped
After release. The episode came out on 24 Sept 2022, 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
  1. Download the MP3 and the proof into the same folder.
  2. Run sha256sum 2022-09-24_s12_e1_thomas_voegtlin_on_electrum_wallet__lightning_tr_oline_nodes.mp3 (on a Mac: shasum -a 256 2022-09-24_s12_e1_thomas_voegtlin_on_electrum_wallet__lightning_tr_oline_nodes.mp3). The result must match the SHA-256 above.
  3. Install the OpenTimestamps client (pip install opentimestamps-client) and run ots verify 2022-09-24_s12_e1_thomas_voegtlin_on_electrum_wallet__lightning_tr_oline_nodes.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 2022-09-24_s12_e1_thomas_voegtlin_on_electrum_wallet__lightning_tr_oline_nodes.mp3.ots shows the block height to look up in any block explorer.

Share: X · Email · Link

Related

Comments

Comments run on my own server. No trackers, no tracking cookies.

0:000:00