path: root/bf/a86f56ef09792a870d55a060f91f64398cb527

Return-Path: <dscotese@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id DC860948
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 14 Nov 2015 02:10:32 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-oi0-f42.google.com (mail-oi0-f42.google.com
	[209.85.218.42])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 801BF15B
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 14 Nov 2015 02:10:30 +0000 (UTC)
Received: by oiww189 with SMTP id w189so59501701oiw.3
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 13 Nov 2015 18:10:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:date:message-id:subject
	:from:to:content-type;
	bh=kXFg5nvhiwpkxx7URd2VQGf+ii1f/sVNudzP1DkoKfk=;
	b=E68pFhjJxyvxg7/VROI3b4zyUckBccbAB4maJ1JtJHqRjKt4N3rcim/8no2H0vmwFZ
	8VgwPKGp6XnVu8A/vf5pS3A9EmiD+iuYPq4CZo9H962e5C+kgocp/8xda5PUvl8pETtd
	pox9g+krBliQXkuIAsKnNk/xTFrvDzM/qGjBQu2p+zDMWtuIxKAy8qBEjNkxGsGLJYQv
	z9f2gY6Fe9gMgfxyVJJ0XHJz7I93/VU4bKk2BARdvaBMoX0+iTwsN+H5vuQQ03ZVKP1H
	7MNrQjiHRu005sbutYpluleRYzb0e5msuk2F+aqqeH0FjTOsEIDdrBnlqLQrTW9FYi/4
	bo2A==
MIME-Version: 1.0
X-Received: by 10.202.93.85 with SMTP id r82mr13937869oib.35.1447467029716;
	Fri, 13 Nov 2015 18:10:29 -0800 (PST)
Sender: dscotese@gmail.com
Received: by 10.60.16.39 with HTTP; Fri, 13 Nov 2015 18:10:29 -0800 (PST)
In-Reply-To: <20151113131353.GA26622@amethyst.visucore.com>
References: <20151113131353.GA26622@amethyst.visucore.com>
Date: Fri, 13 Nov 2015 18:10:29 -0800
X-Google-Sender-Auth: IZAsCwoGeGlbhhDu6z1Jy9N54UM
Message-ID: <CAGLBAhcMMLnze8N=OLK0EypatRKEhFkHTJDo_KJyc_A1h1d-uA@mail.gmail.com>
From: Dave Scotese <dscotese@litmocracy.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a113d41ae21666f052476aec4
X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,URIBL_BLACK
	autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Sat, 14 Nov 2015 03:13:34 +0000
Subject: Re: [bitcoin-dev] Bitcoin Core 0.11.2 released
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: Sat, 14 Nov 2015 02:10:33 -0000

--001a113d41ae21666f052476aec4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I decided to try to certify Wladimir's PGP keys (the old one (2346C9A6)
first, and then the new one (36C2E964), since it was signed with the old
one).

I visited
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-June/009045.ht=
ml
to see that the new key was referenced in a message signed by the old one.
I figure it's safe to assume that if the old key actually signed that
message, then the core dev using <laanwj at gmail.com
<https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>> is an
actual core dev (that's all I'd be worried about).  So I copied the text
from ------BEGIN PGP SIGNED MESSAGE----- to -----END PGP SIGNATURE----- to
my clipboard and asked Kleopatra (on Windows) to verify it.  It says the
signature is bad.  If I alter the text of the email (so the signature would
be have to be different to be valid), it says exactly the same thing.  So
maybe something is wrong with Kleopatra on Windows.

However, the SHA256SUMS.asc file I got from the magnet link posted in the
email (below)  verifies just fine using the new key (36C2E964).  So I
figure Kleopatra is not broken.  It recognizes that the old key was used to
create the signature in that old email, but it says it's invalid.  Has
Wladimir been secretly replaced by someone who doesn't have access to the
private key for 2346C9A6?  Can you make a (bad) signature look like it was
made using a key you don't have? The whole reason for signing is so that we
will know if something like that happened.  So did I do something wrong?
(I mean, besides using Windows).

I believe this is the expected result if someone took something Wladimir
signed and ripped off the signature and pasted it below this new message to
make everyone think the new message was genuine.  Maybe Wladimir made an
edit after the signature was attached.  Or maybe it got changed when it
went through the email system.  It would be nice to know.  Anyway, I fell
back on Windows security and ran the install because it said it verified
that the publisher was "The Bitcoin Foundation".


