Even though I'm a Bitcoin maximallist. I'm losing faith in its ability to stay decentralized when the node software is clearly captured by devs who are paid off by miners and ethereum wannabe startups.
Which coin confiscating BIP? The only BIP I'm aware of is the one that sets reasonable limits on fields designed to hold short text, not blob data.
No, I'm just annoyed by all the ignorant people who want BTC to turn into ETH
Today, we released a new version of SV2 Reference Implementation (SRI).
Starting today miners no longer need a custom BTC Core fork to build block templates with SV2. The bitcoin_core_sv2 crate is integrated into JDC and Pool, enabling direct communication with Bitcoin Core v30. This improves the UX and keeps SRI implementation-agnostic going forward.
With this release, we’re rolling out Docker support for SV2 Apps, making cross-platform deployments easier and shipping binaries for all major platforms. This is the first step toward a smoother UX. In the next release, we plan to ship UI for our miner-side apps: JDC and tProxy.
We’ve split the project into two repositories:
/stratum containing low-level protocol crates and /Sv2-Apps for end-user applications.
This makes the ecosystem easier to understand, contribute, and build on.
Want to test all the new improvements yourself?
Use our Web Deployment Wizard to spin up the full SV2 stack (Including your own pool) and share your feedback with the community.
https://stratumprotocol.org/get-started (for miners)
https://stratumprotocol.org/developers (for devs and full stack deployments)
Running Core to allow large op_returns is like writing a novel in the "delivery instructions" section of a pizza delivery order, and then saying "don't get mad, bro" when the kitchen receipt runs out of printer paper.
Censorship is forcing node runners to relay everything regardless of what their beliefs are.. knots allows you to speak your beliefs without being forced to conform to the corrupt Core developer's goal of turning BTC into a garbage can.
💡 New Tutorial on Plan ₿ Academy
Write a message directly on the Bitcoin blockchain using Electrum and OP_RETURN.
This guide by Manuel Proquin shows you how to:
• Convert your text to hex
• Build the OP_RETURN output
• Broadcast and verify your inscription on-chain
A permanent message — on an immutable ledger.
👉 https://kutt.planb.network/A34SK2
Using the op_return as blob storage is like writing a novel in the "delivery instructions" field in a pizza delivery order.
I would like you to imagine this: what if Google Drive or Dropbox's business model was to use your hard drive space to store other people's viruses, documents, and images? How much would you want them to pay you for that privilege? Because at the moment, Bitcoin nodes are not being paid to store your crap.
Let's keep plummeting until all the leverage gets crushed
New BIP proposal that actually addresses the inscription plague: https://bip444.github.io/
BIP-444 implements temporary consensus limits on data fields to make inscriptions technically and economically impractical while preserving ALL monetary use cases:
- 34-byte scriptPubKey limit (covers all modern payment types)
- 256-byte data push limit (kills image storage)
- Disables unused opcodes being exploited for spam
The economic case is simple: Monetary transactions pay once for one-time value. Inscriptions pay once for PERPETUAL hosting by every node forever. It's an arbitrage exploit where miners capture 100% of revenue while node operators bear 100% of eternal storage costs.
This isn't censorship - it's fixing a specification bug. Every protocol has boundaries. We already limit block size, script size, and disable certain opcodes. This just aligns the boundaries with Bitcoin's actual purpose: money.
The temporary nature (1 year) gives time to develop longer-term solutions while immediately protecting the network. Though honestly, these limits should be permanent. Bitcoin is money, not a decentralized Dropbox for your jpegs.
Core devs will fight this because they've confused "neutrality" with allowing network vandalism. But node operators who actually bear the costs understand: inscriptions are parasitic.
Run Bitcoin Knots. Support UASF if needed. Protect Bitcoin as money.
#Bitcoin #BIP444 #Inscriptions #NodeRunners #BitcoinKnots
Except you trigger a different tax called capital gains.. you are taxed on avoiding inflation.
As Michael Saylor said, if he wanted to destroy Bitcoin, all he would do is hire 100 developers and tell them to "make Bitcoin better"
Taking my ability to filter my node as I see for is taking away my ability to speak my values.
I run knots because it allows me to transmit the mempool that I believe in. THAT is freedom.
The Merge is finally coming!
Make sure to upgrade to the latest node software for the best-in-class and most socially scalable consensus algorithm ever invented for a blockchain.
You can download it here: https://bitcoin.org/en/download
- nostr:npub157y6gz0l0rfhw220rfwnujeff6q2mec33nzkwz23umkrt6482exq8e60gr
#BitcoinTwitter
Run knots to save Bitcoin. Large op_returns will cause mempool congestion, slowing down real transactions, just so some greasy startups can flood the world's best store of value with cat pictures.
I would love to spend my BTC, but I live in a city of 1.5 million people and nowhere accepts BTC.
You sounds like you would fit right in with the UK government. Their Internet oversight and licensing are right up your alley.
We need to close the inscription bug and hardcode an 83b op_return
Filling up the mempool with images and non monetary op_returns benefits nobody.
Genuine transactions get crowded out of blocks, slowing down the speed of real transactions.
We seriously need to hardcode an 83b cap on the op_return, and close the inscription bug.
Hey there Luke, what do you think the likelihood is of successfully forking BTC to hardcode the op_return filter, and eliminating the inscription exploit?