Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hardfork detection based on node configuration in aeternity.yaml #122

Closed
marc0olo opened this issue Dec 18, 2020 · 3 comments
Closed

hardfork detection based on node configuration in aeternity.yaml #122

marc0olo opened this issue Dec 18, 2020 · 3 comments

Comments

@marc0olo
Copy link

currently the middleware only supports the default networks for hardfork detection.

it would be good if the middleware could detect the network and extract the hardfork height(s) based on the configuration in the aeternity.yaml.

cc: @skkw

@marc0olo
Copy link
Author

@skkw it seems like I am also able to use the networks for local testing:

  • local_roma_testnet
  • local_minerva_testnet
  • local_fortuna_testnet
  • local_iris_testnet

unfortunately an explicit network for Lima is missing. would it be possible to add this in the upcoming release 5.6 of the node? then this would be sufficient for me to perform a local integration testing with the middleware.

@velzevur
Copy link
Member

velzevur commented Dec 29, 2020

@marc0olo the upcoming release 5.6 will have the missing local_lima_testnet. This is orthogonal to this issue regarding the MDW being hard fork aware.

Edit: reported as aeternity/aeternity#3435

@skkw
Copy link
Contributor

skkw commented Mar 25, 2021

Sorted out at the AE Node level.

@skkw skkw closed this as completed Mar 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants