It uses the script... it changes depending on the blocks ahead... Having the node offline or not is not problematic for the network as long the witness is not registered (aka enabled). This is why I have developed the script. The idea is to never miss blocks... depending on the status of my node, which is what the network needs.
We have many nodes so having this kind of behaviour for a couple of nodes is not harmfull.
I am testing it during the week this week... but I will eventually have to move if offline for some more testing... (hardware wise).
Thanks for the explanation. I was just asking because I wanted to upvote it.
It's upvoted now :)
Appreciate it.
I will be doing some more changes this week. It was a pretty busy Monday, so not sure how much I can work on this on the daily basis... usually, it's like 10 min of focus before wild monsters appear.
So, a full hour of concentration is very niche.
Anyhow, this is simple enough for me to support as it's not very far away from what I have to support daily at work. Just, on a tiny scale. 😁
For example... just a few minutes ago... I have been off sync by 3 blocks... and because that's enough for me to think I can miss, the script just decided to unregister:
And now (at the time of this comment) its already registered again because I am in sync.
With time I plan to make it more reactive. There are lots I know I can improve.
Did you cause this off sync to test the script?
Hey, the script could be run as a service somewhere :)
No... its probably my lousy ISP and the fact that I am extremely distant from the rest of the world (higher latency). It's very common for the node time to time to not be in full sync with the head of the chain. But still that should not affect the block production if you take the right decisions about when to have the node registered or not (hence my he-awm script)
To be honest, I don't know if this is the code that does not yet know to quickly sync when there is lack or slow response from the Streamer nodes. Do you experience the same or you are always in sync?
I have other stuff running that does not behave like this, so, for now I am yet not 100% sure if this is due network or the P2P code.
I am always in sync. In fact, I am surprised that the node is working so smoothly. (knock knock no jinx :) )
It may help that my VPS resides in Lithuania :)
Most likely... but hence any node can easily become out of sync for a diverse amount of reasons. And to react to that is essential for network stability. That's why I would recommend everyone to use something like the script I created.
Can your script, potentially, be used as a sort of load balancer or node switcher too? So you could switch from one node to the other manually? With some safeguard in place that the switched-to node must be in sync :)