On Fri, Nov 13, 2015 at 5:13 AM, Wladimir J. van der Laan via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Bitcoin Core version 0.11.2 is now available from:
>
>   <https://bitcoin.org/bin/bitcoin-core-0.11.2/>
>
> Alternatively, through bittorrent:
>
>
> magnet:?xt=3Durn:btih:d6d3387160f7e14f6f27dc40ae84cf566ebf631b&dn=3Dbitco=
in-core-0.11.2&tr=3Dudp%3A%2F%
> 2Ftracker.openbittorrent.com%3A80%2Fannounce&tr=3Dudp%3A%2F%
> 2Ftracker.publicbt.com%3A80%2Fannounce&tr=3Dudp%3A%2F%2Ftracker.ccc.de
> %3A80%2Fannounce&tr=3Dudp%3A%2F%2Ftracker.coppersurfer.tk
> %3A6969&tr=3Dudp%3A%2F%2Fopen.demonii.com
> %3A1337&ws=3Dhttps%3A%2F%2Fbitcoin.org%2Fbin%2F
>
> This is a new minor version release, bringing bug fixes, the BIP65
> (CLTV) consensus change, and relay policy preparation for BIP113. It is
> recommended to upgrade to this version as soon as possible.
>
> Please report bugs using the issue tracker at github:
>
>   <https://github.com/bitcoin/bitcoin/issues>
>
> Upgrading and downgrading
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
>
> How to Upgrade
> - --------------
>
> If you are running an older version, shut it down. Wait until it has
> completely
> shut down (which might take a few minutes for older versions), then run t=
he
> installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac=
)
> or
> bitcoind/bitcoin-qt (on Linux).
>
> Downgrade warning
> - ------------------
>
> Because release 0.10.0 and later makes use of headers-first
> synchronization and
> parallel block download (see further), the block files and databases are
> not
> backwards-compatible with pre-0.10 versions of Bitcoin Core or other
> software:
>
> * Blocks will be stored on disk out of order (in the order they are
> received, really), which makes it incompatible with some tools or
> other programs. Reindexing using earlier versions will also not work
> anymore as a result of this.
>
> * The block index database will now hold headers for which no block is
> stored on disk, which earlier versions won't support.
>
> If you want to be able to downgrade smoothly, make a backup of your entir=
e
> data
> directory. Without this your node will need start syncing (or importing
> from
> bootstrap.dat) anew afterwards. It is possible that the data from a
> completely
> synchronised 0.10 node may be usable in older versions as-is, but this is
> not
> supported and may break as soon as the older version attempts to reindex.
>
> This does not affect wallet forward or backward compatibility. There are =
no
> known problems when downgrading from 0.11.x to 0.10.x.
>
> Notable changes since 0.11.1
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
>
> BIP65 soft fork to enforce OP_CHECKLOCKTIMEVERIFY opcode
> - --------------------------------------------------------
>
> This release includes several changes related to the [BIP65][] soft fork
> which redefines the existing OP_NOP2 opcode as OP_CHECKLOCKTIMEVERIFY
> (CLTV) so that a transaction output can be made unspendable until a
> specified point in the future.
>
> 1. This release will only relay and mine transactions spending a CLTV
>    output if they comply with the BIP65 rules as provided in code.
>
> 2. This release will produce version 4 blocks by default. Please see the
>    *notice to miners* below.
>
> 3. Once 951 out of a sequence of 1,001 blocks on the local node's best
> block
>    chain contain version 4 (or higher) blocks, this release will no
>    longer accept new version 3 blocks and it will only accept version 4
>    blocks if they comply with the BIP65 rules for CLTV.
>
> For more information about the soft-forking change, please see
> <https://github.com/bitcoin/bitcoin/pull/6351>
>
> Graphs showing the progress towards block version 4 adoption may be
> found at the URLs below:
>
> - - Block versions over the last 50,000 blocks as progress towards BIP65
>   consensus enforcement: <http://bitcoin.sipa.be/ver-50k.png>
>
> - - Block versions over the last 2,000 blocks showing the days to the
>   earliest possible BIP65 consensus-enforced block: <
> http://bitcoin.sipa.be/ver-2k.png>
>
> **Notice to miners:** Bitcoin Core=E2=80=99s block templates are now for
> version 4 blocks only, and any mining software relying on its
> getblocktemplate must be updated in parallel to use libblkmaker either
> version 0.4.3 or any version from 0.5.2 onward.
>
> - - If you are solo mining, this will affect you the moment you upgrade
>   Bitcoin Core, which must be done prior to BIP65 achieving its 951/1001
>   status.
>
> - - If you are mining with the stratum mining protocol: this does not
>   affect you.
>
> - - If you are mining with the getblocktemplate protocol to a pool: this
>   will affect you at the pool operator=E2=80=99s discretion, which must b=
e no
>   later than BIP65 achieving its 951/1001 status.
>
> [BIP65]: https://github.com/bitcoin/bips/blob/master/bip-0065.mediawiki
>
> BIP113 mempool-only locktime enforcement using GetMedianTimePast()
> - ----------------------------------------------------------------
>
> Bitcoin transactions currently may specify a locktime indicating when
> they may be added to a valid block.  Current consensus rules require
> that blocks have a block header time greater than the locktime specified
> in any transaction in that block.
>
> Miners get to choose what time they use for their header time, with the
> consensus rule being that no node will accept a block whose time is more
> than two hours in the future.  This creates a incentive for miners to
> set their header times to future values in order to include locktimed
> transactions which weren't supposed to be included for up to two more
> hours.
>
> The consensus rules also specify that valid blocks may have a header
> time greater than that of the median of the 11 previous blocks.  This
> GetMedianTimePast() time has a key feature we generally associate with
> time: it can't go backwards.
>
> [BIP113][] specifies a soft fork (**not enforced in this release**) that
> weakens this perverse incentive for individual miners to use a future
> time by requiring that valid blocks have a computed GetMedianTimePast()
> greater than the locktime specified in any transaction in that block.
>
> Mempool inclusion rules currently require transactions to be valid for
> immediate inclusion in a block in order to be accepted into the mempool.
> This release begins applying the BIP113 rule to received transactions,
> so transaction whose time is greater than the GetMedianTimePast() will
> no longer be accepted into the mempool.
>
> **Implication for miners:** you will begin rejecting transactions that
> would not be valid under BIP113, which will prevent you from producing
> invalid blocks if/when BIP113 is enforced on the network. Any
> transactions which are valid under the current rules but not yet valid
> under the BIP113 rules will either be mined by other miners or delayed
> until they are valid under BIP113. Note, however, that time-based
> locktime transactions are more or less unseen on the network currently.
>
> **Implication for users:** GetMedianTimePast() always trails behind the
> current time, so a transaction locktime set to the present time will be
> rejected by nodes running this release until the median time moves
> forward. To compensate, subtract one hour (3,600 seconds) from your
> locktimes to allow those transactions to be included in mempools at
> approximately the expected time.
>
> [BIP113]: https://github.com/bitcoin/bips/blob/master/bip-0113.mediawiki
>
> Windows bug fix for corrupted UTXO database on unclean shutdowns
> - ----------------------------------------------------------------
>
> Several Windows users reported that they often need to reindex the
> entire blockchain after an unclean shutdown of Bitcoin Core on Windows
> (or an unclean shutdown of Windows itself). Although unclean shutdowns
> remain unsafe, this release no longer relies on memory-mapped files for
> the UTXO database, which significantly reduced the frequency of unclean
> shutdowns leading to required reindexes during testing.
>
> For more information, see: <https://github.com/bitcoin/bitcoin/pull/6917>
>
> Other fixes for database corruption on Windows are expected in the
> next major release.
>
> 0.11.2 Change log
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> Detailed release notes follow. This overview includes changes that affect
> behavior, not code moves, refactors and string updates. For convenience i=
n
> locating
> the code changes and accompanying discussion, both the pull request and
> git merge commit are mentioned.
>
> - - #6124 `684636b` Make CScriptNum() take nMaxNumSize as an argument
> - - #6124 `4fa7a04` Replace NOP2 with CHECKLOCKTIMEVERIFY (BIP65)
> - - #6124 `6ea5ca4` Enable CHECKLOCKTIMEVERIFY as a standard script verif=
y
> flag
> - - #6351 `5e82e1c` Add CHECKLOCKTIMEVERIFY (BIP65) soft-fork logic
> - - #6353 `ba1da90` Show softfork status in getblockchaininfo
> - - #6351 `6af25b0` Add BIP65 to getblockchaininfo softforks list
> - - #6688 `01878c9` Fix locking in GetTransaction
> - - #6653 `b3eaa30` [Qt] Raise debug window when requested
> - - #6600 `1e672ae` Debian/Ubuntu: Include bitcoin-tx binary
> - - #6600 `2394f4d` Debian/Ubuntu: Split bitcoin-tx into its own package
> - - #5987 `33d6825` Bugfix: Allow mining on top of old tip blocks for
> testnet
> - - #6852 `21e58b8` build: make sure OpenSSL heeds noexecstack
> - - #6846 `af6edac` alias `-h` for `--help`
> - - #6867 `95a5039` Set TCP_NODELAY on P2P sockets.
> - - #6856 `dfe55bd` Do not allow blockfile pruning during reindex.
> - - #6566 `a1d3c6f` Add rules--presently disabled--for using
> GetMedianTimePast as end point for lock-time calculations
> - - #6566 `f720c5f` Enable policy enforcing GetMedianTimePast as the end
> point of lock-time constraints
> - - #6917 `0af5b8e` leveldb: Win32WritableFile without memory mapping
> - - #6948 `4e895b0` Always flush block and undo when switching to new fil=
e
>
> Credits
> =3D=3D=3D=3D=3D=3D=3D
>
> Thanks to everyone who directly contributed to this release:
>
> - - Alex Morcos
> - - =E0=B8=BFtcDrak
> - - Chris Kleeschulte
> - - Daniel Cousens
> - - Diego Viola
> - - Eric Lombrozo
> - - Esteban Ordano
> - - Gregory Maxwell
> - - Luke Dashjr
> - - Marco Falke
> - - Mark Friedenbach
> - - Matt Corallo
> - - Micha
> - - Mitchell Cash
> - - Peter Todd
> - - Pieter Wuille
> - - Wladimir J. van der Laan
> - - Zak Wilcox
>
> And those who contributed additional code review and/or security research=
.
>
> As well as everyone that helped translating on [Transifex](
> https://www.transifex.com/projects/p/bitcoin/).
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQEcBAEBCgAGBQJWReHOAAoJEHSBCwEjRsmmTAAH/iZQGklLHLIM6a2tTOj4d/O6
> xHg5bJhXGjtzO284Uy3phTzvk+e4mqBTjI8BrSr4D+Vw7mJrfWihdTLlgZYCwso3
> AyAk8ud1H42QanAfUvciY5uXd7cyzr8tCnCIBkvwJT5O8tI3FFhSMM5Fs86WnsP1
> Y10+93sxaVJUave2xm1bmgiwApFZKQ2MNU1IVgFaW8agB59fuqtPRnBdKiK/j+AO
> Jn1LKsObsINYhjtkAFiC66mUOBZ2N3rdhbN3LFl+u7EriTLoYk1OtZZhlC+rOueo
> nxl1H5SHStjrD27vE9Hv2qD5Ckrwo3zib8hZNIVs6MJjFnWUCwNtNg0nqDEvpn4=3D
> =3DxXdY
> -----END PGP SIGNATURE-----
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>



--=20
I like to provide some work at no charge to prove my value. Do you need a
techie?
I own Litmocracy <http://www.litmocracy.com> and Meme Racing
<http://www.memeracing.net> (in alpha).
I'm the webmaster for The Voluntaryist <http://www.voluntaryist.com> which
now accepts Bitcoin.
I also code for The Dollar Vigilante <http://dollarvigilante.com/>.
"He ought to find it more profitable to play by the rules" - Satoshi
Nakamoto

--001a113d41ae21666f052476aec4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>I decided to try to certify Wladimir&#39;s PGP k=
eys (the old one (2346C9A6) first, and then the new one (36C2E964), since i=
t was signed with the old one).<br><br></div>I
 visited=20
<a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-Jun=
e/009045.html">https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015=
-June/009045.html</a> to see that the new key was referenced in a message s=
igned by the old one.=C2=A0 I figure it&#39;s safe to assume that if the ol=
d key actually signed that message, then the core dev using &lt;<a href=3D"=
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev">laanwj at g=
mail.com</a>&gt; is an actual core dev (that&#39;s all I&#39;d be worried a=
bout).=C2=A0 So I copied the text from ------BEGIN PGP SIGNED MESSAGE----- =
to
-----END PGP SIGNATURE----- to my clipboard and asked Kleopatra (on=20
Windows) to verify it.=C2=A0 It says the signature is bad.=C2=A0 If I alter=
 the text of the email (so the signature would be have to be different to b=
e valid), it says exactly the same thing.=C2=A0 So maybe something is wrong=
 with Kleopatra on Windows.<br><br>However, the=20
SHA256SUMS.asc file I got from the magnet link posted in the email
(below)=C2=A0 verifies just fine using the new key (36C2E964).=C2=A0 So I f=
igure Kleopatra is not broken.=C2=A0 It recognizes that the old key was use=
d to create the signature in that old email, but it says it&#39;s invalid.=
=C2=A0 Has Wladimir been secretly replaced by someone who doesn&#39;t have =
access to the private key for 2346C9A6?=C2=A0 Can you make a (bad) signatur=
e look like it was made using a key you don&#39;t have? The whole reason fo=
r signing is so that we will know if something like that happened.=C2=A0 So=
 did I do something wrong?=C2=A0 (I mean, besides using Windows).<br><br></=
div><div>I believe this is the expected result if someone took something Wl=
adimir signed and ripped off the signature and pasted it below this new mes=
sage to make everyone think the new message was genuine.=C2=A0 Maybe Wladim=
ir made an edit after the signature was attached.=C2=A0 Or maybe it got cha=
nged when it went through the email system.=C2=A0 It would be nice to know.=
=C2=A0 Anyway, I fell back on Windows security and ran the install because =
it said it verified that the publisher was &quot;The Bitcoin Foundation&quo=
t;.<br></div><div><br></div></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Fri, Nov 13, 2015 at 5:13 AM, Wladimir J. van der Laan =
via bitcoin-dev <span dir=3D"ltr">&lt;<a href=3D"mailto:bitcoin-dev@lists.l=
inuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-----BEGIN PGP SIG=
NED MESSAGE-----<br>
Hash: SHA512<br>
<br>
Bitcoin Core version 0.11.2 is now available from:<br>
<br>
=C2=A0 &lt;<a href=3D"https://bitcoin.org/bin/bitcoin-core-0.11.2/" rel=3D"=
noreferrer" target=3D"_blank">https://bitcoin.org/bin/bitcoin-core-0.11.2/<=
/a>&gt;<br>
<br>
Alternatively, through bittorrent:<br>
<br>
=C2=A0 =C2=A0 magnet:?xt=3Durn:btih:d6d3387160f7e14f6f27dc40ae84cf566ebf631=
b&amp;dn=3Dbitcoin-core-0.11.2&amp;tr=3Dudp%3A%2F%<a href=3D"http://2Ftrack=
er.openbittorrent.com" rel=3D"noreferrer" target=3D"_blank">2Ftracker.openb=
ittorrent.com</a>%3A80%2Fannounce&amp;tr=3Dudp%3A%2F%<a href=3D"http://2Ftr=
acker.publicbt.com" rel=3D"noreferrer" target=3D"_blank">2Ftracker.publicbt=
.com</a>%3A80%2Fannounce&amp;tr=3Dudp%3A%2F%<a href=3D"http://2Ftracker.ccc=
.de" rel=3D"noreferrer" target=3D"_blank">2Ftracker.ccc.de</a>%3A80%2Fannou=
nce&amp;tr=3Dudp%3A%2F%<a href=3D"http://2Ftracker.coppersurfer.tk" rel=3D"=
noreferrer" target=3D"_blank">2Ftracker.coppersurfer.tk</a>%3A6969&amp;tr=
=3Dudp%3A%2F%<a href=3D"http://2Fopen.demonii.com" rel=3D"noreferrer" targe=
t=3D"_blank">2Fopen.demonii.com</a>%3A1337&amp;ws=3Dhttps%3A%2F%2Fbitcoin.o=
rg%2Fbin%2F<br>
<br>
This is a new minor version release, bringing bug fixes, the BIP65<br>
(CLTV) consensus change, and relay policy preparation for BIP113. It is<br>
recommended to upgrade to this version as soon as possible.<br>
<br>
Please report bugs using the issue tracker at github:<br>
<br>
=C2=A0 &lt;<a href=3D"https://github.com/bitcoin/bitcoin/issues" rel=3D"nor=
eferrer" target=3D"_blank">https://github.com/bitcoin/bitcoin/issues</a>&gt=
;<br>
<br>
Upgrading and downgrading<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
<br>
<br>
How to Upgrade<br>
- --------------<br>
<br>
If you are running an older version, shut it down. Wait until it has comple=
tely<br>
shut down (which might take a few minutes for older versions), then run the=
<br>
installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) =
or<br>
bitcoind/bitcoin-qt (on Linux).<br>
<br>
Downgrade warning<br>
- ------------------<br>
<br>
Because release 0.10.0 and later makes use of headers-first synchronization=
 and<br>
