From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] BIP 113: Median time-past is a HARDfork, not a softfork!
Date: Sun, 1 Nov 2015 19:06:43 +0000 [thread overview]
Message-ID: <201511011906.44081.luke@dashjr.org> (raw)
BIP 113 makes things valid which currently are not (any transaction with a
locktime between the median time past, and the block nTime). Therefore it is a
hardfork. Yet the current BIP describes and deploys it as a softfork.
Furthermore, Bitcoin Core one week ago merged #6566 adding BIP 113 logic to
the mempool and block creation. This will probably produce invalid blocks
(which CNB's safety TestBlockValidity call should catch), and should be
reverted until an appropriate solution is determined.
Rusty suggested something like adding N hours to the median time past for
comparison, and to be a proper hardfork, this must be max()'d with the block
nTime. On the other hand, if we will have a hardfork in the next year or so,
it may be best to just hold off and deploy as part of that.
Further thoughts/input?
Luke
next reply other threads:[~2015-11-01 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 19:06 Luke Dashjr [this message]
2015-11-02 4:27 ` [bitcoin-dev] BIP 113: Median time-past is a HARDfork, not a softfork! jl2012
2015-11-02 5:06 ` Luke Dashjr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201511011906.44081.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox