Skip to content
This repository has been archived by the owner on Mar 5, 2024. It is now read-only.

Update nethermind to chiado reboot #3

Merged
merged 9 commits into from
Nov 2, 2022
Merged

Conversation

tropicar
Copy link
Contributor

Now nethermind supports chiado testnet officialy. We have added the snap synchronization too.

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
NETHERMIND_NETWORKCONFIG_P2PPORT: 30404
NETHERMIND_NETWORKCONFIG_P2PPORT: 31309

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
NETHERMIND_NETWORKCONFIG_DISCOVERYPORT: 30404
NETHERMIND_NETWORKCONFIG_DISCOVERYPORT: 31309

Copy link
Contributor Author

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 Show resolved Hide resolved
Copy link
Member

@alexpeterson91 alexpeterson91 left a 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!

@tropicar
Copy link
Contributor Author

tropicar commented Nov 1, 2022

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!
We must use 31309 ports because there are conflicts if we use 30404.

Copy link
Member

@alexpeterson91 alexpeterson91 left a 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

@alexpeterson91
Copy link
Member

@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
docker-compose.yml Outdated Show resolved Hide resolved
docker-compose.yml Outdated Show resolved Hide resolved
docker-compose.yml Outdated Show resolved Hide resolved
commit changes to new port according to new chainID
docker-compose.yml Outdated Show resolved Hide resolved
Copy link
Member

@alexpeterson91 alexpeterson91 left a 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

@alexpeterson91 alexpeterson91 merged commit c268198 into main Nov 2, 2022
@alexpeterson91 alexpeterson91 deleted the tropicar/update branch November 2, 2022 03:37
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants