RE: Discrepancies with Ecency Delegation API
You are viewing a single comment's thread:
With a background in systems analysis, I enjoyed reading what did here, @themarkymark, to verify whether or not 3 different methods of querying the data produced an identical outcome. And, if not, why not?
Before retiring, I did a lot of similar analysis, with some major ... "surprises" ... produced for my employers. Long story ...
In your position as one of our top Witnesses, would you please provide your perspective on this latest challenge to our Hive blockchain, with HiveSQL going down? In general, what in your judgment would be the best course of action to avoid any reoccurrence of a "single point of failure" having this sort of impact?
And maybe, specifically, since I see reference to HAFSQL as one of your 3 methods, whether or not this is an adequate (superior?) substitute that would serve to avoid a repeat?
P.S. Thank you for reblogging news of the passing of Eric Burgoyne. 🫡
HiveSQL is just a convienience factor, everything is available on chain, but some things are just easier through a standard database. I am not sure if HiveSQL has backup servers and lost them both in this attack or it is just one server.
HAFSQL is only beta right now and doesn't include everything HiveSQL does, but is generally a lot faster in some cases as you don't have to wait over an hour for the db to be updated. I believe it also is only one server.
Okay, thank you. Sounds then, in either case, we are still faced with a single point of failure ...
From the disruptive nature of this attack on HiveSQL, underscoring the benefit it provides to our Hive blockchain, I hope that gets addressed at some point.