What is the best practice for not missing any block during an update?
The update_witness command in CLI wallet allows you to change your witness's block signing key. This architecture allows several different downtime-free update procedures according to your specific hosting situation:
...
Thanks theoretical! Great work!
indeed, very useful and sounds like a fool-proof way to do it with no risk of signing double blocks.
One question: how long does it take for the signing key to be updated after you call the update_witness command? As soon as the transaction is processed by the network? After the next maintenance interval? Sth else?
I seem to recall that in BitShares 0.9.x changing the signing key did take a bit of time to go into effect, so that set_block_production true/false was the preferred way. If in graphene the call to changing the signing key takes effect immediately, then that's really nice as it's a much better way of doing it.