Bitcoin Core, OP_RETURN & Knots Explained | Featuring Rob Hamilton (Anchorwatch)

Adrian sits down with Rob Hamilton of AnchorWatch to unpack how Bitcoin transactions actually work — from inputs and outputs to mining pool dynamics and the ongoing OP_RETURN debate. The conversation covers the differences between Bitcoin Core, Knots, and BTCD implementations, explores the unintended consequences of SegWit and Taproot on chain bloat, and dives into the spam vs. permissionless network health tradeoff. Essential viewing for treasury companies weighing node operations and custody strategies.

Chapters

• 00:00:00 — Intro: Rob’s roots at AnchorWatch, Bitcoin Core, OP_RETURN, Knots & why it matters
• 00:04:10 — BTC transactions: How inputs, outputs & verification work
• 00:09:29 — BTC use case: Risks of storing non-transactional data in blocks
• 00:12:48 — Transaction broadcasting: Mining pool dynamics & private txs
• 00:16:38 — Data inclusion: Node considerations & running your own node
• 00:20:10 — Bitcoin resilience: Can the network handle “graffiti” & threats?
• 00:23:44 — Forks explained: User choices & what happens at a fork
• 00:25:19 — Spam debate: Balancing permissionless network vs network health
• 00:29:16 — Miner incentives: How miners act & influence via economic interests
• 00:32:19 — Bitcoin implementations: Core vs Knots vs BTCD & consensus risks
• 00:38:00 — Segwit & Taproot: Unintended consequences & ordinal creation
• 00:41:23 — BTC Core governance: Role of maintainers & community influence
• 00:46:12 — Freedom vs health: Balancing individual actions with network goals
• 00:49:15 — Where debates happen: Mailing list vs GitHub vs social platforms
• 00:51:56 — Treasury companies: Node running, custody advice & recommendations
• 00:57:04 — OP_RETURN & Segwit: Least harmful ways to add data on-chain
• 01:00:34 — Closing thoughts: Self-reflection, learning & community engagement