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 · E11 · 1:21:25

Lord Kristaps on JoinMarket, Bitcoin Privacy and Open Source (S12 E11 Full Article)

7 Dec 2022 · by Vlad Costea · 6 min read
Published at block 766,220
Cover art for S12 E11, Lord Kristaps on JoinMarket, Bitcoin Privacy & Open Source Contributions
MP3 (152 MB)

The audio keeps playing while you browse the site.

Read the transcript10,071 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 met Kristaps Kaupe on a privacy panel in Riga, and I wanted each person from that panel on the podcast. Kristaps maintains JoinMarket, contributes to Bitcoin Core, RaspiBolt and SatSale, and goes by Lord Kristaps. Yes, there's a story behind that.

He's a practical builder. Most of his work started with fixing something that annoyed him. That's a good lesson for anyone who wants to contribute to Bitcoin. The original show notes have the short version.

A Never Ending Fight

I asked whether there's a limit to how private Bitcoin can get. "I don't see limits. We all the time figure out new ways how to use, I think, Bitcoin more private way. The same time other guys are figuring out how to limit our privacy." He called it a "never ending fight."

Why JoinMarket

"JoinMarket is the first thing that I think is important, it's the most decentralized one. Like you don't have some for-profit company behind it." That cuts both ways. "It's bad because developers don't get paid for working on it."

What first pulled him in was the incentives. He ran a yield generator bot. "You just put bitcoins in some wallet, and then there is some bot running and you get some passive income. You earn some satoshis without giving up your private keys." His verdict: "That is kind of like free markets."

Makers and Takers

JoinMarket has no central coordinator. "There is market makers who provide liquidity for CoinJoins, who runs that yield generator bot. And then there is market takers who just want to have CoinJoins right now." The taker coordinates and "pays for the market makers who provide liquidity some fee."

The result is flexible. "They can have CoinJoin with any amount." There's no round system with fixed denominations, so "every payment can be CoinJoin." At a web shop checkout, "you can do that transaction as a CoinJoin at that moment."

Privacy-wise, "only party that can see which bitcoins go where is the taker side," and it's "not in their interest to give this information away, because they pay for CoinJoins."

Don't expect to get rich being a maker. "You will not get very rich currently by running that JoinMarket yield generator." He runs his own at almost zero fees.

The Catch: Full Nodes and Command Line

"First it requires you to run full node." Projects like "RaspiBolt and RaspiBlitz and Umbrel" are making full nodes popular again, and "that's one of the reasons why JoinMarket has become more popular again." But "for most of the functionality, you need to know command line." The Qt app only does taker mode, and a newer web interface called Jam had just appeared.

His idea for the future is integration. JoinMarket is "not only the wallet software you can use, it's also just protocol how you coordinate CoinJoins," so "one way forward would be to integrate JoinMarket in other wallet software."

He also had a healthy view on the privacy wars. JoinMarket isn't a company, so its developers "don't have so much motivation to try to attack other people."

Fake CoinJoins and Bitcoin Core

His first Bitcoin Core contribution came from a side project. "The idea of fake CoinJoins is that you create transactions that look on blockchain like CoinJoin transactions." The twist: "all the inputs and all the outputs are yours. You're mixing with yourself." The goal: "you can never be sure that CoinJoin is actual CoinJoin." Or, as he put it, "you bring some more chaos to the blockchain."

His script kept paying fees below the relay fee, and Bitcoin Core's error didn't show the numbers. "So to debug my script, I modified Bitcoin Core. Then I of course found a problem in my script. But that was my first contribution." Most of his work since has been in the RPC layer, "where other software talks to Bitcoin Core." He laughed that with non-technical people, "you can say, 'I'm a Bitcoin Core developer.'"

SatSale and Weak Hands Mode

SatSale is "some lightweight alternative to BTCPay Server." Why work on payments? "We need more that circular economy, like more paying for goods and services in Bitcoin. So in that way there is less KYC."

Small businesses he talked to often need fiat soon after a sale. So SatSale has "a cool feature called weak hands mode," where an incoming Lightning payment "immediately swaps for USDT on Liquid Network." His own donation page? "It hasn't weak hands mode enabled, of course. I just keep bitcoins." His belief: "we need alternative softwares for everything."

