Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Bitcoin Core: 0.12.0 release notes #1239
Conversation
Michagogo
commented on the diff
Feb 18, 2016
| +Note that the wallet in Bitcoin Core 0.12 does not yet have support for | ||
| +creating transactions that would be replaceable under BIP 125. | ||
| + | ||
| + | ||
| +RPC: Random-cookie RPC authentication | ||
| +------------------------------------- | ||
| + | ||
| +When no `-rpcpassword` is specified, the daemon now uses a special 'cookie' | ||
| +file for authentication. This file is generated with random content when the | ||
| +daemon starts, and deleted when it exits. Its contents are used as | ||
| +authentication token. Read access to this file controls who can access through | ||
| +RPC. By default it is stored in the data directory but its location can be | ||
| +overridden with the option `-rpccookiefile`. | ||
| + | ||
| +This is similar to Tor's CookieAuthentication: see | ||
| +https://www.torproject.org/docs/tor-manual.html.en |
|
|
laanwj
added
Releases
Core
labels
Feb 19, 2016
|
utACK, also added the tags |
|
Keeping an eye on this. Will merge when it looks like everything is ready (assuming someone doesn't beat me to it). |
Michagogo
commented
Feb 20, 2016
|
Should happen Monday or Tuesday, once @theuni is back from Hong Kong. On Saturday, February 20, 2016, Cøbra notifications@github.com wrote:
|
|
Thanks David! I filled in the magnet link and uncommented the release date and pushed to: |
Michagogo
commented
Feb 23, 2016
|
It won't. The PR is on @harding's fork. On Tuesday, February 23, 2016, Wladimir J. van der Laan <
|
|
@Michagogo not here, but it does in https://travis-ci.org/bitcoin-dot-org/bitcoin.org/builds/111182266 |
|
Not sure what's wrong:
|
Michagogo
commented
Feb 23, 2016
|
Oh. Right. However it seems to be failing… On Tuesday, February 23, 2016, Wladimir J. van der Laan <
|
|
@Michagogo Right, I re-triggered it here to to see if this one passes thus whether the travis failure is my mistake. |
btcdrak
commented on the diff
Feb 23, 2016
| +Because release 0.12.0 and later will obfuscate the chainstate on every | ||
| +fresh sync or reindex, the chainstate is not backwards-compatible with | ||
| +pre-0.12 versions of Bitcoin Core or other software. | ||
| + | ||
| +If you want to downgrade after you have done a reindex with 0.12.0 or later, | ||
| +you will need to reindex when you first start Bitcoin Core version 0.11 or | ||
| +earlier. | ||
| + | ||
| +Notable changes | ||
| +=============== | ||
| + | ||
| +Signature validation using libsecp256k1 | ||
| +--------------------------------------- | ||
| + | ||
| +ECDSA signatures inside Bitcoin transactions now use validation using | ||
| +[https://github.com/bitcoin/secp256k1](libsecp256k1) instead of OpenSSL. |
btcdrak
Contributor
|
|
Pushed a new commit, hopefully it fixes those. |
|
Ignore the "internal image /img/screenshots/armory.png does not exist (line 405)" error. That's fixed in e96bed7 so shouldn't be an issue. |
|
This needs to get merged asap, announces are all out already. |
|
Still waiting for travis on https://travis-ci.org/bitcoin-dot-org/bitcoin.org/builds/111185186 |
harding commentedFeb 18, 2016
Preview: http://dg1.dtrt.org/en/download
TODO:
optional_datefield in the YAML headerNote that this patch also drops the Jan2016 project statement and capacity-increases-related links from the Bitcoin.org/bitcoin-core main page as they were statically sorted, so so would've appeared higher in the listing than the 0.12.0 release announcement. The new website link is left in and placed above the 0.12.0 announcement so that people still go to the new website. Preview:
I've dropped my commit access on Bitcoin.org for busy-ness reasons, so someone else will have to merge this when appropriate. Also, if someone could tag this now as Releases and Bitcoin Core, that would be useful.