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

Update x42 segwit activation #301

Merged
merged 1 commit into from
Mar 9, 2021
Merged

Update x42 segwit activation #301

merged 1 commit into from
Mar 9, 2021

Conversation

DennisAMenace
Copy link
Contributor

The activation period passed on the x42 network. We made this change to our clients and did extensive testing and segwit is working when setting this to always active.

The activation period passed on the x42 network. We made this change to our clients and did extensive testing and segwit is working when setting this to always active.
Copy link
Member

@dangershony dangershony left a comment

Choose a reason for hiding this comment

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

Interesting approach, but ok.
Perhaps once we know all blockcore nodes have segwit active we can move it to buried deployments

@dangershony dangershony merged commit 6a743e0 into block-core:master Mar 9, 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

Successfully merging this pull request may close these issues.

2 participants