Developers SBAT to use the same geth version for the bootnode and normal nodes #78
Description
Expected Behavior
It should connect to the bootnode
Current Behavior
@asaj in his attempted deploy of a network set the bootnode tag to be 9568b4a305e6a51b4f4b48dfd3e8bee505ee83cc as they are currently set for all the other geth nodes. However, that resulted in all the geth nodes being unable to connect to the bootnode with the following error:
Bootstrap URL invalid enode=enode://d576d9d033023258a24cf55cd391e32fd4e2bf6bc5bff13d364e30bad2101e6a@10.20.6.43:30301 err="invalid node ID (wrong length, want 128 hex chars)" "
I found the following SO answer https://stackoverflow.com/questions/52835449/the-output-length-of-bootnode-writeaddress-command-is-64-bytes-not-128-bytes-a that leads to ethereum/go-ethereum#17643
What I don't quite get is why verificationrewards, the tag that predates our merge of upstream geth is the one bootnode version that is compatible with the rest of the geth nodes, vs. 9568b4a305e6a51b4f4b48dfd3e8bee505ee83cc which includes upstream is seemingly not compatible. My guess its somewhere around defaults of which p2p protocol we are using, but haven't dug deeper