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
S8 · E9 · 2:23:27

Ben Arc on the Bowser Wallet, LNbits and Open Source (S8 E9 Full Article)

21 May 2021 · by Vlad Costea · 7 min read
Published at block 684,414
Cover art for S8 E9, Ben Arc on Bowser Wallet, LNBits & Open Source
MP3 (197 MB)

The audio keeps playing while you browse the site.

Read the transcript25,354 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

I invited Ben Arc on during the hardware wallet season because he had just done something unusual. "Yesterday I took Bowser out of beta," he told me. Bowser is a hardware wallet you build yourself from cheap parts, and it hides behind a game of Tetris. Ben calls himself a hobbyist, but he's behind LNbits and a long list of open source projects people actually use.

We covered the Bowser, LNbits, point of sale devices for cafes, credit in open source, and why he thinks Lightning will change video games. The original show notes have the short version.

A Hack Table at Bitcoin 2019

The story starts at a conference. "I went to the Bitcoin 2019 conference and there wasn't a hack space. So I put a couple of tables together, I just made a little hack space," Ben said. He had point of sale kits built around "a little ESP32 microcontroller, which are about three dollars," with an e-paper screen and a cheap keypad.

He handed out about 100 of them. Then Stepan Snigirev came over, "into little microcontrollers and trying to get these microcontrollers to interact with Bitcoin." After the conference, Stepan "put together uBitcoin, which is an Arduino library you can use for these microcontrollers," and later "added the ability to sign a partially signed Bitcoin transaction."

That library is the base the Bowser stands on. Ben was very open about it. "Stepan's uBitcoin library is, you know, the Bitcoin Core libraries, made by Pieter Wuille and whoever else, slimmed down for what we needed to do in an Arduino." His point: "We're all building on top of each other's work. And that's why, ultimately, free and open source always wins."

Why a DIY Hardware Wallet

Ben is a fan of hardware wallets. "A hardware wallet is, I think, the best way to store your Bitcoin," he said. His problem is the price and the trust. People are "put off by that, you know, $80 price tag," and "supply chain attacks kind of scared me."

His ideal setup mixes both worlds: a traditional hardware wallet like a Trezor in a multisig next to something you built yourself. Building it also teaches you what's inside. "People taking control of their own hardware and learning to use their own hardware is important."

He was just as clear about the limits of the M5Stack, which other projects use too. "It's an off-the-shelf microcontroller. It's got no secure element in it. You can make it pretty secure, but it's not secure like a hardware wallet." It's "secure in different ways," like the disguise below.

He also asked people to stick to the tested versions: "as long as you use the versions of the libraries which I specify in the repo, and the version of Electrum which I used as well," it works.

Tetris, Morse Code and Plausible Deniability

The fun part is the disguise. "If I was to get my things searched, all my electronics searched, it looks like a Bitcoin hardware wallet," Ben said of a normal device. "Whereas this little M5Stack thing, you know, I feel comfortable carrying that in my pocket and getting on a plane with it and sitting there playing Tetris."

The PIN is entered in Morse code. "I like Morse code, so I want a PIN where I can put Morse code in. There's a gazillion different ways you could put the PIN in." Someone on Twitter pointed out that a listener could decode the button presses. Ben's answer was that DIY means you can change anything. Fork it and enter the PIN from the SD card, or with a D-pad combo.

I suggested borrowing the way the BitBox takes a PIN, and he liked it. "I'm very much going to look into your idea, Vlad," he said, and promised to give Stadicus props for it.

Transactions move as PSBTs on an SD card. He thinks "PSBTs is the way forward" for DIY devices, but "the size of that blob of data" makes QR codes hard on tiny screens. Setup is quick, though. The base M5Stack is about $40 and the Arduino IDE is free. "Flash it, boom, half an hour, you've got a hardware wallet. And you can verify the code, it's all there."

The Trezor Test

Ben has a simple benchmark for usability: his parents. "What I really like about the Trezor is, you know, my dad can use it. My 88-year-old dad can see the PIN on the Trezor and then he can input it into his computer." He admitted the Bowser isn't for them, and it isn't meant to be. It's for hobbyists and people who want covert storage.

From a Bar's Tax Problem to LNbits

Ben used to be a teacher, and his coding skills were "very limited" at the start. The Lightning hack days changed that. "They were so supporting and nurturing and encouraging, and there wasn't any of that 'Oh, you shouldn't be doing this because you don't know what you're doing' type attitude." His point of sale ended up in use at Room 77, the Berlin bar run by Jörg.

LNbits came out of that bar. Jörg was taking lots of Lightning payments for beer, and "he couldn't identify on his node which transactions were for beer." So LNbits gave each use its own wallet. Ben's comparison: "they just needed to be like a WordPress type thing for Lightning wallets." You start with a simple wallet and add extensions.

