11 questions ...
1. Do Bitcoin Core devs own any Bitcoin themselves (as individuals)?
2. Have they ever indicated that they care about its future as money?
3. What is their incentive for damaging Bitcoin, thus freedom of humanity?
4. Are they knowledgeable about the fight between the central controllers of fiat and decentralised freedom money?
5. There are thousands of alt coins, why use/choose Bitcoin for this purpose?
6. "If it ain't broke then don't fix it", so... what is "broken" that Bitcoin needs the Core 30 changes?
7. Who would have greatest self interest in blackmailing or paying the Core devs to make their op_return changes?
8. Are the Core devs greedy, blackmailed, insane, drugged, stupid, evil or all the above?
9. Will they drop the whole thing at the 11th hour because it was all just an almighty psyop to get weak hands to sell or to test bitcoin diamond hands?
10. Is it just more fiat price suppression FUD and Core 30 changes won't really happen?
11. Other than running Knots or convincing Core devs to reverse their decisions, do we have any other ways to protect Bitcoin against this attack (yes, I see it as an attack)?
I probably can come up with more questions, yet anyone who owns bitcoin needs to ask themselves those questions and get answers well before end September.
Otherwise, we just might have a new website to share with future generations, called "WTF happened in 2025". 🤨😥
Login to reply
Replies (57)
There is pretty much no incentive to update your node software ever again. Maybe this was the intention
Thank you @npub1c6dh...zmx3 🧡✨🙏🫂
ChatGPT responses (see images attached) 🧡


