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
S16 · E42 · 2:36:50

S16 E42: Michael Tidwell on Bitcoin Drama & TABConf

7 Sept 2025 · by Vlad Costea · 11 min read
Published at block 913,601
Cover art for S16 E42, Michael Tidwell on Bitcoin Drama & TABConf
MP3 (215 MB)

The audio keeps playing while you browse the site.

Read the transcript23,220 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

The wheel came up with a name and an egg came up with a solution, and for two and a half hours Michael Tidwell and I let that machinery decide who was to blame for Bitcoin's troubles. I opened the show with the line that set the rules: "I ask you, who is to blame? And you ask me, who is the solution?" Michael organizes TABConf and co-hosts the Blocktime podcast, he had joined for the livestream, and he was about to be asked to answer for a lot of things he had nothing to do with.

The format was something I cooked up for this episode. We spin a wheel loaded with the usual suspects of Bitcoin drama, whoever lands is the culprit, and then Michael cracks a randomly chosen egg containing the remedy. There are eight eggs. We started the game at 00:03:47, and three seconds into the setup his child walked into the room and he had to step away, which is as good a reminder as any that this was a livestream and nobody was in a studio. I had already called him a spook in the first few minutes, for no reason I can reconstruct, so the tone was set.

Plebs Are Birds

Early on we got into why the conference is called what it is. Michael said that a certain commentator "thought it was very funny that I called the conference TABConf without knowing this backstory ahead of time." That commentator, in Michael's description, "has to be like over the top to even get people to start talking about important stuff." I had been trying to get an answer on whether the guy is a genius or a clown, and Michael's view was blunt: "That guy is either a genius or batshit crazy. I love that guy."

From there we drifted to the word "plebs," which I use constantly and which Michael thinks is empty. "I don't even think plebs are real. I think they're like birds." His argument is that it is a marketing term, something a brand reaches for, and not a demographic anyone can point to. I had my own claim ready, that I am "the king of plebs," and he did not accept the title.

We also compared notes on reading. Michael confessed he does not read at all: "I don't read books. I listen to audiobooks." We came back to this at the very end of the night, when books got their own ten minutes, and there is a twist waiting there.

A running gag in the chat was my shirt. A commenter called CoinJoin Chris asked at 00:54:45 whether I was a "Persian club promoter." I have no defense. I wore it, I own it, and I do not have a better theory of what the shirt communicates.

Knots, Core and a Divergence Nobody Expected

The first serious beat was Core versus Knots. Michael gave a number I had not heard framed this way: "there's more lines of code that are different between Knots and Core than there were total lines in the original implementation of Bitcoin." That is a lot of divergence, and his reading of the dispute is not generous to either camp. "this no longer seems like a Bitcoin discussion," he said of how it has played out, and of the people who keep escalating he said, "They just want to get their way."

He had a picture for it, too: "It's like, well, if I'm not going to get my way, I'm, you know, I'm going to scream in the middle of Walmart and cry until I get my toy". On the risk side, he does not like the direction of travel, and said "when you have more than one implementation, it's dangerous."

I pushed on the part that interests me most, which is whether this ends in a hard fork. My prediction on the show was that one comes within a year, and I said "I've seen this movie before." Michael was unconvinced: "I'm not convinced there's going to be a hard fork yet." We left it there, because neither of us had anything to settle it with, and because the wheel was waiting. I had just made a prediction on a livestream with a guest who disagreed, and that is as much of a record as I wanted.

The last piece of that exchange was a bit I had planted earlier. I told Michael, about a particular piece of software, "it's already on your node," a claim I used to needle him about what was running in his basement. He took it in stride and moved on, which was the right call.

Drivechains, Miners and the Case for Testing

Once the wheel landed on Paul Sztorc, Michael went further than I expected. I have interviewed Paul many times, from BIP 300 at Baltic Honeybadger to activating drivechains via CUSF, and I know the arguments cold. Michael's version of the defense was about how to settle it. "I think drivechains gets too much criticism from too many people I respect," he said, and then the line that I think captures his whole approach: "Let miners steal, like prove that it's bad." He wants it tested in the market, with money on the line, and not argued to death in theory.

When Paul came up in the context of opposition, Michael's reaction was "Oh, Paul is up against the spooks." I said I would take his side of that on any day of the week.

