🎁 “Mastering Taproot” is now free to download. This book is written from a builder’s perspective: raw transactions, scripts, witness analysis, and reproducible testnet examples. Pay if you can — learn if you need. 🔗 leanpub.com/mastering-tapr… #Bitcoin #BitcoinCore #Bitcoindev
_________ . ---""" """--- . :______.-': : .--------------. : | ______ | | : : | |:______B:| | | > SYSTEM UP | | |:______B:| | |…
Core takeaways: The v30 change to OP_RETURN was never about “making JPEGs easier to put on-chain.” It’s an infrastructure update forced by emerging L2 protocols like BitVM and Citrea. This is a policy change — not a consensus change — and it does not create any risk of network…
New chapter from How People Tried to Push Non-Transaction Data into Bitcoin. Chapter 9 examines Runes from an engineering standpoint: a modern OP_RETURN-based token protocol that deliberately avoids the failure modes of witness-stuffed designs like BRC-20. Runes replace global…
New chapter is live. Chapter 8 — Ordinals: Taproot Envelopes and the Data Layer Explosion This chapter is about something bigger than “NFTs on Bitcoin.” It’s about how: Taproot quietly removed the 520-byte limits, witness became an unbounded data layer, OP_FALSE OP_IF turned…
One quick clarification after yesterday’s thread: I’m not taking a side in the filter debate. What I’m interested in is the structural gap in how different groups model Bitcoin. Some people reason locally (mempool, OP_RETURN bytes, direct limits). Others reason globally…
People say: “Bitcoin is dead.” Bitcoin: “Hold my Taproot.” Undertaker-level comeback every cycle. But behind the meme is a very real reason why Bitcoin never dies: • It’s a protocol layer, not a product • It’s becoming the global settlement layer • It has native value…
Bear: “Bitcoin is dead.” Bitcoin: “Hold my taproot.” 😵💫👇 If you want the serious version behind the meme — 这里是我刚发的长文（历史＋工程＋金融三重角度）
This whole thread is a great example of a recurring pattern in the OP_RETURN debate: Two groups are speaking from completely different layers of the Bitcoin stack. One group sees the system like this: “Contiguous data goes into OP_RETURN → so just limit OP_RETURN.” The other…
First, I just want to clarify that contiguous, to me, is only possible in OP_RETURN. All other systems require additional recompiling, so I don't consider this "contiguous" per se. And frankly you lost me on some of the alternate methods you're mentioning. My point is: there is…
New post: "The Anatomy of Bitcoin Scripts: From P2PKH to Taproot" Every Bitcoin address — from 2009 to today — follows one pattern: commit-reveal. This piece breaks down stack execution across all address types with ASCII visualizations. Companion notes to my book Mastering…
Before SegWit: Data embedding was a hack—Counterparty & Stamps squeezed bytes into scripts never meant to hold them. After P2WSH: Scripts became legitimate data containers. 75% cheaper. Structured witness space. The architecture that made Ordinals possible. Chapter 7 breaks…
🚨 New chapter published: “Stamp / Stamps — Bare Multisig as ‘Image Container’”. In this piece I explore how Stamps transformed the multisig structure of Bitcoin from a signature scheme into a data-warehouse: • 31-byte chunks encoded as fake pubkeys • Bare multisig outputs…
One additional observation from working through the Counterparty reconstruction: Fake-pubkey grinding is one of the cleanest historical examples showing the exact boundary between Bitcoin’s consensus rules and Bitcoin Core’s policy layer. Consensus requires that: — every pubkey…
📘 Working on Chapter 5 of my upcoming book, How People Tried to Push Non-Transaction Data into Bitcoin. This chapter covers Counterparty — the first protocol to systematically use bare multisig as a data container. I’m documenting the engineering path: — OP_RETURN as…
“It’s very attractive to the libertarian viewpoint if we can explain it properly. I’m better with code than with words though.” — Satoshi That’s exactly why I built this project the way I did — not as a debate about Bitcoin, but as reproducible engineering history.
1/ I’ve released my new research project: “How People Tried to Push Non-Transaction Data into Bitcoin.” A reproducible engineering history of Colored Coins → Omni → Counterparty → Stamps → Ordinals → Atomicals → RGB. GitBook: btcstudy.gitbook.io/bitcoin-data-e…
Here’s the part most people missed about Bitcoin Core v30: The OP_RETURN change wasn’t about Ordinals — it was about BitVM. Clementine needed ~144 bytes of anchor data and had to create unspendable Taproot outputs, permanently polluting the UTXO set. Core developers chose a…
United States 趨勢
- 1. Lakers 49.6K posts
- 2. Dillon Brooks 6,846 posts
- 3. Bron 24.5K posts
- 4. Giants 85.1K posts
- 5. #WWERaw 70.6K posts
- 6. Dart 36K posts
- 7. Patriots 130K posts
- 8. Suns 18.9K posts
- 9. Drake Maye 24.2K posts
- 10. Collin Gillespie 2,021 posts
- 11. #AvatarFireAndAsh 2,905 posts
- 12. Diaz 33.8K posts
- 13. Ryan Nembhard 4,133 posts
- 14. Devin Williams 7,710 posts
- 15. STEAK 10.4K posts
- 16. Gunther 15.1K posts
- 17. Pats 16.2K posts
- 18. James Cameron 4,460 posts
- 19. Devin Booker 2,619 posts
- 20. Joe Schoen 3,439 posts
Something went wrong.
Something went wrong.