From: jl2012@xbt•hk
To: Luke Dashjr <luke@dashjr•org>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP 113: Median time-past is a HARDfork, not a softfork!
Date: Sun, 01 Nov 2015 23:27:50 -0500 [thread overview]
Message-ID: <67789addeb5a0e702998f26cc16a8dbd@xbt.hk> (raw)
In-Reply-To: <201511011906.44081.luke@dashjr.org>
Currently, a tx maybe included in a block only if its locktime (x) is
smaller than the timestamp of a block (y)
BIP113 says that a tx maybe included in a block only if x is smaller
than the median-time-past (z)
It is already a consensus rule that y > z. Therefore, if x < z, x < y
The new rule is absolutely stricter than the old rule, so it is a
softfork. Anything wrong with my interpretation?
Luke Dashjr via bitcoin-dev 於 2015-11-01 14:06 寫到:
> 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
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next prev parent reply other threads:[~2015-11-02 4:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 19:06 Luke Dashjr
2015-11-02 4:27 ` jl2012 [this message]
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=67789addeb5a0e702998f26cc16a8dbd@xbt.hk \
--to=jl2012@xbt$(echo .)hk \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=luke@dashjr$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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