We all have the same tools. If you’re asking why Core made changes like relaxing relay limits on OP_RETURN, go read the actual discussions. This didn’t happen overnight — it’s been openly debated for years. But those debates happen in the places where devs build, not on Twitter or Nostr.”

• Bitcoin Core PRs & Issues:

https://github.com/bitcoin/bitcoin/pulls

https://github.com/bitcoin/bitcoin/issues

• Mailing List (Bitcoin Dev):

https://lists.linuxfoundation.org/pipermail/bitcoin-dev/

• IRC Logs (Technical meetings):

https://bitcoincore.reviews/

You people complain and claim that bitcoin core did not communicate this right. As a node runner if you want to participate in bitcoin development you need to be where discussions happen.

People love Bitcoin for being decentralized — until it feels inconvenient.

Then suddenly they expect devs to ‘explain themselves,’ like it’s a subscription service.

Bitcoin is an open protocol, not a company. If you want to understand it, show up where it’s built. Nobody owes you a push notification.

Reply to this note

Please Login to reply.

Discussion

My point is bitcoin is people and requires trust.

If the people of bitcoin don't care, it will change into something else.

Its not strictly code. Human emotion, incentives, and intentions matter.

But people care and changes on protocol level take ages to go through. That's the beauty of consensus of node runners.