Skip to content

Simplify UASF Activation Logic, and update specification.#515

Closed
da2ce7 wants to merge 1 commit intobitcoin:masterfrom
da2ce7:bip148
Closed

Simplify UASF Activation Logic, and update specification.#515
da2ce7 wants to merge 1 commit intobitcoin:masterfrom
da2ce7:bip148

Conversation

@da2ce7
Copy link
Copy Markdown
Contributor

@da2ce7 da2ce7 commented Apr 10, 2017

This Pull Request Enforces That SegWit is activated, even if the hash-rate is very very slow.

@shaolinfry
Copy link
Copy Markdown
Contributor

I disagree with this change.

@luke-jr
Copy link
Copy Markdown
Member

luke-jr commented Apr 10, 2017

It's unclear to me how BIP 141 nodes will react to a post-timeout activation.

@da2ce7
Copy link
Copy Markdown
Contributor Author

da2ce7 commented Apr 10, 2017

@luke-jr from my understanding they will not enforce SegWit.

@shaolinfry
Copy link
Copy Markdown
Contributor

You cannot change the activation parameters of another BIP mid deployment. BIP148 is it's own soft fork.

@mkwia
Copy link
Copy Markdown

mkwia commented Apr 10, 2017

I don't think this is a good PR.

@luke-jr
Copy link
Copy Markdown
Member

luke-jr commented Apr 10, 2017

@da2ce7 but they may reject blocks as invalid because they fetch the full block, and don't consider witness data valid in it...

@luke-jr
Copy link
Copy Markdown
Member

luke-jr commented Apr 10, 2017

Closing due to NACK from @shaolinfry

@luke-jr luke-jr closed this Apr 10, 2017
It is hoped that miners will respond to this BIP by activating segwit early, before this BIP takes effect. Otherwise this BIP will cause the mandatory activation of the existing segwit deployment before the end of midnight November 15th 2017.
It is hoped that miners will respond to this BIP by activating segwit early, before this BIP takes effect. Otherwise this BIP may cause the mandatory activation of the existing segwit deployment before the end of midnight November 15th 2017.

This BIP mandatory enforces SegWit within one full 2016 block retagat intivals after August 1st 2017.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

"retagat intivals"?

In chainparams.cpp: Set BIP 9 flag to never time-out.

- consensus.vDeployments[Consensus::DEPLOYMENT_SEGWIT].nTimeout = 1493596800; // May 1st 2017
+ consensus.vDeployments[Consensus::DEPLOYMENT_SEGWIT].nTimeout = 999999999999ULL; // Never (BIP 148)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

What happens to Core nodes if UASF nodes activate SegWit after November 2017? Core nodes will only recognize SegWit lock-in until November 2017.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants