You are viewing a single comment's thread from:

RE: Which witness stays on Steem and leaves to Hive?

in #witness-category • 5 years ago

3201346ms database.cpp:803 _maybe_warn_multiple ] Encountered block num collision at block 41812632 due to a fork, witnesses are: [["zzan.witnesses","2020-03-20T08:53:21"],["zzan.witnesses","2020-03-20T08:53:21"]]

repeat * infinity
You should learn how to run a witness, now you're number 10

5 years ago in #witness-category by
$0.06
  • Past Payouts $0.06
  • - Author $0.03
  • - Curators $0.03
1 vote
Reply 4
Sort:  
  • Trending
    • [-]
     5 years ago  

    getting the same thing here

    $0.00
      Reply
      [-]
       5 years ago  

      Thank you, I want you to let me know.
      I want to add a backup node to stabilize the node, but I don't know how.

      $0.00
        Reply
        [-]
         5 years ago (edited) 

        Change the signing key in the backup node config to a new key, and then use a tool like https://github.com/witness-essentials/watcher to swap between active signing keys automatically when you miss blocks.

        Another thing that would vastly improve the stability of the network is to just change your signing keys to STM1111111111111111111111111111111114T1Anm

        You're now witness 7, and I'm 28. I should not be teaching you anything at this point.

        $0.00
          Reply
          [-]
           5 years ago (edited) 

          Thanks for your advice.
          I'm done!

          Ranking is not important.
          I can always descend back down. And You can come up at any time again!!!

          $0.00
            Reply