You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
INFO [10-14|16:20:38.926] Gasprice oracle is ignoring threshold set threshold=2
WARN [10-14|16:20:38.926] Engine API enabled protocol=eth
INFO [10-14|16:20:38.926] Starting peer-to-peer node instance=Geth/v1.14.9-unstable-e9467eec-20240829/linux-arm64/go1.23.0
Fatal: Error starting protocol stack: bad bootstrap node "enode://8e7f762ec60d6e63c2010fa68d041de02420a2d885a451351da996855358add14180cfe95024cb443528cc8ee4c487edc343ca1acd9a4253394509c11da21c40@0.0.0.0:30303": invalid IP (multicast/unspecified)
Fatal: Error starting protocol stack: bad bootstrap node "enode://8e7f762ec60d6e63c2010fa68d041de02420a2d885a451351da996855358add14180cfe95024cb443528cc8ee4c487edc343ca1acd9a4253394509c11da21c40@0.0.0.0:30303": invalid IP (multicast/unspecified)
This can be reproduced when adding ethereum_rust as the first participant in the localnet:
**Motivation**
Running in any position of the `network_params.yaml` except the last
generates an error for the following node when checking our enode url
**Description**
When setting up the `Node` struct, we were using `0.0.0.0` instead of
the actual ip, this PR maps `0.0.0.0` to the local ip there.
This force us to specify the IP of the node in case of using a public
one. The local IP is used due to it being the one needed in Kurtosis. If
this could be an issue for other common forms of running the Node
outside of the CI checks we'll need to go with a more complex solution
using nat for example.
Also if we prefer to not use a crate and obtain it by ourselves I could
go that path!
_Note regarding `tx_spammer`: Unfortunately `tx_spammer` is not working
as we expected, being the first node in the configuration file
completely removed transactions from the kurtosis run (no nodes have
them now), we need to create another issue and investigate that
further._
Resolves#847
This can be reproduced when adding
ethereum_rust
as the first participant in the localnet:The text was updated successfully, but these errors were encountered: