From: Luke Dashjr <luke@dashjr•org>
To: jl2012@xbt•hk
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP 113: Median time-past is a HARDfork, not a softfork!
Date: Mon, 2 Nov 2015 05:06:36 +0000 [thread overview]
Message-ID: <201511020506.37593.luke@dashjr.org> (raw)
In-Reply-To: <67789addeb5a0e702998f26cc16a8dbd@xbt.hk>
On Monday, November 02, 2015 4:27:50 AM jl2012@xbt•hk wrote:
> 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?
I agree, false alarm. Somehow I had confused the comparison of locktimes this
morning. :(
Sorry about that,
Luke
prev parent reply other threads:[~2015-11-02 5:06 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
2015-11-02 5:06 ` Luke Dashjr [this message]
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=201511020506.37593.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jl2012@xbt$(echo .)hk \
/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