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.

Sign up for GitHub

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

Jump to bottom

Add config field for accepting network upgrade activation heights #7840

Closed
Tracked by #7845
mpguerra opened this issue Oct 26, 2023 · 0 comments · Fixed by #8383
Closed
Tracked by #7845

Add config field for accepting network upgrade activation heights #7840

mpguerra opened this issue Oct 26, 2023 · 0 comments · Fixed by #8383
Assignees
@arya2
Labels
A-consensus Area: Consensus rule updates A-network Area: Network protocol updates or fixes C-enhancement Category: This is an improvement C-testing Category: These are tests S-needs-triage Status: A bug report needs triage

Comments

@mpguerra
Copy link
Contributor

mpguerra commented Oct 26, 2023 •
edited by arya2
Loading

Motivation

This field is needed for configuring custom testnet activation heights without hard-coded changes or compilation features.

Part of #7970
@mpguerra mpguerra mentioned this issue Oct 26, 2023
Open
13 tasks
@mpguerra mpguerra added this to Zebra Oct 26, 2023
@github-project-automation github-project-automation bot moved this to 🆕 New in Zebra Oct 26, 2023
@mpguerra mpguerra added C-enhancement Category: This is an improvement P-Medium ⚡ A-network Area: Network protocol updates or fixes S-needs-triage Status: A bug report needs triage labels Oct 26, 2023
@arya2 arya2 changed the title Add config field or CLI option for accepting network upgrade heights Add config field for accepting network upgrade heights Feb 26, 2024
@arya2 arya2 mentioned this issue Feb 26, 2024
Closed
@arya2 arya2 changed the title Add config field for accepting network upgrade heights Add config field for accepting network upgrade activation heights Feb 26, 2024
@arya2 arya2 added C-testing Category: These are tests A-consensus Area: Consensus rule updates labels Feb 26, 2024
@arya2 arya2 mentioned this issue Feb 26, 2024
Closed
14 tasks
@mpguerra mpguerra moved this from New to Product Backlog in Zebra Mar 6, 2024
@mpguerra mpguerra added this to the Regtest milestone Mar 6, 2024
@mpguerra mpguerra moved this from Product Backlog to Sprint Backlog in Zebra Mar 6, 2024
@arya2 arya2 closed this as not planned Won't fix, can't repro, duplicate, stale Mar 18, 2024
@github-project-automation github-project-automation bot moved this from Sprint Backlog to Done in Zebra Mar 18, 2024
@arya2 arya2 reopened this Mar 19, 2024
@arya2 arya2 moved this from Done to Sprint Backlog in Zebra Mar 19, 2024
@arya2 arya2 moved this from Sprint Backlog to Review/QA in Zebra Apr 11, 2024
@arya2 arya2 mentioned this issue Apr 11, 2024
Merged
9 tasks
@arya2 arya2 self-assigned this Apr 11, 2024
@mergify mergify bot closed this as completed in #8383 Apr 19, 2024
@github-project-automation github-project-automation bot moved this from Review/QA to Done in Zebra Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@arya2 arya2

Labels
A-consensus Area: Consensus rule updates A-network Area: Network protocol updates or fixes C-enhancement Category: This is an improvement C-testing Category: These are tests S-needs-triage Status: A bug report needs triage
Projects
Zebra
Status: Done
Milestone
No milestone
2 participants
@mpguerra @arya2