Thank you @Vikingarna1990 🧡✨
Sounds almost like ChatGPT is defending Core... But I do agree with the last screenshot :) We decide what our nodes run... Thank's @npub15tdn...67mv for putting your effort in this important topic and raising awarenes.
Thanks too for your input. 🧡✨ We all need to stay awake, get to the bottom of what is truth and protect this most precious gift to humanity.
What is broken that Core 30 fixes is basically the winner for me. The OP_RETURN limit wasn't broken and it wasn't controversial. Those advocating to remove the limit were using a contrived hypothetical that having a limit drives people to other forms of spam.
The change itself was controversial, not the original limit. It should not have been implemented.
I will never run a Bitcoin Core node again. I will consider node implementations other than Knots if they are developed and Knots gives me a reason not to trust it. But Knots is not just perfectly fine, it does exactly what I want it to do.
But I'll repeat: I will never run a BITCOIN Core node again. That project is dead to me. I would consider a fork that removes the idiotic changes from the last few versions. But at this point, sticking with Knots is also find.
Great questions ⚡️ No matter what the answers are, I love that "we the nodes" truly are empowered to make a conscious choice and that our actions will have an impact. I believe too many of us know that Bitcoin is far more than a "blockchain relaying data" or "1s and 0s." I'm not willing to give up the chance to finally end the repeating karmic cycle suppressing the potential of 7.5 billion people. I can't wait to experience a world where we can explore what it means to be human beyond all these constructs imposed "by fiat" - in a way, many Bitcoiners already are. Thank you, excited to be on this journey with you ⚡️✨
Here's to hope! 🙏🧡🤩
Thanks @leon_21 🙏🫂
6. What's broken? It seems that the real motivation behind this change is that of allowing Citrea to publish arbitrary data larger than 80 bytes. However, why is it that Alpen Labs with their Strata bridge can fit everything they need for *very similar purposes* under 80 bytes? The fact that Citrea sucks shouldn't cause any damage to Bitcoin, hence I'm beginning to think there's unfortunately something shady going on here
Where is the case made that the op_return limit needs to change? Is there one? If so why does it not get circulated and the attention compared to the no change case?
@npub1d3x3...sgfq @npub1s33s...252p
Luke, can you announce a date to hard fork Bitcoin?
Knots node has increased from 1% to 20% in just a few month, most core node runners don't want to upgrade their node because it will remove the spam filter. Its clear you have the backing of the bitcoin community. You can do this. ✊
Hardwire into the bitcoin protocol that the op_return can't be increased above 80bytes (or even lower).
This will solve the problem.
Not an ideal solution, but if this is a real threat, then drastic action is needed!
Keep Bitcoin Alive 🧡
People aren’t taking this shit seriously enough. This is a very urgent issue facing #bitcoin . I’ve been posting about this like a Karen for the past couple weeks and there is virtually no response…very concerning.
crazy, scammy, naive, or stupid
You are the Bcashers of 2025
I think you will find that bitcoin core are following the footsteps of bitcoin cash wanting to change the rules that have made bitcoin the success it has become. The hard fork is to preserve the status quo not change it.
Keep Bitcoin Alive 🧡
Go ahead and hard fork then if you are so sure, the Bcashers were sure they were right too. In the meantime you've got Knots to run if you want.
It's because it isn't the big problem you think it is. You are being manipulated into believing something that isn't as bad as it appears. That is the reason there's not a lot of response. The loudest voices in this are the ones who are frantically worried about something that isn't a concern. It is FUD.
Thank you for your zap ⚡️ 🧡✨🙏
I disagree with you. It’s a problem, there are several unintended or intended consequences to blowing out the OP_Return data limit. I think there is a lack of understanding, laziness and complacency that underscores people’s indifference, not that it’s FUD. This is a technical tug of war over the network. Being diligent and educated on the subject doesn’t make one “frantic.”
Do you run a node? If so, why? If not, why? Do you use core, or knots? Why?
Thank you @npub1sxxh...5k56 @Vikingarna1990 @npub13tku...llwf @npub10a6e...nlkp @npub1dagr...c25u and I hope I remembered all others who gave my post a zap or share. 🧡🙏🫂 This is such an important topic for all Bitcoiners to be engaged with. 🧡✨
Thank you @npub1yzmj...7uh7 and @npub1andy...8jd4 🧡🙏🫂
You are concerned about bitcoin core changing the op_return limit and you are concerned that there aren't enough responses to it. I explained to you why there's not a lot of responses (it's not as big of an issue as you think) except the naive and mostly newbie bitcoiners who have been captured by Kratter. Go ahead and worry and run Knots, the rest of us are going to chill out.
Hi there, where can I follow the Discusion? I would like to read/hear about the Argumentation my self.
Greetings from Germany
Great questions.
I'm asking knots to do the hard fork! 🙏
I am running knots. I support knots nodes. But unless every bitcoin core node converts to knots (or every core node does not upgrade) then eventually the csam will find an updated core node and be inscribed onto the bitcoin block chain.
The hard fork is an insurance policy. If the worst happens and csam flood the bitcoin network and governments all over the world make it illegal to run nodes because of csam and people shit themselves and don't want to run nodes because they don't want csam on their hard drives, then the forked version is there without the csam. And we can switch to the bitcoin chain without the the csam.
Having the hard forked version might be enough for government to not get so heavy handed, because they will be aware that people can switch to the hard forked version hence, the hard forked version could fail, but its mere presence helps the existing bitcoin to continue, because the governments realise its futile being so heavy handed, because everyone will switch to the hard forked version anyway.
Or another scenario is just the threat of a hard fork could push bitcoin core to sort its act out. And pull the plug on removing the anti- spam filters. Problem solved.
The hard fork could be a spectacular failure and existing bitcoin flourishes. Thats a success in my eyes. I just want Bitcoin to succeed fully whether with a hard fork or not.
I dont want a hard fork. But Bitcoin core aren't leaving us with much choice. In an ideal world I would prefer the existing bitcoin flourishes even with csam, enough people look through / beyond the csam on the block chain and see bitcoin for what it is. Bitcoin is freedom. Imo no amount of csam changes this. But we are dealing with people here.
Keep Bitcoin Alive 🧡
Lol! You obviously weren't around in 2017 for the hard fork (you probably haven't even done a full 4yr cycle yet). Luke isn't going to do a hard fork but you can ask him all you want.
I was just ruminating on question #1. All indications are "NO".
Yes he already replied to me on X, 20% knots on bitcoin network isn't enough for a hard fork. Plus he said hard fork isn't the optimal way to combat this problem.
Hopefully core pull the plug on the removing the op_return filter next month. They can see the bitcoin community isn't supporting them. Most core node runners have told me they won't be updating their core node next month, so even the core supporters don't support this.
If core don't take action, and pay attention to what the community is telling them, then over time they become irrelevant.
Not sure where we'd be if it wasn't for Luke and Knots. 💪
That’s a lot of assumptions you’re making….
But if your “explanation” to anything is “it’s not a big deal” with no other reasoning or reference to go along with that then I guess fuck it, it must not be a big deal. You really changed my point of view on the subject 🥴
Well it's nice that you trust Luke. You know he had over 200 bitcoin stolen a couple if years ago, right? He kept them on a laptop & someone got his pgp keys and took the bitcoin. Not only that but because the thief had Luke's pgp keys Luke had to send out a warning for people not to download or update Knots. Anyway I'm sure Knots is perfectly safe these days 👍
Yeah of course because it would be as catastrophic for Knots as the hard fork in 2017 was for Bcash. The miners aren't going to switch to Knots. The only people shouting about this are all the gullible/naive followers of the dumb f*ck Kratter & a few others. Oh well, enjoy your day.
Yeah I did realise the fallout of a hard fork isn't straight forward. The community gets divided and not easy to pull off.
I do hope core get their act together. Surely the rise of knots from 1% to 20% and the fact that a good % of core node runners don't upgrade their node, hopefully this should send a strong message to push core to reassess their approach. We can only hope no lasting damage is created in the interim. 🤞
Thank you @npub1aqn7...2kry 🧡✨🙏🫂
You could begin by hearing and then following their YouTube channels, plus they're here at Nostr as well @npub1wnlu...n3wr and @npub1s33s...252p 🧡✨👍
Have you wondered why Saylor hasn't weighed in on this? He has a lot at stake, right? He hasn't talked about this at all, so obviously he isn't very concerned. What about other big names in the space like Lyn Alden & Matt Odell who say the spam arguments brought up by Knots are way overblown?
I hope they are right. Its wrong to assume its not an issue just because the big names don't think so.
Will you be updating your core node next month? Or do you run a knots node?
Thank you for the zap ⚡️ @npub1s3je...gy7t 🧡🙏🫂
👍
The chart tells the story more accurately than the machine.
“Vote with your feet.”
Thanks for your efforts!
Thanks again @npub1aqn7...2kry 🧡🙏
Thanks for sharing @JL 🧡
Thanks @npub13tku...llwf 🧡🙏
Thanks @npub1z8fa...npau 🙏🫂
Bitcoin Core 30’s OP_RETURN limit increase to ~100KB sparks debate.
Dangers:
• Blockchain bloat risks centralization by straining node resources.
• Spam transactions could clog mempools.
• Legal risks from illegal data storage.
• Deviates from Bitcoin’s monetary focus.
Benefits:
• Enables larger proofs, sidechains, and privacy tools.
• Reduces UTXO bloat from workarounds.
• Aligns policy with consensus rules.
• User-configurable limits.
Clear-Headed Assessment: Dangers outweigh benefits. Increased centralization, spam, and legal risks threaten Bitcoin’s core mission as decentralized money. Benefits like flexibility are minor and better addressed off-chain. Defaults matter, and this could normalize data bloat, risking node wars and regulatory issues.
1. Most likely No
2. You cant care about the future of something youre not vested in. The first proof of caring about bitcoin is owning some
3. Whoever pays the piper dictates the tune. Core developers get grants from shitcoiners trying to bring their grift to bitcoin so, they have to do what the shitcoiners say they need to bring their jpegs to bitcoin or the grant goes away...these developers have to earn a living
4. They are coders....good at coding but otherwise not very intelligent. Being able to code is not the same as wisdom
5. Because all the shitcoins have failed and are failing. more ordinary people who are the victims of the grift are mostly beginning to see it and migrating to bitcoin...to keep the drift going, destroy bitcoin so the crypto space blows up and there's no safety haven for innocents to run to
6. Of course it ain't broke...the objective is to break it
7. All the influencers and vc advocating for the change have an altcoin or a company that entertains shitcoin...Jameson lopp, citrea etc
8. All of the above
9. Their hands have to be forced and the only way to do that is if version 30 does not have support...more knots nodes and existing core nodes refusing to update to version 30
10. No faith in core. We can only hope it was all a fiat price suppression fud...that will be a best case scenario
11. The other way is long term, bitcoin core software or any other cannot be the reference software implementation....there has to be at least 5 or more bitcoin software implementations and more bitcoiners running nodes
Did wonder about it being fiat price suppression fud. That'd be best case scenario. 🫣😥🧡
Everything is built on bitcoin core. That’s why most people aren’t arguing this matter.
The original poster posted are seeking to find out who everyone is that’s also another reason most people aren’t posting.
Appreciate you understanding that for some of us *everything* is built on #BitcoinOnly
"Fuck the Banks
Fuck the politicians
Buy Bitcoin"
-Plato
Maybe ima old but all this knot 🪢 talk just feels like a distraction from @npub1jp98...zj44 being implemented worldwide.
Who would want that?


