|
|
|
|
|
by nailer
1269 days ago
|
|
I don't think you've worked on distributed systems before. Consensus algorithms do not solve bugs. Say, being human, and a software author, you didn't anticipate a node with a single ID producing two valid blocks (someone's blue/green setup went active/active). Yes, one could say that you should have anticipated a single node producing two valid blocks and programmed defensively. I would argue that many people would not have, and even if they did, they would not anticipate other potential bugs. This does not mean the design is centralised: it's just that it's a peer-to-peer design with bugs. Like all software, ever. You can read cause and effects of the outages, including the one above, here: https://status.solana.com/history |
|
Not yet, but that's definitely an open problem that needs good solutions, and bugs aren't an excuse for allowing centralization.
The "solution" to bugs being used by Ethereum is simply: move very slowly and try very hard to not create bugs in the first place. But others, i.e. Polkadot, are trying to come up with ways of reaching consensus around reverting or patching bugs.
> I would argue that many people would not have, and even if they did, they would not anticipate other potential bugs.
Well, tough shit. This isn't a space with room for errors, certainly not ones this big.
> This does not mean the design is centralised: it's just that it's a peer-to-peer design with bugs. Like all software, ever.
It does mean it's centralized.
If you are skeptical that it's even possible to avoid bugs, well yeah, me too. That's why crypto is a high-risk space: bugs aren't really acceptable, but so far we really haven't found a way to completely avoid them.