-
Notifications
You must be signed in to change notification settings - Fork 388
simplicity: activate on first week of unanimous signalling after block 3333333 #1427
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
simplicity: activate on first week of unanimous signalling after block 3333333 #1427
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fa02ff7
to
fcf644e
Compare
fcf644e
to
fa02ff7
Compare
Rebased. (My diff is identical to Pablo's rebase, but mine has a gpg signature from me on it.) |
fa02ff7
to
816a39e
Compare
Just remembered that we interpret nStartTime as a block height, not a timestamp elements/src/consensus/params.h Line 50 in 246a764
|
Liquidv1 has passed block 3333333 yesterday which would make a neat/memorable start height |
Oof, good catch! |
816a39e
to
6e1854f
Compare
…k 3333333 This block passed on April 14 (so we will activate as soon as this is merged and there is a week of unaminous signalling), and its a nice memorable number.
6e1854f
to
308a393
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reACK 308a393
This patch simply starts signalling for Simplicity in any blocksigner that has it enabled. Once we have one week (10080 blocks) of unanimous signalling, then it activates.