RE: HivePUD 01-Oct-2020

You are viewing a single comment's thread:

The node issues definitely aren't fun! Unfortunately, you may find that using PeakD via PeakLock directly will go a little more smoothly- right now, Hivemind nodes are all being prepped for the coming hardfork and it appears Keychain is struggling with this a bit. This is sort of a perfect storm- because a majority of Hivemind has been rebuilt from the ground up, those nodes all require updates and replays, and we're getting into the home stretch where all the operators are getting ready and most don't have backups (RPCs are the really expensive nodes, which is part of what all of this is meant to address along with speed and better options for end users.)

Normally, these RPC issues aren't something that we see a lot of going into a hardfork, because the nodes being updated for HFs are the witness nodes- those handle validation of transactions, rather than the signing and broadcasting. (this isn't totally in depth technically accurate but it's enough to sort of outline what's happening.) Most witness operators have backups, and even if they miss a block, you generally don't see the error on your end when you're doing your thing. With many of the Hivemind nodes being fully replayed, everyone else is hammering at the few ones that are up and many operators have restrictions in place to make sure their nodes don't get swamped, so that translates to slow downs. It's pretty crummy, but part of getting all of this work deployed and actually improve speeds and performance. ( I know it doesn't feel like it from an end user perspective at this second.)

It really underlines why it is important we have more and more, why projects need their own, and why bringing the costs and ease of deployment down really matters! It's a kind of annoyingly painful step on creating a Hive that serves users better. Thanks for being patient.



0
0
0.000
1 comments