Can we get updated bootnodes?

Mining
1

https://github.com/gluwa/creditcoin/blob/dev/docs/miner-setup.md shows:

–bootnodes “/dns4/bootnode.creditcoin.network/tcp/30333/p2p/12D3KooWAEgDL126EUFxFfdQKiUhmx3BJPdszQHu9PsYsLCuavhb” “/dns4/bootnode2.creditcoin.network/tcp/30333/p2p/12D3KooWSQye3uN3bZQRRC4oZbpiAZXkP2o5UZh6S8pqyh24bF3k” “/dns4/bootnode3.creditcoin.network/tcp/30333/p2p/12D3KooWFrsEZ2aSfiigAxs6ir2kU6en4BewotyCXPhrJ7T1AzjN”

The problem is that it seems like bootnode3 changed but the command wasn’t updated with the new peer ID so you get errors like this:

2023-03-20 18:33:49 The bootnode you want to connect provided a different peer ID than the one you expect: 12D3KooWFrsEZ2aSfiigAxs6ir2kU6en4BewotyCXPhrJ7T1AzjN.

1 Like
2

bootnode2 seems to have changed also:

2023-04-07 19:18:47 :broken_heart: The bootnode you want to connect provided a different peer ID than the one you expect: 12D3KooWSQye3uN3bZQRRC4oZbpiAZXkP2o5UZh6S8pqyh24bF3k.

1 Like
3

@dlebee Might need your eyes here.

1 Like
4

To explain, some nodes have older configurations (not dead pool’s node), since its decentralized we don’t have control on nodes that are improperly configured.
When nodes peer with those specifically bad configured nodes. the nodes give them their peer nodes (with the wrong peer id)
The node logs are just saying that its invalid and it won’t be using the peer coming from the other node that is not configured properly.
It doesn’t cause any issues its just a warning

1 Like
5

The example miner commands should still be updated so the warnings aren’t shown

1 Like
6

There is a little confusion here, the bootnodes are up to date in the mining documentation.

It’s other nodes that haven’t updated their startup command that are propagating the wrong peer to your node causing the warning message.

Due to the nature of decentralization you can’t control what other nodes will propagate to your node.

2 Likes