Skip to content

Conversation

@btcdrak
Copy link
Contributor

@btcdrak btcdrak commented Dec 10, 2015

BIP68 and BIP113 will be deployed together which simplifies the specification slightly

Copy link
Contributor

Choose a reason for hiding this comment

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

I would just say this: ", and ends at the MTP of the previous block." and get rid of the "or ... BIP113"

BIP68 must be deployed with BIP113 because MTP calculations are
used by this BIP.
@afk11
Copy link
Contributor

afk11 commented Dec 11, 2015

ACK

1 similar comment
@petertodd
Copy link
Contributor

ACK

luke-jr added a commit that referenced this pull request Dec 11, 2015
BIP68: update specification to assume MTP
@luke-jr luke-jr merged commit 6bfc015 into bitcoin:master Dec 11, 2015
@NicolasDorier
Copy link
Contributor

Well, too bad I did not see that before, it broke completely #6312, which was well reviewed and assumed same MTP policy for both nLockTime and sequence lock time.

@btcdrak
Copy link
Contributor Author

btcdrak commented Dec 14, 2015

@NicolasDorier This was agreed at the IRC meeting. I am leaning for 7184 to replace 6312 in any case.

@btcdrak btcdrak deleted the bip68mtp branch December 14, 2015 13:33
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.

6 participants