The Lord Title

"I'm English Lord, not Lord of Bitcoin." It's one of those novelty plots where "you buy one square feet of land somewhere in England." A good friend bought it for his birthday, so "I have documents that I am Lord and stuff."

RaspiBolt, Odroid and Cats

He likes RaspiBolt because "it's a guide, it's not some installer," which "allows you to understand better how everything works." He found things to improve, and "at one moment you are already maintainer."

He moved off the Raspberry Pi to an Odroid HC4. "Raspberry Pi is too slow for me." The real reason was mirroring: "It has two SATA slots." With Lightning, "it's possible that in the middle of the transaction your hard drive crashes." He learned this from his cats, who "somehow smashed it down to the ground." He didn't lose funds, but "I needed to resync all the blockchain and it was pain."

He also warned about SD cards: "they have limited number of erase cycles. And at one moment, the SD card will die."

As a teenager he even built his own operating system. "It had Tetris. I ported Tetris to it." It taught him a lot, because "you need to write like driver for keyboard, driver for screen, like everything." He's still a fan of real-time systems, which optimize for the worst case. "As a desktop user, I just hate when my computer freezes." These days, "I think it's more important to work on Bitcoin than to try to build your own operating system."

What Lightning Hides

"There aren't like silver bullets there." But Lightning has a real advantage: "there is no permanent public ledger like blockchain." With the blockchain, "I can analyze it after 20 years. With Lightning, I definitely cannot do that." Still, "Lightning is kind of more private for sender than receiver," and channels can be probed by sending test payments until one succeeds.

For most people, though, he still sees Lightning as the more private option. His example was two friends using the same custodial mobile wallet. On Lightning, "BlueWallet knows everything about our transaction. They don't know who we are." Do the same thing on-chain in the simple way, and "potentially not only BlueWallet, but most of the world knows about the transaction." So "I personally prefer to pay with Lightning Network whenever possible."

Routing nodes have their own problem. "Your channels are public," and if you run on clearnet, "your UTXOs are tied to your, for example, home IP address." On-chain privacy still matters. Taproot's anonymity set was small at the time, "but that will change definitely at some point."

Somebody Needs to Build Practical Stuff

When he started, he thought privacy was for "smart guys in universities writing scientific papers." Then "I understood, yeah, but somebody needs to do actually practical, practical some stuff." Projects like RaspiBolt and BTCPay Server aren't breakthroughs, "but that's giving something practical."

What Makes This Episode Worth Listening To

I love guests who prove you don't need a PhD to contribute. Kristaps fixed his own problems, shared the fixes and ended up maintaining serious privacy software. If you care about CoinJoins or running a solid node, give this one a listen.

You can read the full transcript, the original show notes, or visit Lord Kristaps' guest page.

Listen to Kristaps Kaupe on Spotify, Apple Podcasts, and More

Time stamps:

  1. 00:02:02– A never ending fight
  2. 00:03:07– Why JoinMarket
  3. 00:03:47– Yield generator bots
  4. 00:05:21– Makers and takers
  5. 00:06:05– The taker coordinates
  6. 00:07:08– Full nodes required
  7. 00:07:53– Command line, Qt and Jam
  8. 00:10:24– Every payment can be a CoinJoin
  9. 00:14:11– Only the taker knows
  10. 00:17:58– No reason to attack others
  11. 00:20:28– Integrating JoinMarket
  12. 00:25:06– SatSale
  13. 00:26:47– Weak hands mode
  14. 00:27:13– Alternative software for everything
  15. 00:30:36– The Lord title
  16. 00:32:53– Fake CoinJoins
  17. 00:34:12– First Bitcoin Core contribution
  18. 00:42:10– RaspiBolt and the Odroid
  19. 00:43:01– From contributor to maintainer
  20. 00:44:48– His own operating system
  21. 00:47:17– Real-time systems
  22. 00:53:12– Mirrored drives
  23. 00:53:56– The cats
  24. 00:56:51– SD cards wear out
  25. 01:02:25– Lightning privacy
  26. 01:03:28– Sender vs receiver
  27. 01:06:48– The BlueWallet example
  28. 01:10:06– Routing nodes and IP addresses
  29. 01:13:11– Practical builders

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