diff options
author | Jorge Timón <jtimon@jtimon.cc> | 2015-10-01 02:11:49 +0200 |
---|---|---|
committer | bitcoindev <bitcoindev@gnusha.org> | 2015-10-01 00:11:51 +0000 |
commit | bbf304b0f16519884323f99ade6aa34cb02c2b12 (patch) | |
tree | 1e4e24d9ac71b66fd96ffe919ab552fe76a72a2e | |
parent | 33b7cde62c0550649949290bea76f292f8a3529a (diff) | |
download | pi-bitcoindev-bbf304b0f16519884323f99ade6aa34cb02c2b12.tar.gz pi-bitcoindev-bbf304b0f16519884323f99ade6aa34cb02c2b12.zip |
Re: [bitcoin-dev] Let's deploy BIP65 CHECKLOCKTIMEVERIFY!
-rw-r--r-- | d0/ee74e45f9ccc9047a29bde3811d0e5e2616eaf | 129 |
1 files changed, 129 insertions, 0 deletions
diff --git a/d0/ee74e45f9ccc9047a29bde3811d0e5e2616eaf b/d0/ee74e45f9ccc9047a29bde3811d0e5e2616eaf new file mode 100644 index 000000000..b2fce65f1 --- /dev/null +++ b/d0/ee74e45f9ccc9047a29bde3811d0e5e2616eaf @@ -0,0 +1,129 @@ +Return-Path: <jtimon@jtimon.cc> +Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org + [172.17.192.35]) + by mail.linuxfoundation.org (Postfix) with ESMTPS id 9937D1893 + for <bitcoin-dev@lists.linuxfoundation.org>; + Thu, 1 Oct 2015 00:11:51 +0000 (UTC) +X-Greylist: whitelisted by SQLgrey-1.7.6 +Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com + [209.85.212.180]) + by smtp1.linuxfoundation.org (Postfix) with ESMTPS id DBA0B138 + for <bitcoin-dev@lists.linuxfoundation.org>; + Thu, 1 Oct 2015 00:11:50 +0000 (UTC) +Received: by wicfx3 with SMTP id fx3so5564868wic.0 + for <bitcoin-dev@lists.linuxfoundation.org>; + Wed, 30 Sep 2015 17:11:49 -0700 (PDT) +X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; + d=1e100.net; s=20130820; + h=x-gm-message-state:mime-version:in-reply-to:references:date + :message-id:subject:from:to:cc:content-type; + bh=L9lyPY0tbZ+CiH8q0e3c8OQa2YYBBlhe2RP4ND7J7cA=; + b=dEPpS4DfajqPC44mQQvj4mxTz26K9Fqv16M2fMbQe/Q+ntI9V3cJYNYsgs6ZnhW7bl + encWBJ5s8LnVilCYnvSmDh7nfdvlSllY20y8XuENoGXRuNeKyK4duVXe6D8HY4u1QXbl + aBFiK4vmxdWAAdUAPBWUXrIYQBHEIzerETfJc75Ykd/BN3oVPnTXTHL7xRQ8/lgn9Nlo + lj/vX12YDFwaT5GQkivzcAHM5yw9ylvXbwoRPq5bhbnKMvy84NSS1ULsZHTqsLUKgIOy + HpJfwJvKYboKuTrqeJbrGHHxReVsXOF66RSmZmTEwmUXRlIJKDhJ/6kkzWW7APwDKLA8 + 1sXg== +X-Gm-Message-State: ALoCoQndKySHT1yCR+Na/FCNq3HsDnDoHOzW0xGZRbK4Ai/FVj+4izxOZ40CGypNFWk1YB2650Ya +MIME-Version: 1.0 +X-Received: by 10.180.186.98 with SMTP id fj2mr176621wic.58.1443658309713; + Wed, 30 Sep 2015 17:11:49 -0700 (PDT) +Received: by 10.194.114.199 with HTTP; Wed, 30 Sep 2015 17:11:49 -0700 (PDT) +Received: by 10.194.114.199 with HTTP; Wed, 30 Sep 2015 17:11:49 -0700 (PDT) +In-Reply-To: <CABm2gDqAhjd1721XPjjAiev4coveLM0NUE9ng+W2tgswHiW5bg@mail.gmail.com> +References: <20150927185031.GA20599@savin.petertodd.org> + <CA+w+GKRCVr-9TVk66utp7xLRgTxNpxYoj3XQE-6y_N8JS6eO6Q@mail.gmail.com> + <CAAS2fgSEDGBd67m7i8zCgNRqtmQrZyZMj7a5TsYo41Dh=tdhHQ@mail.gmail.com> + <CA+w+GKRKGS=KZrLtiW8Zbn4EQH_TELfQR+TfrADCMXLR22Q+tw@mail.gmail.com> + <CADm_WcbJoH27H9ckr5sfmE0gh7YbSjKr1uLse0s3b4GTT+jEAA@mail.gmail.com> + <CA+w+GKS01sVXqNY6a39EjqL8NVO6k1Vq6sd0VZjeqF_tsx7OAA@mail.gmail.com> + <CABm2gDpojk4Sb9eVVcFiaQng+mKs+3iWFu_Ep0h7VC1ip7US5Q@mail.gmail.com> + <CA+w+GKTf2vnJ0WdrK1HzFwCx154e=BP=kGcZvGYY7cbcijwLSQ@mail.gmail.com> + <CABm2gDqAhjd1721XPjjAiev4coveLM0NUE9ng+W2tgswHiW5bg@mail.gmail.com> +Date: Thu, 1 Oct 2015 02:11:49 +0200 +Message-ID: <CABm2gDrr2qg4NCCLR0Ut2Jj1Wq2ieRS2EZkM+Ytb0a6ieZrSuA@mail.gmail.com> +From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc> +To: Mike Hearn <hearn@vinumeris.com> +Content-Type: multipart/alternative; boundary=001a11c263d8ba5ec80520ffe4c3 +X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE, + RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 +X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on + smtp1.linux-foundation.org +Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org> +Subject: Re: [bitcoin-dev] Let's deploy BIP65 CHECKLOCKTIMEVERIFY! +X-BeenThere: bitcoin-dev@lists.linuxfoundation.org +X-Mailman-Version: 2.1.12 +Precedence: list +List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org> +List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, + <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe> +List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/> +List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org> +List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help> +List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, + <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe> +X-List-Received-Date: Thu, 01 Oct 2015 00:11:51 -0000 + +--001a11c263d8ba5ec80520ffe4c3 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: quoted-printable + +On Oct 1, 2015 12:14 AM, "Jorge Tim=C3=B3n" <jtimon@jtimon.cc> wrote: +> +> On Wed, Sep 30, 2015 at 11:06 PM, Mike Hearn <hearn@vinumeris.com> wrote: +> >> Exactly, all those "mini divergences" eventually disappear +> > +> > A miner that has accepted a newly invalid transaction into its memory +pool +> > and is trying to mine it, will keep producing invalid blocks forever +until +> > the owner shuts it down and upgrades. This was happening for weeks afte= +r +> > P2SH triggered. +> > +> > For instance, any miner that has modified/bypassed IsStandard() can do +this, +> > or any miner that accepts direct transaction submission, or any miner +that +> > runs an old node from before OP_NOPs were made non-standard. +> +> That is correct. But doesn't seem to contradict anything I said. + +Actually, no, sorry, the second paragraph is not correct as explained by +Greg Maxwell. + +--001a11c263d8ba5ec80520ffe4c3 +Content-Type: text/html; charset=UTF-8 +Content-Transfer-Encoding: quoted-printable + +<p dir=3D"ltr"><br> +On Oct 1, 2015 12:14 AM, "Jorge Tim=C3=B3n" <jtimon@jtimon.cc&= +gt; wrote:<br> +><br> +> On Wed, Sep 30, 2015 at 11:06 PM, Mike Hearn <<a href=3D"mailto:hea= +rn@vinumeris.com">hearn@vinumeris.com</a>> wrote:<br> +> >> Exactly, all those "mini divergences" eventually di= +sappear<br> +> ><br> +> > A miner that has accepted a newly invalid transaction into its me= +mory pool<br> +> > and is trying to mine it, will keep producing invalid blocks fore= +ver until<br> +> > the owner shuts it down and upgrades. This was happening for week= +s after<br> +> > P2SH triggered.<br> +> ><br> +> > For instance, any miner that has modified/bypassed IsStandard() c= +an do this,<br> +> > or any miner that accepts direct transaction submission, or any m= +iner that<br> +> > runs an old node from before OP_NOPs were made non-standard.<br> +><br> +> That is correct. But doesn't seem to contradict anything I said.</= +p> +<p dir=3D"ltr">Actually, no, sorry, the second paragraph is not correct as = +explained by Greg Maxwell.<br> +</p> + +--001a11c263d8ba5ec80520ffe4c3-- + |