-
Notifications
You must be signed in to change notification settings - Fork 0
Conversation
docker-compose.yml
Outdated
NETHERMIND_JSONRPCCONFIG_ADDITIONALRPCURLS: "http://0.0.0.0:8551|http;ws|net;eth;subscribe;engine;web3;client" | ||
LOG: INFO | ||
NETHERMIND_NETWORKCONFIG_DISCOVERYPORT: 30404 | ||
NETHERMIND_NETWORKCONFIG_P2PPORT: 30404 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NETHERMIND_NETWORKCONFIG_P2PPORT: 30404 | |
NETHERMIND_NETWORKCONFIG_P2PPORT: 31309 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed
docker-compose.yml
Outdated
NETHERMIND_NETWORKCONFIG_P2PPORT: 31309 | ||
NETHERMIND_JSONRPCCONFIG_ADDITIONALRPCURLS: "http://0.0.0.0:8551|http;ws|net;eth;subscribe;engine;web3;client" | ||
LOG: INFO | ||
NETHERMIND_NETWORKCONFIG_DISCOVERYPORT: 30404 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NETHERMIND_NETWORKCONFIG_DISCOVERYPORT: 30404 | |
NETHERMIND_NETWORKCONFIG_DISCOVERYPORT: 31309 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ports need to be kept as is or updated to the new port as defined by the new chain ID, reverting to 30404 does not work!
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All good i mean the P2P ports can be changed to the proper ones not a placeholder because 10200 is the new chainID for Chiado so P2P port for this repo under new specs is 32304
200*10=2,000+30303=32303+1=32304
But it's not necessary now since it works with the old ports we set for it
@tropicar dappnode/DAppNode#457 (comment) can you update the main comment with the fixed formatting and the proper ports for chiado now that 10200 is its chainID per the official config? and idk i guess we should probably just do the ports now since this is the time before publishing updates for the reboot and its planned to be a long term testnet |
fixed engineAPI link display
commit changes to new port according to new chainID
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just went ahead and did the ports. we should for all now. i calculated all already theyre in the above comment link
Now nethermind supports chiado testnet officialy. We have added the snap synchronization too.