So I get that bitcoin is all about consensus, right? But it feels like the developers can just ignore the community when they push updates. Like, version 30 came without any consensus, and they just did it anyway. That's kinda worrying, don’t you think?
But hold on a second. That wasn’t really a consensus change, more of a policy shift in Bitcoin Core. Users can totally skip updates if they want or use other clients, so it’s not all doom and gloom.
A lot of users just want things to stay the same, so they don’t push for change. Developers aren’t all-powerful. If you have a good idea, many would collaborate with you. The community also votes on rules, and you can tweak your own node’s protocols too.
I’m not sure there’s a clear distinction between policy and consensus. Those op-return changes stirred up some heat, and honestly, I think the devs control the code no matter what anyone else thinks. How do you even define consensus when it’s not based on a simple voting system?
Consensus rules are set in stone, telling us what makes blocks or transactions legit. Policies are just local rules for what nodes choose to add to their mempool. It’s like saying your container holds liquid, but you only want water while accepting others. That’s the policy.
Thanks for breaking that down. I used to run a Start9 Knots node, but I struggle with the tech side. Who really gets to vote in Bitcoin’s consensus? Is it devs, node operators, holders? And how do we even know the vote results?
I’ve noticed that we might be opening the door to Sybil attacks, where wealthy nodes flood the network with fake support for bad changes. Bitcoin's math is solid, but the human side is getting influenced by Wall Street. Feels like we’re losing the rebel aspect.
Totally see your point. The motto is 'Don’t trust, VERIFY'... but how can we verify decentralization when node ownership is so hidden? That’s a major issue right there.
You bring up some valid concerns about governance. But saying consensus isn’t socially enforced is key. Developers can write any code, but they can’t force adoption. An update without consensus is just noise unless users, miners, and exchanges adopt it.
Sure, updates are optional, but most operators just hit that update button to fix bugs, like how Windows users auto-update. So you can’t count on them to protect against bad updates if they’re not coders themselves.
Miners really matter here. They’re the ones signaling what gets accepted, not the node operators. If you want change, find a mining pool that backs your ideas. Look at the BTC vs BCH split, miners drove the decision.
If you’re right about miners holding the power, that actually raises a red flag for decentralization. If it’s just a handful of miners calling the shots, we’re back where we started, concentrating power.
But come on, how many hobbyist miners are still in the game? Most of the hashrate is in the hands of big pools now. The small-scale miners barely make a dent anymore.
The consensus is whatever rules mining nodes enforce, regardless of OS. Nodes can run on anything but it’s the rules that matter. They can still agree even on different systems.
Remember SegWit2x? Miners were signaling for it, but the broader community didn’t want it, so it fizzled out. Shows how miners don’t always get their way.
That’s a fair point. Trusting node operators who aren’t coders is risky, and we probably don’t talk about that enough. But it’s not like they have real voting power. More nodes don’t equal more influence. They just reject invalid blocks.
I’ve noticed the same thing. If you call out the influence of a few in the U.S., you get labeled a 'fudder.' But v30 proved they’ll push changes regardless of community feedback.