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

Set the minimum network protocol version to 170_110 after NU6 mainnet activation #9045

Open
mpguerra opened this issue Nov 20, 2024 · 0 comments · May be fixed by #9058
Open

Set the minimum network protocol version to 170_110 after NU6 mainnet activation #9045

mpguerra opened this issue Nov 20, 2024 · 0 comments · May be fixed by #9058
Assignees
Labels
NU-6 Network Upgrade: NU6 specific tasks
Milestone

Comments

@mpguerra
Copy link
Contributor

mpguerra commented Nov 20, 2024

Motivation

After NU6 activates on mainnet, Zebra should always reject pre-NU6 nodes.

Scheduling

We need to wait for:

  • NU6 mainnet activation - 23 November 2024

Tasks

Update the INITIAL_MIN_NETWORK_PROTOCOL_VERSION to:

  • Mainnet, Nu6
  • Testnet, Nu6

Related work

@mpguerra mpguerra added the NU-6 Network Upgrade: NU6 specific tasks label Nov 20, 2024
@mpguerra mpguerra added this to the NU6 milestone Nov 20, 2024
@mpguerra mpguerra added this to Zebra Nov 20, 2024
@github-project-automation github-project-automation bot moved this to New in Zebra Nov 20, 2024
@mpguerra mpguerra changed the title Set the minimum network protocol version to 170_110 after NU6 mainnet activation Set the minimum network protocol version to 170_110 after NU6 mainnet activation Nov 20, 2024
@mpguerra mpguerra moved this from New to Sprint Backlog in Zebra Nov 20, 2024
@oxarbitrage oxarbitrage self-assigned this Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NU-6 Network Upgrade: NU6 specific tasks
Projects
Status: Sprint Backlog
Development

Successfully merging a pull request may close this issue.

2 participants