Hi, Validators,
We have identified some rogue
peers sending out consensus messages signed with non-active blskeys on harmony mainnet.
Those nodes will be blocked in the network later once we implemented the block list feature as described here (https://talk.harmony.one/t/nodes-sending-invalid-p2p-messages-to-the-network/786)
It may occur if you are running legacy version of node program prior to v2.1.9.
For now, please do a self check on your node or backup node, and taking them offline if they are in the rogue
peer list.
https://stedolan.github.io/jq/download/
curl -s --request POST 'http://127.0.0.1:9500/' --header 'Content-Type: application/json' --data-raw '{ "jsonrpc": "2.0", "method": "hmyv2_getNodeMetadata", "params": [], "id": 1}' | jq .result.peerid
Please upgrade to the latest release of v2.2.0 (https://github.com/harmony-one/harmony/releases/tag/v2.2.0). The new release will not sign/send out consensus messages if the blskey is not active in the current committee.
check .hmy/blskeys
You may check your node version by running the following command in the console.
./node.sh -V
QmbnAEajvZ9LD6fXSEBSbHfSEdEaCdW4ZurqgXjVFtXfiv
QmQyvhNnWZhdUxPBaFLX6is9tyUmwU9HCF72D5voTyk4L1
QmaL1UJKmYCWjofXZAnj3v9wHME6pp2AxBqmVMnwYFyD2z
QmbhzzZfrvGEYGbJb4J5PEH49U1Rij5AKwxwbE7jdHaXsA
QmbkUogCRth6ZU5pQix3T2sqgqs41LFK6SnmeEUE7mSLMS
QmedFVmsiv7c7yEqhyRpT8Q9XSH5DmxKFWBV3Qc3CvJQrX
QmPBKJyk5XfkTPNPDq14GYapYjPg1SX4Qd6L2qhhSxhQhG
QmPcSauz9muL7tjPbD7qLYBYBppSSa5nyp3qHjoNKQMKDt
QmPCxfdjRCMESrsR497c1Y4mf4eHaTd74EBGRum8Zy6XWN
QmPQvv2VU56FPMaUBpNdqfXbsmXJnTUUDvkGBBAJipMYe9
QmR8Uehk9G518ZAycVn8BHTS7YSnwVnSS4KdWwfwF1kyW9
QmYtmRGC6K17nYrdj57qAu5BSuMs6wsALTjbi7CbLNx7SN
QmZYL4bFrjqDjx43e3WsGzCxiQnDom3XkxsXkDPfp154GL
QmcX6BYPeoy2g6XaPZSaajjwDZuubWDktg9bgpzi8A3ae8
QmR8Uehk9G518ZAycVn8BHTS7YSnwVnSS4KdWwfwF1kyW9
QmWYwrrFxx3aps4RdUUiFpbfwfVU4we7zyABLZBcoP6N5G
QmX5BWmgb4PHtWgFg3K5MjG2jKXX6tqePq1QFiwS2Ni9aq
QmT8PGPQx9KwpgaqAfsNXXCH1gRU5SaAtGYTfYFFS9uhsD
QmUApSb3eJ6aJah5vbDsjdRo8iX8MRVTHoKfZGQ1XHk6JR
QmXR5YoUuNmXVsHVrLcBsQFGRnKk8HbCsBSVto1Tn6B4uE