Is #Bitcoin mining performing every step of nChain's bitcoin patent claim? 🤯 I've mapped US Pat. 12,277,552 to standard BTC Core + Stratum V1 practices. The findings might shock you. What could this mean for major mining pools? This is the 2nd weakest of 9 patents reviewed!

It’s quite interesting and telling watching them sweat as they see reality closing in

Bitcoin Nation provides an in-depth analysis of building a society on Bitcoin’s principles. It explores why Bitcoin maximalists believe there is no second best when it comes to digital currencies. Engage with new perspectives on how Bitcoin could fundamentally reshape our world.

@CsTominaga

has nchain ever successfully enforced any of their patents? appreciate your commentary

I have no idea. I don't know much about nChain.

How can 2012 software or a 2016 BIP 152 violate a 2019 patent (at earliest)? Prior art. This will go nowhere. The code snippets doesn't even seem to be real code from Bitcoin Core. It's just hallucinated code. I call this AI slop. Stop asking ChatGPT to think for you.

Cool! Discussion and debate. "How can 2012 software or a 2016 BIP 152 violate a 2019 patent (at earliest)? Prior art" Maybe. Stratum V1 (2012) and BIP 22/152 (2012-2016) are excellent invalidity fodder. The patent survived initial examination by arguing a formatting/timing nuance (“full ordered list re-broadcast on every template refresh while hashing”). Whether that nuance withstands PTAB or district-court scrutiny is an open question—but it has not been adjudicated yet. Until it is, anyone using the method after 20 Nov 2024 can potentially (theoretically) be sued for infringement and must raise invalidity as a defense. "The code snippets doesn't even seem to be real code from Bitcoin Core. It's just hallucinated code." “The code snippets don’t even seem to be real code from Bitcoin Core.” Fair skepticism! But those snippets appear to be legit if looking at Bitcoin Core v27.0-rc1, a release candidate you can verify yourself on GitHub (bitcoin/bitcoin, tag v27.0). Here’s where they live: Constructor: CBlockHeaderAndShortTxIDs(const CBlock&, uint64_t) Found in src/blockencodings.h, around lines 93–102. This builds a compact block header with short transaction IDs. PushMessage: m_connman.PushMessage(&pnode, msgMaker.Make(NetMsgType::CMPCTBLOCK, cmpctblock)); Located in src/net_processing.cpp, roughly lines 7021–7035. This sends the compact block to peers. Deserialize Path: A switch-case for NetMsgType::CMPCTBLOCK leading to ProcessMessageCmpctBlock Same file, src/net_processing.cpp, around lines 8848–8859. Handles incoming compact block messages. FillBlock / CheckBlock: In src/blockencodings.cpp, lines ~428–463. Reconstructs and validates blocks. You can clone the repo, checkout tag v27.0, and grep those lines yourself. All of that being said, this is a hypothetical analysis with no warranties of accuracies or fitness. This is not an accusation of infringement and these patents are not mine, and I am not a lawyer (and this is not legal advice), engineer or developer. I am just a Dad, and probably not as smart as you guys. I am just interested in jumpstarting the conversation. All disclaimers from my original post apply here as well.

Only @CsTominaga can shed light on this.

Interesting.

People are afraid to chime in I think.

They definitely are....