parallel block download (see further), the block files and databases are no=
t<br>
backwards-compatible with pre-0.10 versions of Bitcoin Core or other softwa=
re:<br>
<br>
* Blocks will be stored on disk out of order (in the order they are<br>
received, really), which makes it incompatible with some tools or<br>
other programs. Reindexing using earlier versions will also not work<br>
anymore as a result of this.<br>
<br>
* The block index database will now hold headers for which no block is<br>
stored on disk, which earlier versions won&#39;t support.<br>
<br>
If you want to be able to downgrade smoothly, make a backup of your entire =
data<br>
directory. Without this your node will need start syncing (or importing fro=
m<br>
bootstrap.dat) anew afterwards. It is possible that the data from a complet=
ely<br>
synchronised 0.10 node may be usable in older versions as-is, but this is n=
ot<br>
supported and may break as soon as the older version attempts to reindex.<b=
r>
<br>
This does not affect wallet forward or backward compatibility. There are no=
<br>
known problems when downgrading from 0.11.x to 0.10.x.<br>
<br>
Notable changes since 0.11.1<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<br>
<br>
BIP65 soft fork to enforce OP_CHECKLOCKTIMEVERIFY opcode<br>
- --------------------------------------------------------<br>
<br>
This release includes several changes related to the [BIP65][] soft fork<br=
>
which redefines the existing OP_NOP2 opcode as OP_CHECKLOCKTIMEVERIFY<br>
(CLTV) so that a transaction output can be made unspendable until a<br>
specified point in the future.<br>
<br>
1. This release will only relay and mine transactions spending a CLTV<br>
=C2=A0 =C2=A0output if they comply with the BIP65 rules as provided in code=
.<br>
<br>
2. This release will produce version 4 blocks by default. Please see the<br=
>
=C2=A0 =C2=A0*notice to miners* below.<br>
<br>
3. Once 951 out of a sequence of 1,001 blocks on the local node&#39;s best =
block<br>
=C2=A0 =C2=A0chain contain version 4 (or higher) blocks, this release will =
no<br>
=C2=A0 =C2=A0longer accept new version 3 blocks and it will only accept ver=
sion 4<br>
=C2=A0 =C2=A0blocks if they comply with the BIP65 rules for CLTV.<br>
<br>
For more information about the soft-forking change, please see<br>
&lt;<a href=3D"https://github.com/bitcoin/bitcoin/pull/6351" rel=3D"norefer=
rer" target=3D"_blank">https://github.com/bitcoin/bitcoin/pull/6351</a>&gt;=
<br>
<br>
Graphs showing the progress towards block version 4 adoption may be<br>
found at the URLs below:<br>
<br>
- - Block versions over the last 50,000 blocks as progress towards BIP65<br=
>
=C2=A0 consensus enforcement: &lt;<a href=3D"http://bitcoin.sipa.be/ver-50k=
.png" rel=3D"noreferrer" target=3D"_blank">http://bitcoin.sipa.be/ver-50k.p=
ng</a>&gt;<br>
<br>
- - Block versions over the last 2,000 blocks showing the days to the<br>
=C2=A0 earliest possible BIP65 consensus-enforced block: &lt;<a href=3D"htt=
p://bitcoin.sipa.be/ver-2k.png" rel=3D"noreferrer" target=3D"_blank">http:/=
/bitcoin.sipa.be/ver-2k.png</a>&gt;<br>
<br>
**Notice to miners:** Bitcoin Core=E2=80=99s block templates are now for<br=
>
version 4 blocks only, and any mining software relying on its<br>
getblocktemplate must be updated in parallel to use libblkmaker either<br>
version 0.4.3 or any version from 0.5.2 onward.<br>
<br>
- - If you are solo mining, this will affect you the moment you upgrade<br>
=C2=A0 Bitcoin Core, which must be done prior to BIP65 achieving its 951/10=
01<br>
=C2=A0 status.<br>
<br>
- - If you are mining with the stratum mining protocol: this does not<br>
=C2=A0 affect you.<br>
<br>
- - If you are mining with the getblocktemplate protocol to a pool: this<br=
>
=C2=A0 will affect you at the pool operator=E2=80=99s discretion, which mus=
t be no<br>
=C2=A0 later than BIP65 achieving its 951/1001 status.<br>
<br>
[BIP65]: <a href=3D"https://github.com/bitcoin/bips/blob/master/bip-0065.me=
diawiki" rel=3D"noreferrer" target=3D"_blank">https://github.com/bitcoin/bi=
ps/blob/master/bip-0065.mediawiki</a><br>
<br>
BIP113 mempool-only locktime enforcement using GetMedianTimePast()<br>
- ----------------------------------------------------------------<br>
<br>
Bitcoin transactions currently may specify a locktime indicating when<br>
they may be added to a valid block.=C2=A0 Current consensus rules require<b=
r>
that blocks have a block header time greater than the locktime specified<br=
>
in any transaction in that block.<br>
<br>
Miners get to choose what time they use for their header time, with the<br>
consensus rule being that no node will accept a block whose time is more<br=
>
than two hours in the future.=C2=A0 This creates a incentive for miners to<=
br>
set their header times to future values in order to include locktimed<br>
transactions which weren&#39;t supposed to be included for up to two more<b=
r>
hours.<br>
<br>
The consensus rules also specify that valid blocks may have a header<br>
time greater than that of the median of the 11 previous blocks.=C2=A0 This<=
br>
GetMedianTimePast() time has a key feature we generally associate with<br>
time: it can&#39;t go backwards.<br>
<br>
[BIP113][] specifies a soft fork (**not enforced in this release**) that<br=
>
weakens this perverse incentive for individual miners to use a future<br>
time by requiring that valid blocks have a computed GetMedianTimePast()<br>
greater than the locktime specified in any transaction in that block.<br>
<br>
Mempool inclusion rules currently require transactions to be valid for<br>
immediate inclusion in a block in order to be accepted into the mempool.<br=
>
This release begins applying the BIP113 rule to received transactions,<br>
so transaction whose time is greater than the GetMedianTimePast() will<br>
no longer be accepted into the mempool.<br>
<br>
**Implication for miners:** you will begin rejecting transactions that<br>
would not be valid under BIP113, which will prevent you from producing<br>
invalid blocks if/when BIP113 is enforced on the network. Any<br>
transactions which are valid under the current rules but not yet valid<br>
under the BIP113 rules will either be mined by other miners or delayed<br>
until they are valid under BIP113. Note, however, that time-based<br>
locktime transactions are more or less unseen on the network currently.<br>
<br>
**Implication for users:** GetMedianTimePast() always trails behind the<br>
current time, so a transaction locktime set to the present time will be<br>
rejected by nodes running this release until the median time moves<br>
forward. To compensate, subtract one hour (3,600 seconds) from your<br>
locktimes to allow those transactions to be included in mempools at<br>
approximately the expected time.<br>
<br>
[BIP113]: <a href=3D"https://github.com/bitcoin/bips/blob/master/bip-0113.m=
ediawiki" rel=3D"noreferrer" target=3D"_blank">https://github.com/bitcoin/b=
ips/blob/master/bip-0113.mediawiki</a><br>
<br>
Windows bug fix for corrupted UTXO database on unclean shutdowns<br>
- ----------------------------------------------------------------<br>
<br>
Several Windows users reported that they often need to reindex the<br>
entire blockchain after an unclean shutdown of Bitcoin Core on Windows<br>
(or an unclean shutdown of Windows itself). Although unclean shutdowns<br>
remain unsafe, this release no longer relies on memory-mapped files for<br>
the UTXO database, which significantly reduced the frequency of unclean<br>
shutdowns leading to required reindexes during testing.<br>
<br>
For more information, see: &lt;<a href=3D"https://github.com/bitcoin/bitcoi=
n/pull/6917" rel=3D"noreferrer" target=3D"_blank">https://github.com/bitcoi=
n/bitcoin/pull/6917</a>&gt;<br>
<br>
Other fixes for database corruption on Windows are expected in the<br>
next major release.<br>
<br>
0.11.2 Change log<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
Detailed release notes follow. This overview includes changes that affect<b=
r>
behavior, not code moves, refactors and string updates. For convenience in =
locating<br>
the code changes and accompanying discussion, both the pull request and<br>
git merge commit are mentioned.<br>
<br>
- - #6124 `684636b` Make CScriptNum() take nMaxNumSize as an argument<br>
- - #6124 `4fa7a04` Replace NOP2 with CHECKLOCKTIMEVERIFY (BIP65)<br>
- - #6124 `6ea5ca4` Enable CHECKLOCKTIMEVERIFY as a standard script verify =
flag<br>
- - #6351 `5e82e1c` Add CHECKLOCKTIMEVERIFY (BIP65) soft-fork logic<br>
- - #6353 `ba1da90` Show softfork status in getblockchaininfo<br>
- - #6351 `6af25b0` Add BIP65 to getblockchaininfo softforks list<br>
- - #6688 `01878c9` Fix locking in GetTransaction<br>
- - #6653 `b3eaa30` [Qt] Raise debug window when requested<br>
- - #6600 `1e672ae` Debian/Ubuntu: Include bitcoin-tx binary<br>
- - #6600 `2394f4d` Debian/Ubuntu: Split bitcoin-tx into its own package<br=
>
- - #5987 `33d6825` Bugfix: Allow mining on top of old tip blocks for testn=
et<br>
- - #6852 `21e58b8` build: make sure OpenSSL heeds noexecstack<br>
- - #6846 `af6edac` alias `-h` for `--help`<br>
- - #6867 `95a5039` Set TCP_NODELAY on P2P sockets.<br>
- - #6856 `dfe55bd` Do not allow blockfile pruning during reindex.<br>
- - #6566 `a1d3c6f` Add rules--presently disabled--for using GetMedianTimeP=
ast as end point for lock-time calculations<br>
- - #6566 `f720c5f` Enable policy enforcing GetMedianTimePast as the end po=
int of lock-time constraints<br>
- - #6917 `0af5b8e` leveldb: Win32WritableFile without memory mapping<br>
- - #6948 `4e895b0` Always flush block and undo when switching to new file<=
br>
<br>
Credits<br>
=3D=3D=3D=3D=3D=3D=3D<br>
<br>
Thanks to everyone who directly contributed to this release:<br>
<br>
- - Alex Morcos<br>
- - =E0=B8=BFtcDrak<br>
- - Chris Kleeschulte<br>
- - Daniel Cousens<br>
- - Diego Viola<br>
- - Eric Lombrozo<br>
- - Esteban Ordano<br>
- - Gregory Maxwell<br>
- - Luke Dashjr<br>
- - Marco Falke<br>
- - Mark Friedenbach<br>
- - Matt Corallo<br>
- - Micha<br>
- - Mitchell Cash<br>
- - Peter Todd<br>
- - Pieter Wuille<br>
- - Wladimir J. van der Laan<br>
- - Zak Wilcox<br>
<br>
And those who contributed additional code review and/or security research.<=
br>
<br>
As well as everyone that helped translating on [Transifex](<a href=3D"https=
://www.transifex.com/projects/p/bitcoin/" rel=3D"noreferrer" target=3D"_bla=
nk">https://www.transifex.com/projects/p/bitcoin/</a>).<br>
<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1<br>
<br>
iQEcBAEBCgAGBQJWReHOAAoJEHSBCwEjRsmmTAAH/iZQGklLHLIM6a2tTOj4d/O6<br>
xHg5bJhXGjtzO284Uy3phTzvk+e4mqBTjI8BrSr4D+Vw7mJrfWihdTLlgZYCwso3<br>
AyAk8ud1H42QanAfUvciY5uXd7cyzr8tCnCIBkvwJT5O8tI3FFhSMM5Fs86WnsP1<br>
Y10+93sxaVJUave2xm1bmgiwApFZKQ2MNU1IVgFaW8agB59fuqtPRnBdKiK/j+AO<br>
Jn1LKsObsINYhjtkAFiC66mUOBZ2N3rdhbN3LFl+u7EriTLoYk1OtZZhlC+rOueo<br>
nxl1H5SHStjrD27vE9Hv2qD5Ckrwo3zib8hZNIVs6MJjFnWUCwNtNg0nqDEvpn4=3D<br>
=3DxXdY<br>
-----END PGP SIGNATURE-----<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div><br><br clear=3D"all"><br>-- <br><div class=3D"gmail_sig=
nature"><div dir=3D"ltr">I like to provide some work at no charge to prove =
my value. Do you need a techie?=C2=A0 <br>I own <a href=3D"http://www.litmo=
cracy.com" target=3D"_blank">Litmocracy</a> and <a href=3D"http://www.memer=
acing.net" target=3D"_blank">Meme Racing</a> (in alpha). <br>I&#39;m the we=
bmaster for <a href=3D"http://www.voluntaryist.com" target=3D"_blank">The V=
oluntaryist</a> which now accepts Bitcoin.<br>I also code for <a href=3D"ht=
tp://dollarvigilante.com/" target=3D"_blank">The Dollar Vigilante</a>.<br>&=
quot;He ought to find it more profitable to play by the rules&quot; - Satos=
hi Nakamoto</div></div>
</div>

--001a113d41ae21666f052476aec4--