Today, the entire Hive network runs on a single consensus implementation:
hived, the C++ node. Every witness, every full node, every exchange — all running the same codebase.That's a single point of failure. If there's a latent consensus bug in
hived, there is nothing to catch it. Every node makes the same mistake in the same way, and we only find out when something breaks in production.
¿What? How comes nobody has commented or mentioned something like this before and yet they (many) still continue to preach and boast about the invulnerability of the system and the integrity and resilience of the entire protocol and network?
Has no one ever told them about the supreme importance of having a backup system or at least a secondary, temporary and transitional plan B in case things as they currently work go completely to hell?
Or perhaps it's that they simply don't care anymore, or maybe those who really should care about these things just don't care at all if everything gets tits up because they have already mined and extracted enough do$h to retire and stop making their lives miserable by coding and trying to fine tune and refine the system for less than 2.5k nobodies who are really of no interest for them? ¿Huh?
Well, in any case, the only thing I can do at this point is wish you luck in what you set out to do and that you manage to accomplish it successfully without giving up in the process.
Cheers!!
RE: Let's talk about a little project I've been working on for the last bit: Gopherd, a go implementation of the HIVE protocol