I told Michael about a thing I believe happened at the debate at TABConf between Paul and Peter Todd: that Paul had taken body-language coaching beforehand and then froze on stage. I raised it at 01:10:43 and I am passing along what I said, not claiming it as established. Michael's own memory of the event is different and more critical of the other side. "Peter Todd, I think came, like he wasn't prepared. He, he sort of like, you know, winged it, more or less in my opinion." I later recorded the TABConf 8 livestream, Part 1, where Michael was a guest alongside Paul and others.

On the other side of the ledger, I asked about MEV. Michael is building a game in which bytes of the block hash determine the terrain, and he calls this "some weird, esoteric type of MEV on Bitcoin." It is a toy, but a toy that exercises exactly the kind of block-level extraction people argue about, and I liked that he described it by what it does and did not oversell it.

Citrea, Liquid and Whether Anyone Wants a Killer App

I put Citrea and Liquid in front of him and asked whether trust-minimized bridges matter. His answer was that the trust model might be the wrong thing to fixate on. "did Bitcoiners care about Liquid is a question as well," he said, meaning the question might be whether there was ever a killer application to pull people in, regardless of how the peg works.

I was not generous. "I seriously don't care about stablecoins," I said, which got a raised eyebrow, because half the money flowing through these systems is exactly that.

Lightning was the other place we split. Michael said "Lightning didn't live up to expectations," and then immediately qualified it: "Just to be clear, I am a fan of Lightning." I had been running a routing node and I told him how it went: "I lost more money than I actually made." We stayed on that for a while, and I came away with the impression that the fan and the sufferer are talking about different layers of the same thing. At one point I gave a plug, "Listen to the Bitcoin Takeover Podcast," and he told me that the host of a podcast does not get to plug his own show in the middle of someone else's argument.

Why TABConf Is Free of Whales

Michael organizes TABConf, and the philosophy behind it is stricter than most conferences. There are no whale passes. Everyone who speaks goes through the same public GitHub submission process, and "You can't buy your way on stage." The ticket cost came up at 01:16:40, when I teased him about his handle, miketwentyone, and the price: "$121 worth of Bitcoin, or fiat USD, and/or whatever." The conference loses money on every ticket: "Essentially we lose money on every ticket we sell." He joked about moving the price to a 256-themed number: "We might go to SHA-256, you know, 256 price point in the future. I don't know, like, it's up in the air. We'll see."

What happens in the rooms is hands-on, which is why I keep coming back. Meshtastic and Warnet are recurring projects. Michael described the mesh work this way: "you don't need the internet to broadcast a Bitcoin transaction or a secret message." On the attack side, "last year we attacked Bitcoin Core, a bunch of Bitcoin Core versions." The point of all of it, as he put it, is conviction through action: "You get convicted through actual doing, actual building."

I could not resist a little history. I mentioned that Chris DeRose stripped on stage at TABConf 2019. This was at 01:08:10 in the stream, and Michael's response to the event was that there was no agreement on its merits: "There was no consensus on whether or not that was a good event or not."

He also has a standing instruction for newcomers, which doubles as the conference thesis: "you should always assume Bitcoin was a terrible idea and you should prove yourself otherwise by coming to TABConf."

Eight Eggs and the Twenty Minutes After

The eggs were the engine of the night. When the wheel landed on Satoshi, at 01:29:18, the egg solution was "just HODL," on account of OCEAN, which Michael was happy to take as a joke about miner decentralization. I took the Satoshi landing as a chance to talk about the man I find least convincing as a messiah, and said so: "Like, he was just a guy." That is the line I borrowed from Martti Malmi, who looked at the creator of Bitcoin once and thought exactly that.

Nearly every egg had a joke inside it. The eighth and last was opened at 02:16:45, and it read: "Sell all your Bitcoin." We had a laugh at what that meant for a show that had just spent two hours dealing out remedies.

Then the show kept going for another twenty minutes. Mental health, how resilient Bitcoin actually is, and books. That stretch was my favourite part of the night. On resilience, Michael was calm: "Bitcoin would still survive very easily," and "if this were to kill Bitcoin, then Bitcoin was doomed already." On how he got to that calm, he said it was "from a place that was maybe a little bit more based in my head."

There was an aside about diets in there too. Michael said he has gone keto several times and "I've never been constipated, so I don't know why that's a trope. But keto, a ketogenic diet, is amazing." I will let that stand without comment.