This is one way to gather intelligence
Ask questions 😂😂😂
View quoted note →
As someone who is currently a beginner node runner, and trying my hand at hobby mining (just bitaxes at home for now), it seemed like this debate was important to keep tabs on and follow closely. That's probably still true, but...
As someone who started out just as a user of bitcoin who relies on actual miners for including my transactions in blocks, and on dedicated node runners who validate transactions, it occurred to me to ask, "How much does this affect regular, pedestrian users of bitcoin?"
Like, if you're not mining, and if you're not running a node, is your use of a bitcoin wallet and bitcoin-sats as a store of value and a medium of exchange really affected in any way by this debate and these proposed changes? As long as there isn't a hard fork, the answer seems to be no, no difference for simple users.
Please correct me if that's wrong, but isn't this all a non-issue for such pedestrian users of bitcoin? If it comes to a hard fork, perhaps that's a different story, but who knows? Not me
#asknostr
Matthew Kratter has some good messages about this, for example 🧡
Thank you!
I also just posted this today and might be helpful as well
🫂🙏

forwardsteps 🪢
Listening to @Samson Mow and @Danny Knowles Good, balanced conversation. Thanks guys. 🧡🙏🫂 Description: Samson Mow is the...
Sorry to bug you again. Here's a super short summary
🌷

forwardsteps 🪢