Comment by anupj
1 day ago
The 184 billion BTC overflow bug is a reminder that even “immutable” code is only as trustworthy as its review process. The real miracle isn’t that a bug happened, but that Satoshi patched it in hours and the network agreed to roll back. Decentralization is great, but consensus is everything
As long as there's singular entity which leads the changes to the protocol, there's no decentralization.
BTC has occasionally obtained community driven patches by distributed consensus rather than a centralized approach (as recently as 2021 with the Taproot soft fork). When Quantum Computing finally becomes a threat to BTC, there will almost certainly be a distributed consensus to update the protocol again. Now what happened with Ethereum could be argued as not so decentralized since the organization (Ethereum Foundation) has extremely strong political influence over the corporations that support it.
I really hate the “someone will certainly solve this problem!” mentality.
You can’t just magically update the protocol to work around the ability of someone to break elliptic curve cryptography. That not how this works. It’s not how any of this works.
5 replies →
Your critique is valid but outdated. This happened way back in 2010. Satoshi disappeared a long time ago now.
There are still influential people, but none with the authority of Satoshi himself.
Bitcoin (et al) is/are not fully decentralized in the sense that a core development team actively maintains and proposes changes, even minimal ones. While it's true that major updates require broad consensus and may be rejected by nodes if controversial, we should acknowledge that certain points of centralization exist, particularly around development and decision making. These often overlooked aspects now carry more financial consequences, especially as Bitcoin becomes more intertwined with regulated financial instruments and political power.
For example, now, many L2s around Bitcoin are fully depending , and influencing on a future change: enabling again the OP_CAT opcode [1].
[1] https://github.com/sCrypt-Inc/awesome-op-cat
2 replies →
See also, the DAO hack.
2 replies →
Indeed. Permissionless blockchain is much less of a technological innovation, but more of a governance innovation, specifically an accountability sink, where instead of a named entity (corporation, institution, person) being in charge, you have this amorphous blob in charge that does come together if its interests are affected (this 184 bn Bitcoin bug, the DAO hack, etc.), but otherwise even in the presence of heinous crimes shrugs and says: "who, me? what can I do?"
I don't understand why that's so attractive to so many participants - possibly because the enormous negative externalities of such a thing more often than not don't fall on themselves, but other, more vulnerable people.
(Not always though: when 200 Bitcoin were stolen from ultra-libertarian Bitcoin developer Luke Dashjr, he came crying for help from the bad bad centralized FBI rather quickly...)
Leading doesn't mean coercion. Leadership in decentralization implies consent.
Comsent by whom? In most "decentralized governance" projects I've heard about, all you need is for the holders of 51% of the tokens to agree, and the holders of the other 49% have no recourse but to leave.
14 replies →
> and the network agreed to roll back
Is there a tiny community of a couple of nodes running the original network?
Just like the Ethereum fork in 2016 [0]. Before then, the battle cries of the crypto advocates were:
...until someone exploited a code defect and took the founders' money, then they re-write history and ignored the hypocrisy.
[0]: https://en.wikipedia.org/wiki/The_DAO
> ...until someone exploited a code defect and took the founders' money, then they re-write history and ignored the hypocrisy.
Not everybody agreed - and so the Ethereum Classic blockchain was created, causing all the problems that go hand in hand with having different, forked blockchains:
> https://en.wikipedia.org/wiki/Ethereum_Classic
That's different because in Bitcoin's case there was a clear violation of the specification, of how it supposed to work. So the bug was fixed to make the software working as it intended to be. If there were two node implementations then one would just stop to work until fixed.
In Ethereum's case there were no violation of any specification. In fact there were no bug in the blockchain itself. Just someone took founder's money, they didn't like it and so they decided to get them back. And note that after that, there were bugs in the nodes code that were breaking the spec (which you should compare to the bitcoin's bug), but because of multiple node implementations only some of the nodes stopped and so we don't care about those issues.
That's probably more important than worrying about bugs in the code. There will be bugs, the concern is what are the rules for rectifying the damage done by those bugs. Plus, where do I go to appeal if I disagree with the decision?
> ignored the hypocrisy
You don't need to exaggerate so strongly.
Powers gonna power
It’s based on a social consensus only, the rest (Nakamoto Consensus, PoW, longest chain, difficulty adjustment, block halving, artificial limited supply, decentralization, censorship-resistant P2P network, open source, etc.) is a combination of a Rube Goldberg machine & crypto bros LARPing.
I halfway disagree:
There is a huge scientific merit of the algorithms for reaching a distributed consensus when not all participants can be trusted (including the fact that the Bitcoin paper uses game theory to give evidence why malicious entities attempting to create another fork will by the mere design of the algorithms have a hard time).
What is, of course, social consensus are some aspects about what it "socially" means that there exists this concrete consensus in the blockchain. By the design of the protocol and its data structures, there do exist boundaries concerning possible "social interpretations" of this consensus, but a lot of aspects are up to different interpretations.
> There is a huge scientific merit of the algorithms for reaching a distributed consensus when not all participants can be trusted
Not quite. Distributed consensus had been solved in the 1980's theoretically and the 1990's practically, even in the presence of byzantine nodes. What Nakamoto consensus was first in was to extend this to the permissionless setting (at enormous expense & inefficiency, and with no benefits, in my view; though enabling large scale rule breaking or "censorship resistance", which some see as a benefit).
Nakamoto Consensus didn’t solved a secure scalable PBFT (Practical Byzantine Fault Tolerant) Consensus.
Bitcoin didn’t solved a forkability and finality problems. Blockchain (or more properly hashchain) is a linked list of hashpointers, and since anyone can create a hashpointer pointing to the head of the hashchain - it means anyone can fork it. And indeed Bitcoin was forked multiple times, and the solution to forks was almost always either centralized and/or social.
IMO PBFT consensus algos have a niche applications anyway, and not required for Electronic Cash implementation, only for decentralized and/or disintermediated Systems-of-Record, but that’s a complete opposite of bearer instruments like electronic cash.
Bitcoin is the OG Birkin Handbag. Valuable for the story. People compete to own a bit of it for that. You can create your own Bitcoin clone and own all of it! But no story, no value.
2 replies →
> There is a huge scientific merit of the algorithms for reaching a distributed consensus when not all participants can be trusted
Yes, they existed a long time ago and aren't wasteful as a way to generate "value".
2 replies →
That "rube goldberg machine" is what makes social consensus possible in a distributed system where everyone is anonymous and there's no single centralized authority.
Yes, but no. The Rube Goldberg of PoW isn't just for show, it's a protection from Sybil attack (not that it makes the economics of it any less of a disaster).
You cherry picked one thing from the list, and even there made a mistake.
In Bitcoin PoW used as a method for leader election of the node composing the list of validated transactions on the ledger (aka block), or even an empty list of transactions (aka Nakamoto-style Consensus).
But without all the Rube Goldbergian nonsense it’s simply an illegal/unlicensed lottery where the participants pay with electricity for the right to earn records on the longest chain (aka UTXO with mining block rewards).
2 replies →
Seems someone missed the boat...
Nocoiners cannot understand Bitcoin?
14 replies →