His advice to developers who don't know what to build: go outside. "It all starts from real world problems." Feedback from people "in real brick and mortar" is what makes a project better.

Onboarding the Local Cafe

Ben's favorite use case is "the bar owner or the cafe owner who wants to accept Bitcoin." Give them a cheap point of sale and a cheap hardware wallet. Lightning payments pile up, and when they hit a set amount, they get looped out on-chain. "The risk is $300," he'd tell the cashier, and after that it goes "to this hardware wallet, and then the Bitcoin's yours."

The bigger goal is self-sovereignty that pays. "You can incentivize the autonomy and the self-sovereignty and them running their own nodes in a way which is good business." Run the setup for a small fee, then show them how to run it themselves.

Give Credit Where It's Due

Ben cares a lot about recognition in open source. He likes the DBAD license: "you can use this, you can use this hardware, you can use the software, whatever." If people like your fork, "give me some props."

He compared it to science. "Scientists will often, if they write a paper, then they have to credit people." In his view, many builders "don't give enough props and recognition to the shoulders of the people they're standing on."

He also explained why he won't sell devices himself. "If I start pursuing commercial ventures, then it will take time away from the free and open source and the educational stuff, which I'm kind of more passionate about." He'd like someone else to "buy a bunch of these devices and then pre-flash them."

For beginners, he said Bitcoin is a good place to learn. "Bitcoin is full of very enthusiastic people who will totally help you." He remembered Stepan being "incredibly patient with me as I'm asking stupid questions."

He also shared how he sees open source in wider terms. "These are free and open source pieces of software, and we're decentralizing the way in which we produce them." That's a debate for another day.

Lightning and Video Games

We ended on games. Ben likes the projects that don't try to make new games. "They're just taking popular computer games and then putting Bitcoin in them, you know, your CS:GO and your Minecraft." He thinks Lightning "will have a huge impact on computer games," as long as it doesn't go "all shitcoiny."

What Makes This Episode Worth Listening To

You hear how a hack table, a cheap microcontroller and a bar's bookkeeping problem turned into tools many Bitcoiners still use. Ben is honest about what DIY hardware can and can't do. If you've ever wanted to build something but didn't know where to start, he makes it sound doable.

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

Listen to Ben Arc on Spotify, Apple Podcasts, and More

Time stamps:

  1. 00:02:41– Why he doesn't sell devices
  2. 00:04:42– Bowser out of beta
  3. 00:06:39– A hack table at Bitcoin 2019
  4. 00:08:42– uBitcoin
  5. 00:11:01– Why hardware wallets matter
  6. 00:12:44– Supply chain attacks and multisig
  7. 00:15:44– Owning your hardware
  8. 00:17:18– Morse code PINs
  9. 00:20:55– Tetris and plausible deniability
  10. 00:23:54– Why open source wins
  11. 00:26:54– The cafe owner use case
  12. 00:28:18– Real-world feedback
  13. 00:30:06– No secure element
  14. 00:36:49– PSBTs and QR codes
  15. 00:47:02– From teacher to developer
  16. 00:49:27– Room 77 and the birth of LNbits
  17. 00:51:53– WordPress for Lightning wallets
  18. 00:53:58– Ideas come from real problems
  19. 00:57:00– Looping out to a hardware wallet
  20. 01:01:38– Self-sovereignty as good business
  21. 01:10:00– The Trezor test
  22. 01:17:20– The DBAD license
  23. 01:18:03– Credit like in science
  24. 01:51:55– Fork it and improve it
  25. 01:54:12– Half an hour to a hardware wallet
  26. 01:58:34– Ask questions
  27. 02:01:47– Decentralizing production
  28. 02:19:06– Lightning in video games

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
855a6d7302f337ad20aa15037433aa0b8db9b6816890a9bf51856d850347c0aa
Proof
2021-05-14_s8_e9_ben_arc_on_bowser_wallet__lnbits__open_source.mp3.ots · all episode hashes (proof)
Status
Anchored in Bitcoin block 974,312
Timestamped
After release. The episode came out on 14 May 2021, 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 2021-05-14_s8_e9_ben_arc_on_bowser_wallet__lnbits__open_source.mp3 (on a Mac: shasum -a 256 2021-05-14_s8_e9_ben_arc_on_bowser_wallet__lnbits__open_source.mp3). The result must match the SHA-256 above.
  3. Install the OpenTimestamps client (pip install opentimestamps-client) and run ots verify 2021-05-14_s8_e9_ben_arc_on_bowser_wallet__lnbits__open_source.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 2021-05-14_s8_e9_ben_arc_on_bowser_wallet__lnbits__open_source.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