The books I promised you came last. Earlier he had told me he does not read. The book he named was Aaron van Wirdum's The Genesis Book: "That is my favorite book, hands down." I had Aaron on the show to talk about it.

Craig Wright, Clubhouse and What Counts as Bitcoin

One story I kept coming back to was Michael on Clubhouse, arguing with BSV supporters about Craig Wright. He described the confrontation at 02:20:32 and the arguments he made on the room's stage. I got something wrong while we talked about it, and he corrected me: the checksum on pay-to-public-key-hash addresses is not a consensus rule. I had treated it as one. He was right, I was wrong, and I took the correction.

The question I saved for the end was the one that decides a lot of fights. What would make Bitcoin Cash into Bitcoin? Michael's answer: "we would be calling Bitcoin Cash Bitcoin, and I would be okay with that." The condition was sustained dominance, in price and in hash rate. His reasoning leaned on how names work. "If everyone calls a shoe, like a guitar, then even though it makes absolutely no sense, that's how language is changing. That's how culture is changing."

That is a more relaxed position than most of the people who show up at his conference would take. It follows from everything else he said on the show, and from the format of the show itself: eight eggs, no authority, nobody certain. I was on camera in a shirt that a commenter called Persian club wear, the host of a podcast that Michael would not let me plug, and I had stopped caring about the wheel somewhere around the third egg.

When the stream ended, the first thing I did was look for the last egg. It had said to sell everything.

Listen to Michael Tidwell on Spotify, Apple Podcasts, YouTube, and More

Time stamps:

  1. 00:01:09– Welcome and episode gimmick intro
  2. 00:01:30– Sponsors shoutout
  3. 00:01:36– Bitcoin drama discussion starts
  4. 00:03:38– Bitcoin Core vs Knots debate
  5. 00:04:28– Wheel spin: Blame the plebs
  6. 00:06:52– Egg pick: Solution is "use tabs"
  7. 00:07:56– Adam Back's "use tabs" context from 2017
  8. 00:09:09– Paul Sztorc's role and personality
  9. 00:10:52– Defining "pleb" in Bitcoin culture
  10. 00:13:42– Hodlonaut story and Lightning Torch
  11. 00:16:32– Roger Ver interview drama
  12. 00:18:43– Hijacking Bitcoin book discussion
  13. 00:22:58– Layer 2 Labs sponsor plug and drivechains
  14. 00:25:14– Citrea ZK rollup explanation
  15. 00:27:48– Liquid federation vs true sidechains
  16. 00:32:39– Core vs Knots diffs and risks
  17. 00:33:52– Peter Todd's OP_RETURN proposal
  18. 00:34:56– CSAM fears and cultural debates
  19. 00:38:05– Illicit content already on chain
  20. 00:40:54– Multiple Bitcoin implementations history
  21. 00:44:03– Libbitcoin rewrite and optimizations
  22. 00:44:37– Bitcoin Cash fork and implementations
  23. 00:46:42– Potential hard fork predictions
  24. 01:46:05– MEV in Bitcoin via game example
  25. 01:47:57– Drivechains delay: Blame the spooks
  26. 01:50:27– Solution: Hard fork
  27. 01:51:59– Drivechains on Litecoin pros/cons
  28. 01:55:01– Litecoin as testbed for Bitcoin tech
  29. 01:57:59– Stablecoins on Bitcoin layers
  30. 02:00:16– Lightning Network limitations meme
  31. 02:01:35– Lightning critique and distractions
  32. 02:04:49– Lightning wheel spin: Blame Jack Dorsey
  33. 02:07:34– Solution: Listen to Bitcoin Takeover
  34. 02:08:28– Too many Bitcoin conferences issue
  35. 02:10:45– Early Bitcoin conferences like San Jose 2013
  36. 02:13:00– Craig Wright blame: Roger Ver
  37. 02:17:08– Solution: Sell all your Bitcoin
  38. 02:18:24– Reasons to sell all Bitcoin
  39. 02:19:47– BSV community and Craig Wright claims
  40. 02:23:28– Mental health in Bitcoin and seeking clarity
  41. 02:27:23– Bitcoin's robustness to issues
  42. 02:31:26– Advice for newcomers on understanding Bitcoin
  43. 02:32:41– TABConf plug and history books
  44. 02:35:05– Fortune-telling wrap-up and farewell

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