I ran into this problem with a custom Ethereum implementation suddenly unable to connect to the Ethereum bootnodes. Specifically, I ping bootnodes and get no response. I could set up my own bootnode and receive a response fine, unless I set a v5 flag to on, in which case I get an error: "bad prefix". I found the place in the code that corresponds to this error, apparently there has been some changes made to do away with the message hash on all packets and replace it with a prefix string, which is currently the empty string? This breaks both v3 and v4 packets, not sure if this is running on bootnodes? Relevant code below:
Hi,
I ran into this problem with a custom Ethereum implementation suddenly unable to connect to the Ethereum bootnodes. Specifically, I ping bootnodes and get no response. I could set up my own bootnode and receive a response fine, unless I set a v5 flag to on, in which case I get an error: "bad prefix". I found the place in the code that corresponds to this error, apparently there has been some changes made to do away with the message hash on all packets and replace it with a prefix string, which is currently the empty string? This breaks both v3 and v4 packets, not sure if this is running on bootnodes? Relevant code below: