Remove blog items

This commit is contained in:
thephez 2018-01-04 14:13:27 -05:00
parent 05122eb7f2
commit 3cebbda5af
14 changed files with 0 additions and 2389 deletions

View file

@ -1,27 +0,0 @@
---
# This file is licensed under the MIT License (MIT) available on
# http://opensource.org/licenses/MIT.
layout: base
lang: en
---
<link rel="alternate" type="application/atom+xml" href="/en/rss/blog.xml" title="Bitcoin.org Site Blog">
<div class="subhead-links"><a href="/en/blog">Blog home</a>
| <a type="application/atom+xml" href="/en/rss/blog.xml"><img src="/img/icons/header_rss.svg" alt="rss" class="rssicon"> Subscribe to RSS feed</a>
| <a href="https://github.com/thephez/dash.org/commits/master/{{page.path|uri_escape}}">Post history</a>
| <a href="https://github.com/thephez/dash.org/issues/new?body=Source%20File%3A%20{{page.path|uri_escape}}%0A%0A">Report issue</a></div>
<div class="post">
<header class="post-header">
<h1 class="post-title">{{ page.title }}</h1>
</header>
<article class="post-content">
{{ content }}
</article>
<p class="post-meta">Posted to the <a href="/en/blog">Bitcoin.org Site
Blog</a> on {{ page.date | date: "%d %B %Y" }} {% if page.author %} by {{ page.author }}{% endif %}{% if page.meta %} {{ page.meta }}{% endif %}</p>
</div>

View file

@ -1,464 +0,0 @@
---
# This file is licensed under the MIT License (MIT) available on
# http://opensource.org/licenses/MIT.
type: posts
layout: post
category: blog
title: "Quarterly Report March 2015"
permalink: /en/posts/quarterly-report-march-2015.html
date: 2015-03-05
author: >
David A. Harding (<a href="mailto:dave@dtrt.org">email</a>, <a
href="https://github.com/harding">GitHub</a>,
<a href="http://www.reddit.com/user/harda/">Reddit</a>)
---
*Thanks to [our
volunteers](https://github.com/bitcoin-dot-org/bitcoin.org/graphs/contributors?from=2014-12-01&to=2015-02-28&type=c)
and the financial sponsorship of [The Bitcoin
Foundation](https://bitcoinfoundation.org/), we've made the
following accomplishments this quarter.*
Summary for December 2014, January 2015, and February 2015.
* **Quarterly page views:** [over 7 million.](https://bitcoin.org/stats/)
* **Translations:** Bitcoin.org now has fully proofread and complete
translations for 26 languages. New and significantly-improved
translations added this quarter include Bulgarian, Greek, Polish,
and Turkish.
* **Developer documentation:** added 114 new or completely rewritten
printed pages worth of text describing Bitcoin Core's RPC interface
and 8 more pages describing its new HTTP REST interface. Bitcoin Core
0.10.0's new headers-first sync is now documented as is the older
blocks-first sync. Begun in the previous quarter, this quarter also
saw the completion of over 30 printed pages worth of text describing
the Bitcoin peer-to-peer network.
* **Contributors:** long-time site maintainer Saïvann Carignan, who has
made [over 1,000
commits](https://github.com/bitcoin-dot-org/bitcoin.org/commits/master?author=saivann)
during the past two years, has announced he no longer has time to lead
the project. A search is on for new volunteers who are willing to
contribute to one of most trusted Bitcoin resources on the Internet.
* **Wallets:** reviewed and added three new wallets to the Choose Your
Wallet page, and all previously-listed wallets now support HTTP Strict
Transport Security (HSTS) for secure parts of their sites.
* **User guides:** A new guide has been published to the site providing
detailed instructions for supporting the network by running the
Bitcoin Core full node. The announcement of the page received over
[200 upvotes on
Reddit](http://www.reddit.com/r/Bitcoin/comments/2wvdko/new_page_on_bitcoinorg_running_a_full_node/).
## Translations
> "Muchas gracias por atender esto inmediatamente, ¡y por el trabajo
> realizado!" (Many thanks for doing this immediately, and for all the
> work done!) --Adamantike on Transifex.com
![Bitcoin.org available in 26 languages](/img/blog/free/translations.png)
Non-US/UK visitors accounted for 35% percent of Bitcoin.org's traffic
this quarter, about 2.5 million page views. Future translation work will
likely depend on how the English portion of the site is changed in the
coming months.
* **Newly proofread:** Bulgarian, Polish, and Turkish translations
* **FAQ translated:** the longest localized page on the site, the
[FAQ](http://btcorg.localhost/en/faq) has now been translated into
Polish and Turkish.
* **Newly added:** a Greek translation
* **Updated:** this quarter saw updates small and large for the
translations to Bulgarian, Chinese (Traditional), Chinese
(Simplified), Danish, Dutch, French, German, Greek, Hindi, Hungarian,
Indonesian, Italian, Japanese, Korean, Persian, Polish, Portuguese,
Romanian, Russian, Swedish, Turkish, and Ukrainian.
We are extremely grateful for all the translations contributed by
volunteers and paid translators on our [Transifex project
page](https://www.transifex.com/projects/p/bitcoinorg/) as well as the
many reviews made by Saïvann Carignan.
## Developer documentation
> "Nice work!" ---Jonas Schnelli about the new HTTP REST documentation
> ([source](https://github.com/bitcoin-dot-org/bitcoin.org/pull/720#issuecomment-71515413))
![Illustration from new headers-first documentation](/img/blog/free/en-headers-first-moving-window.png)
The three main developer documentation webpages received a total
of about 90,000 page views this quarter. Accomplishments this
quarter include:
* **RPC rewrite:** added [114 new or completely
rewritten](https://github.com/bitcoin-dot-org/bitcoin.org/pull/693) printed
pages worth of text describing Bitcoin Core's RPC interface and [8
more pages](https://github.com/bitcoin-dot-org/bitcoin.org/pull/720)
describing its new HTTP REST interface.
* **What's headers first?** Bitcoin Core 0.10.0's new
headers-first sync [is now
documented](https://github.com/bitcoin-dot-org/bitcoin.org/pull/736) as is
[the older blocks-first
sync](https://github.com/bitcoin-dot-org/bitcoin.org/pull/685).
* **P2P protocol:** begun in the previous quarter, this quarter also saw
the [completion](https://github.com/bitcoin-dot-org/bitcoin.org/pull/657) of
over 30 printed pages worth of text [describing the Bitcoin
peer-to-peer network](https://bitcoin.org/en/developer-reference#p2p-network).
* **Ease contribution:** nearly every subheading [now
includes](https://github.com/bitcoin-dot-org/bitcoin.org/pull/682) links that
allow instant submission of corrections or reporting of issues related
to the text.
* **Documentation is not a specification:** relaying comments frequently
made by Bitcoin Core developers, we now make clear that the
[documentation is not a
specification](https://github.com/bitcoin-dot-org/bitcoin.org/pull/679)
* **Bitcoin Core 0.10.0:** many small changes were made to update the
documentation to accurately describe Bitcoin Core 0.10.0 behavior.
Most documentation was written by David A. Harding, with reviews
conducted by Saïvann Carignan, Jonas Schnelli, and others.
## Regular Updates
> "Great!"
> "Thanks."
> "Thank you!"
> ---Users after we helped promote their Bitcoin events (sources:
> [1](https://github.com/bitcoin-dot-org/bitcoin.org/issues/702),
> [2](https://github.com/bitcoin-dot-org/bitcoin.org/issues/741),
> [3](https://github.com/bitcoin-dot-org/bitcoin.org/issues/741))
![Excerpt from the Events page map](/img/blog/free/events.png)
The English [homepage](https://bitcoin.org/en/) and [Getting
Started](https://bitcoin.org/en/getting-started) page by themselves
received over 2.0 million visits this quarter. These and other regular
content pages are often updated based on suggestions by first-time
contributors, with the bulk of updates going to the [Events
page](https://bitcoin.org/en/events) and the [Resources
page](https://bitcoin.org/en/resources) (and its many translations).
* **Update events:** listed 20 new events in addition to the events
automatically listed by the site software.
* **Update links:** updated redirected or broken links, as well as removed
or redirected links that point to resources our contributors no longer
think are useful.
* **Localize links:** pointed links to relevant local resources for some
languages.
* **Add non-profit link directory:** added the excellent non-profit link
directory compiled by GiveBTC.org.
* **Mention innovative technology:** added the Lighthouse P2P crowdfunding
platform to the list of innovative Bitcoin technology.
We are grateful to all of the contributors who opened issues and made
pull requests to keep the site content current and useful.
## Wallets
> "Thank you! Good catch!" ---GreenAddress on GitHub after we discovered
> a bug in the new GreenBits wallet
> ([source](https://github.com/bitcoin-dot-org/bitcoin.org/pull/725#issuecomment-73322654))
![Just some of the wallets currently listed](/img/blog/free/wallets.png)
The [Choose Your Wallet page](https://bitcoin.org/en/choose-your-wallet)
is one of our most visited pages---just the English version of the page
alone has received over 400,000 visitors this quarter. However,
maintaining the page is also one of our most time-consuming activities due
to the number of wallet authors who want us to include their wallet on
the page.
* **New wallets:** we reviewed and added three new wallets
[Airbitz](https://github.com/bitcoin-dot-org/bitcoin.org/pull/652),
[Circle](https://github.com/bitcoin-dot-org/bitcoin.org/pull/697), and
[Coinapult](https://github.com/bitcoin-dot-org/bitcoin.org/pull/577).
* **Made HSTS a requirement:** after contacting eight wallet
providers and asking them to enable HTTP Strict Transport Security
(HSTS) on their sites, all eight eventually agreed to use this
simple server setting to help prevent possibly-devastating
man-in-the-middle attacks.
* **Removed Blockchain.info:** although a very popular wallet service,
Blockchain.info was
[delisted](https://github.com/bitcoin-dot-org/bitcoin.org/pull/663) after a
polite online discussion with its CEO. A period of 60 days was chosen,
after which they may apply to be relisted.
* **Published wallet requirements:** a set of wallet requirements and
guidelines [were
discussed](https://github.com/bitcoin-dot-org/bitcoin.org/pull/670) and
published, allowing wallet authors to evaluate for themselves whether
their wallet would be a good fit for Bitcoin.org.
Saïvann Carignan spearheaded all the wallet efforts above, although we
are also grateful to the many people who commented on the wallet issues
and pull requests.
As Saïvann has become too busy to continue maintenance of the wallet
section of the site, we are actively [looking for a
volunteer](https://github.com/bitcoin-dot-org/bitcoin.org/issues/778) to take
over reviewing wallets and managing wallet requirements. This is a great
volunteer position for anyone who likes trying new wallets and who wants
to interact directly with wallet authors.
## New Full Node Guide
> "Awesome, thanks for writing this down!" ---Andreas Schildbach on
> GitHub
> ([source](https://github.com/bitcoin-dot-org/bitcoin.org/pull/711#issuecomment-70187037))
![Screenshot included in the full node guide](/img/blog/free/bitcoin-core.png)
Fulfilling a [request made by Wladimir J. van der
Laan](http://www.mail-archive.com/bitcoin-development%40lists.sourceforge.net/msg05406.html),
Bitcoin Core's lead developer, we were proud to write and publish a
[guide to running a full node](https://bitcoin.org/en/full-node) this
quarter. The goal is to encourage users to run full nodes when possible
to support the Bitcoin network.
As of February 28th, the full node guide has been published for only
five days and has received over 4,000 page views.
* **Target multiple OSes:** initial instructions are provided for Ubuntu
Desktop and Ubuntu Server, other Linux distributions (desktop or
server), and Windows 7 (desktop only). New volunteers have [begun the
process](https://github.com/bitcoin-dot-org/bitcoin.org/issues/763) of
contributing Windows 8.1 instructions, and we are still looking for a
Mac user to contribute OS X instructions.
* **Describe opening port 8333:** thanks to the core developers, running
Bitcoin Core is easy. The hard part for some users is opening port
8333, so we [provide detailed
instructions](https://bitcoin.org/en/full-node#network-configuration)
for just that aspect.
* **Detail risks:** feedback from a core developer encouraged us to make
it clear that running a full node isn't always easy, so users who read
our guide won't become demoralized and give up on running a full node
forever the first time they encounter a problem.
* **Over 200 upvotes:** soon after release, the guide was submitted to
Reddit where it received [over 200
upvotes](http://www.reddit.com/r/Bitcoin/comments/2wvdko/new_page_on_bitcoinorg_running_a_full_node/)
and a rare "98% upvoted" quality score.
The guide was primarily written by David A. Harding, with reviews by
Saïvann Carignan and Jameson Lopp, and promotion also by Jameson.
## Website Improvements
> "Confirmed it works. Thanks a lot!" --Wladimir J. van der Laan on
> GitHub about the updated Download page
> ([source](https://github.com/bitcoin-dot-org/bitcoin.org/pull/664#issuecomment-74473907))
Sometimes small tweaks to the site can have a large impact. Some of the
changes made this quarter include:
![New torrent and magnet links](/img/blog/free/torrent.png)
* **Bitcoin Core 0.10.0:** it is our privilege to help the
core developers release new versions of Bitcoin Core by
[updating](https://github.com/bitcoin-dot-org/bitcoin.org/pull/664) the
[Download page](https://bitcoin.org/en/download) and the [hosted
release notes.](https://bitcoin.org/en/version-history) For the
0.10.0 release, we added a [torrent
file](https://bitcoin.org/bin/bitcoin-core-0.10.0/bitcoin-0.10.0.torrent)
and [magnet
link](magnet:?xt=urn:btih:170c61fe09dafecfbb97cb4dccd32173383f4e68&dn=0.10.0&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr=udp%3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr=udp%3A%2F%2Ftracker.ccc.de%3A80%2Fannounce&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr=udp%3A%2F%2Fopen.demonii.com%3A1337&ws=https%3A%2F%2Fbitcoin.org%2Fbin%2F)
to help ensure availability of the files even if Bitcoin.org
goes down.
The new torrent has been downloaded over 900 times and there are at
least 44 active seeders as of February 28th.
* **Image optimization:** 83 SVG images were
[optimized,](https://github.com/bitcoin-dot-org/bitcoin.org/pull/774) saving
over 250 KB of disk space and a significant amount of bandwidth, as
well as helping users on slow connections read the site more quickly.
* **Release ordering:** as the core developers plan to backport the
BIP66 changes to older versions of Bitcoin Core, we've made sure the
release notes on the site are ordered by version number rather than
date so that we always recommend the highest version of Bitcoin Core
to new users.
Saïvann Carignan wrote the code to enable the torrent and magnet links
as well as sorting releases by version number. J. Louis optimized the
SVG images.
## Server And Development Tools
> "I don't know what people are complaining about... I think it's pretty
> great actually!" ---/u/itsgremlin on Reddit about Bitcoin.org in
> general
> ([source](http://www.reddit.com/r/Bitcoin/comments/2oessw/bitcoinorg_what_would_you_want_here/cmmg9r7))
![Travis CI verifying the site builds correctly](/img/blog/free/travis.png)
With 7 million page views per quarter, Bitcoin.org serves an average of
54 pages a minute---so even a single second of downtime might prevent us
from helping a Bitcoin user. This quarter we took additional steps to
ensure that the site works correctly while also attempting to make it
easier for new volunteers to contribute to keeping the site accurate and
updated.
* **Continuous integration:** each new pull request improving the site
is now [automatically built using Travis
CI](https://github.com/bitcoin-dot-org/bitcoin.org/pull/771), allowing
contributors to quickly discover bugs in their code even if they don't
compile the site themselves.
* **Troubleshooting:**
[investigated](https://github.com/bitcoin-dot-org/bitcoin.org/issues/712) slow
bandwidth issues with downloads.
* **Preventive maintenance:** mitigated DDoS attacks and made sure stats
are not affected by attacks. Also set Content-Security-Policy policies
against XSS attacks.
* **Guide volunteers:** [added a
list](https://github.com/bitcoin-dot-org/bitcoin.org/pull/742) of [suggestions
for new
contributors](https://github.com/bitcoin-dot-org/bitcoin.org#how-to-participate)
so they can dive in immediately.
* **Audits:** wrote an automated script that will send an alert when
sensitive parts of the site are changed or when Bitcoin Core downloads
are missing correct signatures.
Travis CI support was added by David A. Harding with advice and support
from Cory Fields, Wladimir J. van der Laan, and Pieter Wuille.
Troubleshooting was performed by Saïvann Carignan with the help of
GitHub user @patrikr, Christopher Gurnee, and David. Preventative
maintenance and audit code were contributions by Saïvann, and the
volunteer quick start guide was contributed by David.
## Public Website Statistics
> "38,135,685 page views [since January 2014]" ---[The stats
> page](https://bitcoin.org/stats/)
![stats December 2014](/img/blog/free/stats-2014-12.png)
![stats January 2015(/img/blog/free/stats-2015-01.png)
![stats February 2015](/img/blog/free/stats-2015-02.png)
## Expense Report
> "This is awesome and sorely needed. [...] Appreciate everything you do
> for the community, keep up the great work!" ---/u/wserd on Reddit
> about the new Full Node page ([source](http://www.reddit.com/r/Bitcoin/comments/2wvdko/new_page_on_bitcoinorg_running_a_full_node/cough5b))
![Expense graph](/img/blog/free/expenses.png)
| Previous balance | 4.994 784 06 BTC
|--------------------------|-------------------
| Foundation's sponsorship | 20.779 976 01 BTC
| Website maintenance | -5.786 595 31 BTC
| Translations | -4.735 938 00 BTC
| Server hosting | -4.552 368 00 BTC
| Developer documentation | -2.614 684 15 BTC
| **New balance** | &nbsp;8.085 174 61 BTC
## Next Quarter's Goals
> "I'm running a full node (~20 connections) with Bitcoin Core Version
> v0.10.0rc1 (64-Bit) on Windows 8.1 and willing to help out!"\
> ---Volunteer on GitHub for the Full Node page
> ([source](https://github.com/bitcoin-dot-org/bitcoin.org/issues/763))
In addition to Bitcoin.org's recurring goals, such as funding the
servers (currently about $600 USD per month), we hope to accomplish the
following three major goals during the next quarter:
1. **New wallet maintainer:** we're [seeking a
volunteer](https://github.com/bitcoin-dot-org/bitcoin.org/issues/778) to
review new wallets for inclusion on the Choose Your Wallet page, as
well as to monitor existing wallets for problems and to propose new
criteria that allow us to only recommend the very best wallets.
2. **New developer documentation:** the developer documentation is
currently 250 printed pages long, and on May 24th it will celebrate
its [one-year
anniversary](https://github.com/bitcoin-dot-org/bitcoin.org/pull/393#issuecomment-44089996)
on Bitcoin.org. In the upcoming quarter we plan to add about 50 more
printed pages worth of content, including:
* A [glossary/vocabulary
page](https://groups.google.com/forum/#!topic/bitcoin-documentation/s_mL1syxYoQ)
providing definitions for the over 150 specialized terms and
synonyms used in Bitcoin development
* Documentation for at least the most common opcodes, and possibly
all the enabled opcodes. This section will be essentially a more
detailed version of the [Bitcoin Wiki script
page](https://en.bitcoin.it/wiki/Script)
* [Improved type
information](https://github.com/bitcoin-dot-org/bitcoin.org/pull/753) in
the RPC and REST sections, as
[requested](http://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg07069.html)
by Ocaml-Bitcoin developer Dario Teixeira.
* Substantially revising and expanding the [current wallet
section](https://bitcoin.org/en/developer-guide#wallets), likely
leading to a new section focused on ECDSA keys and signatures.
* Continuing to expand the [overview of the Bitcoin P2P
protocol](https://bitcoin.org/en/developer-guide#p2p-network).
3. **Better volunteer resources:** we want to make it easier for
community members to volunteer to contribute to Bitcoin.org in ways
both small and large. New documentation about site procedures is
forthcoming and we will be looking for other ways to encourage and
simplify first-time contributions.
## Thanks To Sponsors And Volunteers
> "Thank you for your sponsorship and your support of our work!"
> ---Saïvann Carignan
> "The Foundation provides us a modest monthly grant so we can pay for
> servers and some other stuff, and we put their logo on the bottom of
> the page and write a quarterly report telling them what we've
> accomplished thanks to their sponsorship. Beyond that, they let us
> make our own decisions, for which independence we're quite grateful."
> ---David A. Harding on Reddit
> ([source](http://www.reddit.com/r/Bitcoin/comments/2wvdko/new_page_on_bitcoinorg_running_a_full_node/couu1cv))
We thank [The Bitcoin Foundation](https://bitcoinfoundation.org/) for
their continued financial support of the site, and extend our heartfelt
appreciation to the [15
people](https://github.com/bitcoin-dot-org/bitcoin.org/graphs/contributors?from=2014-12-01&to=2015-02-28&type=c)
who contributed commits this quarter and the much larger number of
people who provided valuable feedback in over 439 comments on pull
requests and issues.
---
*If you have any questions about the content of this report, please
[open an issue](https://github.com/bitcoin-dot-org/bitcoin.org/issues/new) on
GitHub or email Dave Harding, <dave@dtrt.org>.*

View file

@ -1,110 +0,0 @@
---
# This file is licensed under the MIT License (MIT) available on
# http://opensource.org/licenses/MIT.
type: posts
layout: post
category: blog
title: "Site Updates In March 2015"
permalink: /en/posts/site-updates-april-2015.html
date: 2015-04-01
author: >
David A. Harding (<a href="mailto:dave@dtrt.org">email</a>, <a
href="https://github.com/harding">GitHub</a>,
<a href="http://www.reddit.com/user/harda/">Reddit</a>)
---
*Thanks to [our
volunteers](https://github.com/bitcoin-dot-org/bitcoin.org/graphs/contributors?from=2015-03-01&to=2015-03-31&type=c)
and the financial sponsorship of [The Bitcoin
Foundation](https://bitcoinfoundation.org/), we made the following
accomplishments this month.*
* **No more broken links:** all internal links on Bitcoin.org's 834 pages
are now automatically checked by [HTML Proofer][] through our [Travis
Continuous Integration (CI)][] infrastructure. We plan to enable HTML
Proofer's HTML validation subroutine in the future to provide even
better quality assurance. Thanks to HTML Proofer author [Garen
Torikian][] for writing such a great tool!
* **Coinapult wallet** was briefly removed from the Bitcoin.org [Choose Your
Wallet][] page after they suffered a security breach. After restoring
full services to their customers and assuring us that customer
deposits are safe, we re-added them.
* **KnC wallet** has been removed from the Choose Your Wallet page after
multiple issues, including an abandoned website, no new commits to
[their codebase][] in several months, and reports that their iOS app
no longer worked. (In positive news, we have received reports that it
is still possible to recover funds from the wallet seed.)
* **Translations** were updated thanks to translation volunteers on
[Transifex][].
* **Seven new events** were added. Please check the [Events page][] to see
whether there are any interesting Bitcoin meetups or conferences in
your area.
* **New pages & features:** a [developer documentation][] glossary
section and Javascript-based search engine were [proposed][] but not
quite finished by the end of the month.
## Site Traffic
According to or [website statistics][], 4.3 million people visited the
website in March. However, as seen in the illustration below, there was
a suspicious spike in visits that look like a possible attempt at
[referer spam][] (even though we don't publish referer information).
Almost all of the suspicious traffic was directed at the Spanish, Dutch,
and French Bitcoin.org home pages, leaving statistics for the rest of
the site fairly accurate.
We suspect the accurate number of unique visitors in March was around
2.0 million, roughly the same as in February.
![March traffic statistics graph](/img/blog/free/stats-2015-03.png)
Notable traffic patterns this month included:
* The [Full Node Guide][] first released last month received over 8,000
page views, a surprisingly high number for a new technical document.
Hopefully this is a sign that users really want to run full nodes for
themselves.
* The [Choose Your Wallet page][] continues to receive over 130,000 page
views a month, as it keeps on trying to help novice users choose
their first Bitcoin wallet.
* The [Bitcoin Core Download page][] has just as many page views as it
did last month (75,000) when Bitcoin Core 0.10.0 was released. If you
haven't upgraded yet to get new features like [headers-first block
sync][] and [lower vulnerability to OpenSSL code changes][], take some
time to read the [0.10.0 release notes][] to see what you're missing.
## Thank You Volunteers!
Special thanks to the 19 volunteers who contributed and commented
through [GitHub][] this month: anthonyc0603, arvicco, barmstrong,
Bitcoinference, borisstankovic, ConsumersResearch, dajohi, dquintela,
Firescar96, FrancisPouliot, gurnec, harding, larshesel, LinusU, louisjc,
luke-jr, muresanroland, pstratem, and saivann.
[HTML proofer]: https://github.com/gjtorikian/html-proofer
[Travis continuous integration (CI)]: https://travis-ci.org/bitcoin-dot-org/bitcoin.org
[Garen Torikian]: https://github.com/gjtorikian
[Choose Your Wallet]: /en/choose-your-wallet
[Transifex]: https://www.transifex.com/projects/p/bitcoinorg/
[Events page]: /en/events
[developer documentation]: /en/developer-documentation
[proposed]: https://github.com/bitcoin-dot-org/bitcoin.org/pull/793
[GitHub]: https://github.com/bitcoin-dot-org/bitcoin.org#how-to-participate
[their codebase]: https://github.com/kncgroup/bitcoin-wallet
[full node guide]: /en/full-node
[CHoose your wallet page]: /en/choose-your-wallet
[Bitcoin core download page]: /en/download
[headers-first block sync]: /en/developer-guide#headers-first
[lower vulnerability to OpenSSL code changes]: https://github.com/bitcoin/bips/blob/master/bip-0066.mediawiki
[0.10.0 release notes]: /en/release/v0.10.0
[website statistics]: https://bitcoin.org/stats/2015-03.html
[referer spam]: https://en.wikipedia.org/wiki/Referer_spam

View file

@ -1,90 +0,0 @@
---
# This file is licensed under the MIT License (MIT) available on
# http://opensource.org/licenses/MIT.
type: posts
layout: post
category: blog
title: "Dev Docs: New Glossary And Search Feature"
permalink: /en/posts/developer-docs-glossary-and-search.html
date: 2015-04-14
author: >
David A. Harding (<a href="mailto:dave@dtrt.org">email</a>, <a
href="https://github.com/harding">GitHub</a>,
<a href="http://www.reddit.com/user/harda/">Reddit</a>)
---
*Thanks to [several volunteers][] and the financial sponsorship of [The
Bitcoin Foundation][], we've added two major new features to the
[Bitcoin.org Developer Documentation][].*
A new [glossary section][] has been added to the Bitcoin.org Developer
Documentation, and with it comes a fully-Javascript search engine that
helps you look up glossary entries, Bitcoin Core RPCs, Bitcoin BIPs,
Script-language opcodes, and Bitcoin P2P protocol messages.
## Developer glossary main page
![Developer glossary main page](/img/blog/free/devglossary-main-page.png)
The glossary main page provides a search box and a sorted list of terms.
It uses a floating list so that it looks good on both mobiles and
desktop/laptop screens.
A link is provided at the bottom of the page to allow readers to
recommend new glossary terms. (It works like the Submit New Event link
on the [Events page][].)
### Glossary entries
![Glossary entries](/img/blog/free/devglossary-entries.png)
Each glossary entry has its own page providing a short definition
(limited to 255 characters), one or more synonyms, zero or more "not to
be confused with" terms, and zero or more links to resources on and off
Bitcoin.org. Separate pages were used to allow search engines to link
directly to the most relevant entry, rather than forcing users to scroll
through a giant page of definitions.
The glossary currently has:
* 89 glossary entry pages
* 51 additional synonyms
* 222 links (all internal to Bitcoin.org or to Bitcoin Wiki, BitcoinTalk, or Bitcoin StackExchange)
Each page includes links to edit it, view its history, or report an
issue about it.
### Dev search box
![Glossary search box](/img/blog/free/devglossary-search-box.png)
A Javascript-powered search box is added to the following pages: [Dev
Guide][], [Dev Reference][], [Dev Examples][], [Dev Glossary][], and individual
glossary entry pages.
The box allows finding the following by keyword, listed in the order
they appear in the search:
* Glossary entries (Bitcoin.org)
* RPCs (Bitcoin.org)
* Opcodes (Bitcoin Wiki)
* BIPs (just notable and non-withdrawn BIPs; GitHub.com BIPs repo)
* Bitcoin P2P protocol messages (Bitcoin.org)
The search uses [JQuery][] and [JQuery UI][], both MIT-licensed. Both are
loaded from the Bitcoin.org server so there's no stats leakage when
people load them.
[dev guide]: /en/developer-guide
[dev reference]: /en/developer-reference
[dev examples]: /en/developer-examples
[dev glossary]: /en/developer-glossary
[jquery]: https://jquery.com/
[jquery ui]: https://jqueryui.com/
[several volunteers]: https://github.com/bitcoin-dot-org/bitcoin.org/pull/793
[Bitcoin.org developer documentation]: /en/developer-documentation
[the bitcoin foundation]: https://bitcoinfoundation.org/
[glossary section]: /en/developer-glossary
[events page]: /en/events

View file

@ -1,41 +0,0 @@
---
# This file is licensed under the MIT License (MIT) available on
# http://opensource.org/licenses/MIT.
type: posts
layout: post
lang: en
category: blog
title: "Bitcoin.org Hard Fork Policy"
permalink: /en/posts/hard-fork-policy.html
date: 2015-06-16
---
Contentious hard forks are bad for Bitcoin. At the very best, a
contentious hard fork will leave people who chose the losing side of the
fork feeling disenfranchised. At the very worst, it will make bitcoins
permanently lose their value. In between are many possible outcomes, but
none of them are good.
The danger of a contentious hard fork is potentially so significant
that Bitcoin.org has decided to adopt a new policy:
> Bitcoin.org will not promote software or services that will leave the
> previous consensus because of an intentional and contentious hard fork attempt.
This policy applies to full node software, such as Bitcoin Core,
software forks of Bitcoin Core, and alternative full node
implementations.
It also applies to wallets and services that have the ability to detect
the contentious hard fork, and which release code or make announcements
indicating that they will cease operating on the side of the previous
consensus.
It does not apply to software that cannot detect the contentious hard
fork and which continues doing whatever it would've done anyway.
To be clear, we encourage wallet authors and service providers to offer
their opinions on hard fork proposals, and we will not penalize anyone
for contributing to a discussion. We will only stop promoting particular
wallets and services if they plan to move their users onto a
contentious hard fork by default.

View file

@ -1,45 +0,0 @@
---
# This file is licensed under the MIT License (MIT) available on
# http://opensource.org/licenses/MIT.
type: posts
layout: post
lang: en
category: blog
title: "Repository Move"
permalink: /en/posts/repository-move.html
date: 2015-06-23
author: |
<a href="https://bitcoin.org/en/about-us#maintenance">Bitcoin.org Maintainers</a>
---
Bitcoin.org has moved our main git repository to the new
*bitcoin-dot-org* GitHub organization:
<https://github.com/bitcoin-dot-org/bitcoin.org>
We moved to an independent organization to make clear that Bitcoin.org
and Bitcoin Core are separate projects, even though we frequently have
the pleasure of working together.
Nothing besides the repository URL has changed---Bitcoin.org will
continue to provide all of the same information and resources as it did
before. The [team of contributors][] is also staying the same.
Existing links to the old repository (including developer git
configurations) should continue to work, but we that suggest you upgrade
them to point to the new repository at your first convenience. Git users
can who have the Bitcoin.org repository as their `upstream` can run,
cd bitcoin.org
git remote set-url upstream 'https://github.com/bitcoin-dot-org/bitcoin.org'
All current [issues][] and [pull requests][] remain open, and any [forks hosted
on GitHub][] shouldn't need to be updated.
If you have any problems, please [open an issue][].
[team of contributors]: https://bitcoin.org/en/about-us#https://bitcoin.org/en/about-us#help
[issues]: https://github.com/bitcoin-dot-org/bitcoin.org/issues
[pull requests]: https://github.com/bitcoin-dot-org/bitcoin.org/pulls
[forks hosted on github]: https://github.com/bitcoin-dot-org/bitcoin.org/network
[open an issue]: https://github.com/bitcoin-dot-org/bitcoin.org/issues/new

View file

@ -1,103 +0,0 @@
---
# This file is licensed under the MIT License (MIT) available on
# http://opensource.org/licenses/MIT.
type: posts
layout: post
category: blog
title: "New Bitcoin Core Sub-Site"
permalink: /en/posts/bitcoin-core-subsite.html
## Set correct date at merge
date: 2015-09-14
author: |
<a href="https://github.com/harding">David A. Harding</a>
---
Bitcoin.org is proud to announce the addition of a dozen new pages to
the site about [Bitcoin Core][]. Several of the pages describe [Bitcoin
Core's powerful features][], others [provide help][] for Bitcoin Core
users, and several make it easier to [start contributing][] to
Bitcoin Core.
{:.center}
![Excerpts from Bitcoin.org's Bitcoin Core pages](/img/blog/free/bitcoin-core-pages-collage.png)
{:.center}
*Excerpts from Bitcoin.org's <a href="/en/bitcoin-core/">Bitcoin Core</a> pages*
Both Bitcoin Core and Bitcoin.org have come a long way since the site
began promoting the earliest public versions of the software.
{:.center}
![Bitcoin.org homepage, 3 March 2009](/img/blog/free/bitcoin-org-2009-03-03.png)
{:.center}
*Bitcoin.org homepage, 3 March 2009 ([Internet Archive][])*
These new pages give us a chance to introduce more recent Bitcoin users
to the advantages of full nodes like Bitcoin Core, particularly how full
validation [helps protect Bitcoin's essential decentralization][] from
takeover by a handful of miners, Bitcoin banks, and service providers.
## A Brief Guide to The New Pages
- [Bitcoin Core overview][]: provides a brief description of Bitcoin
Core and links to the other sections of the sub-site.
- [Feature overview][]: briefly describes some of Bitcoin Core's
leading benefits and links to pages that provide more details.
- [Get help page][]: resources to help Bitcoin Core users find help.
Prior to this PR, we also created and filled a category on the Bitcoin
Wiki with all the existing [Bitcoin Core help pages][].
- [Contribute overview][]: links to ways you can directly contribute to
Bitcoin Core and Bitcoin Core users.
## Future Plans
We plan to enhance this new section of the Bitcoin.org website by
collecting together some of Bitcoin Core's disparate documentation and
providing instructions for important ways users can enhance their privacy and
security while using Bitcoin Core—such as using Tor and an offline
wallet.
In addition, we hope to provide more resources that help businesses
understand the benefits of validating the transactions they receive with
their own full nodes.
If you want to help, please feel free to email the Bitcoin.org
documentation maintainer,
{{site.text.bitcoin_org_docs_maintainer_email_link}}.
## Thank You
Thank you to everyone who made these pages possible, especially the
people who reviewed Bitcoin.org pull requests [1044][],
[1009][], [1007][], [966][], [957][], and [869][] as well as the
[Bitcoin Foundation][] for their funding of the Bitcoin.org server
during the time these pages were written.
We hope you enjoy the new pages. If you see any problems, please don't
hesitate to [open an issue][].
[Bitcoin Core]: /en/bitcoin-core/
[Bitcoin Core's powerful features]: /en/bitcoin-core/features/
[provide help]: /en/bitcoin-core/help
[start contributing]: /en/bitcoin-core/contribute/
[Internet Archive]: https://web.archive.org/web/20090303195936/http://bitcoin.org/
[helps protect Bitcoin's essential decentralization]: /en/bitcoin-core/features/validation#help-protect-decentralization
[bitcoin core overview]: /en/bitcoin-core/
[feature overview]: /en/bitcoin-core/features/
[get help page]: /en/bitcoin-core/help
[Bitcoin Core help pages]: https://en.bitcoin.it/wiki/Category:Bitcoin_Core_documentation
[contribute overview]: /en/bitcoin-core/contribute/
[1044]: https://github.com/bitcoin-dot-org/bitcoin.org/pull/1044
[1009]: https://github.com/bitcoin-dot-org/bitcoin.org/pull/1009
[1007]: https://github.com/bitcoin-dot-org/bitcoin.org/pull/1007
[966]: https://github.com/bitcoin-dot-org/bitcoin.org/pull/966
[957]: https://github.com/bitcoin-dot-org/bitcoin.org/pull/957
[869]: https://github.com/bitcoin-dot-org/bitcoin.org/pull/869
[Bitcoin Foundation]: https://bitcoinfoundation.org/
[open an issue]: https://github.com/bitcoin-dot-org/bitcoin.org/issues/new

View file

@ -1,121 +0,0 @@
---
# This file is licensed under the MIT License (MIT) available on
# http://opensource.org/licenses/MIT.
type: posts
layout: post
category: blog
title: "Updated Instructions: How to Run a Full Node"
permalink: /en/posts/how-to-run-a-full-node.html
date: 2016-12-31
author: |
<a href="https://github.com/wbnns">Will Binns</a>
---
{:.center}
![How to Run a Full Node](/img/blog/free/how-to-run-a-full-bitcoin-node.png)
Updated instructions for [how to run a full node](https://bitcoin.org/en/full-node)
as of version **0.13.1** are now available on Bitcoin.org. These instructions allow
one to quickly get set up and running with a full node on the following
operating systems:
- [Linux](https://bitcoin.org/en/full-node#linux-instructions)
- [MacOS](https://bitcoin.org/en/full-node#mac-os-x-instructions)
- [Windows](https://bitcoin.org/en/full-node#windows-instructions)
In addition to the above operating systems, tips on [how to configure a full
bitcoin node for a local area network](https://bitcoin.org/en/full-node#network-configuration)
and [how to tweak the reference client configuration](https://bitcoin.org/en/full-node#configuration-tuning)
are available.
## Why is running a full bitcoin node important?
Full nodes help enforce the consensus rules of the Bitcoin network. When a full
node client is running, it downloads every new block and every new transaction
and checks them to make sure they are valid. Here are some examples of consensus
rules, though there are many more:
- Blocks may only [create](https://en.bitcoin.it/wiki/Controlled_supply) a
certain number of bitcoins.
- Transactions must have correct signatures for the bitcoins being spent.
- Transactions/blocks must be in the correct data format.
- Within the [block chain](https://en.bitcoin.it/wiki/Block_chain), a transaction
output cannot be double-spent.
*Read more about what a full node is, the consensus rules above and other
incentives for supporting the network in the [Bitcoin Wiki](https://en.bitcoin.it/wiki/Full_node).*
## Minimum Requirements
Bitcoin Core full nodes have certain requirements. If you try running a node on
weak hardware, it may workbut youll likely spend more time dealing with
issues. If you can meet the following requirements, youll have an easy-to-use
node.
- Desktop or laptop hardware running recent versions of Windows, Mac OS X, or
Linux.
- 125GB of free disk space (size of the blockchain plus room to grow)
- 2GB of memory (RAM)
- A broadband Internet connection with upload speeds of at least 400 kilobits
(50 kilobytes) per second
- An unmetered connection, a connection with high upload limits, or a connection
you regularly monitor to ensure it doesnt exceed its upload limits. Its
common for full nodes on high-speed connections to use 200GB in uploads or more
a month. Download usage is around 20GB/month, plus around an additional 100GB
the first time you start your node.
- 6 hours/day that your full node can be left running. (You can do other things
with your computer while running a full node.) More hours would be better, and
best of all would be if you can run your node continuously.
**Note:** many operating systems today (Windows, Mac, and Linux) enter a low-power
mode after the screensaver activates, slowing or halting network traffic. This
is often the default setting on laptops and on all Mac OS X laptops and
desktops. Check your screensaver settings and disable automatic “sleep” or
“suspend” options to ensure you support the network whenever your computer is
running.
## What to do if you need help
Please seek out assistance in the [community](https://bitcoin.org/en/community)
if you need help setting up your full node correctly to handle high-value and
privacy-sensitive tasks. Do your own diligence to ensure who you get help from
is ethical, reputable and qualified to assist you.
## Acknowledgments
A special thanks goes to the contributors (in no preferential order) who have
worked to improve this page over time:
- [David Harding](https://github.com/harding)
- [Kevin Cooper](https://github.com/kevcooper)
- [Joseph Becher](https://github.com/drazisil)
- [Jorgeminator](https://github.com/Jorgeminator)
- [Gyomu](https://github.com/Gyomu)
- [Jonas Schnelli](https://github.com/jonasschnelli)
- [Marko Falke](https://github.com/MarcoFalke)
- [cpmx](https://github.com/cpmx)
- [anduck](https://github.com/anduck)
- [dabura667](https://github.com/dabura667)
- [seusher](https://github.com/seusher)
**Interested in getting involved?**
[Learn how you can participate](https://github.com/bitcoin-dot-org/bitcoin.org#how-to-participate).

View file

@ -1,58 +0,0 @@
---
# This file is licensed under the MIT License (MIT) available on
# http://opensource.org/licenses/MIT.
type: posts
layout: post
category: blog
title: "Bitcoin Exchanges: Options for Newcomers to Bitcoin Now Available"
permalink: /en/posts/bitcoin-exchanges-options-for-newcomers.html
date: 2017-02-03
author: |
<a href="https://github.com/wbnns">Will Binns</a>
---
{:.center}
![Bitcoin Exchanges](/img/blog/free/bitcoin-exchanges.png)
[A directory of Bitcoin Exchanges servicing the worlds 20 largest
economies](https://bitcoin.org/en/exchanges), as well as several international
options (serving many countries) are now available on Bitcoin.org.
## Helping People Interested in Bitcoin, Get Bitcoin
This new addition to the site:
- Links to the `Find an Exchange` button on the [Getting Started](https://bitcoin.org/en/getting-started)
page and helps many of the new people entering the Bitcoin ecosystem via
Bitcoin.org, get bitcoin.
- Improves SEO for Bitcoin.org, because the site can now potentially rank very
well for “Bitcoin Exchange” as well as other key phrases that include country
names that are contained on the page (i.e. Bitcoin Exchange China, Bitcoin
Exchange India, etc.).
- Has unique anchor links for each country that people can share on social media
that will allow others to find the bitcoin exchanges that are available for
their specific country.
- Allows Bitcoin.org to focus the [wallets page](https://bitcoin.org/en/choose-your-wallet)
on wallets that allow people to maintain full control over their funds
(Resolving [issue #1109](https://github.com/bitcoin-dot-org/bitcoin.org/issues/1109),
because custodial wallets that provide exchange services can be moved off of the
wallets page to this new page).
- Is also accessible via the Resources `dropdown` menu.
## Questions, Comments & Feedback
Questions, issues, suggestions or feedback are always welcome on Bitcoin.org. If
interested in contributing in this regard, please open an issue or submit a pull
request.
## Use Discretion when Choosing an Exchange
As noted in the above screen shot, Bitcoin Exchanges provide varying degrees of
safety, security, privacy, and control over your funds and information. Perform
your own due diligence and choose a wallet where you will keep your bitcoin
before selecting an exchange.
=== === ===
Interested in getting involved with Bitcoin.org?
[Learn how you can participate](https://github.com/bitcoin-dot-org/bitcoin.org#how-to-participate).

View file

@ -1,993 +0,0 @@
---
# This file is licensed under the MIT License (MIT) available on
# http://opensource.org/licenses/MIT.
type: posts
layout: post
category: blog
title: "Bitcoin Core Version 0.14.0 Released"
permalink: /en/posts/bitcoin-core-version-0-14-0-released.html
date: 2017-03-08
author: |
<a href="https://github.com/wbnns">Will Binns</a>
---
{:.center}
![Bitcoin Core Version 0.14.0](/img/blog/free/bitcoin-core-0140.png)
[Bitcoin Core version 0.14.0 is now available](https://bitcoin.org/en/download).
This is a new major version release, including new features, various bugfixes
and performance improvements, as well as updated translations.
Please report bugs using the [issue tracker on GitHub](https://github.com/bitcoin/bitcoin/issues).
[Subscribe here](https://bitcoincore.org/en/list/announcements/join/) to receive
security and update notifications.
## Compatibility
Bitcoin Core is extensively tested on multiple operating systems using
the Linux kernel, macOS 10.8+, and Windows Vista and later.
Microsoft ended support for Windows XP on [April 8th,
2014](https://www.microsoft.com/en-us/WindowsForBusiness/end-of-xp-support),
No attempt is made to prevent installing or running the software on Windows XP,
you can still do so at your own risk but be aware that there are known
instabilities and issues. Please do not report issues about Windows XP to the
[issue tracker](https://github.com/bitcoin/bitcoin/issues).
Bitcoin Core should also work on most other Unix-like systems but is not
frequently tested on them.
## Notable changes
### Performance Improvements
Validation speed and network propagation performance have been greatly
improved, leading to much shorter sync and initial block download times.
- The script signature cache has been reimplemented as a "cuckoo cache",
allowing for more signatures to be cached and faster lookups.
- Assumed-valid blocks have been introduced which allows script validation to
be skipped for ancestors of known-good blocks, without changing the security
model. See below for more details.
- In some cases, compact blocks are now relayed before being fully validated as
per BIP152.
- P2P networking has been refactored with a focus on concurrency and
throughput. Network operations are no longer bottlenecked by validation. As a
result, block fetching is several times faster than previous releases in many
cases.
- The UTXO cache now claims unused mempool memory. This speeds up initial block
download as UTXO lookups are a major bottleneck there, and there is no use for
the mempool at that stage.
### Manual Pruning
Bitcoin Core has supported automatically pruning the blockchain since 0.11.
Pruning the blockchain allows for significant storage space savings as the vast
majority of the downloaded data can be discarded after processing so very little
of it remains on the disk.
Manual block pruning can now be enabled by setting `-prune=1`. Once that is set,
the RPC command `pruneblockchain` can be used to prune the blockchain up to the
specified height or timestamp.
### `getinfo` has been deprecated
The `getinfo` RPC command has been deprecated. Each field in the RPC call
has been moved to another command's output with that command also giving
additional information that `getinfo` did not provide. The following table
shows where each field has been moved to:
![getinfo RPC deprecation](/img/blog/free/getinfo-deprecation.png)
### ZMQ On Windows
Previously the ZeroMQ notification system was unavailable on Windows
due to various issues with ZMQ. These have been fixed upstream and
now ZMQ can be used on Windows. Please see [this
document](https://github.com/bitcoin/bitcoin/blob/master/doc/zmq.md) for
help with using ZMQ in general.
### Nested RPC Commands in Debug Console
The ability to nest RPC commands has been added to the debug console. This
allows users to have the output of a command become the input to another
command without running the commands separately.
The nested RPC commands use bracket syntax (i.e. `getwalletinfo()`) and can be
nested (i.e. `getblock(getblockhash(1))`). Simple queries can be done with
square brackets where object values are accessed with either an array index or a
non-quoted string. Both commas and spaces can be
used to separate parameters in both the bracket syntax and normal RPC command
syntax.
### Network Activity Toggle
A RPC command and GUI toggle have been added to enable or disable all p2p
network activity. The network status icon in the bottom right hand corner
is now the GUI toggle. Clicking the icon will either enable or disable all
p2p network activity. If network activity is disabled, the icon will
be grayed out with an X on top of it.
Additionally the `setnetworkactive` RPC command has been added which does
the same thing as the GUI icon. The command takes one boolean parameter,
`true` enables networking and `false` disables it.
### Out-of-sync Modal Info Layer
When Bitcoin Core is out-of-sync on startup, a semi-transparent information
layer will be shown over top of the normal display. This layer contains
details about the current sync progress and estimates the amount of time
remaining to finish syncing. This layer can also be hidden and subsequently
unhidden by clicking on the progress bar at the bottom of the window.
### Support for JSON-RPC Named Arguments
Commands sent over the JSON-RPC interface and through the `bitcoin-cli` binary
can now use named arguments. This follows the [JSON-RPC specification](http://www.jsonrpc.org/specification)
for passing parameters by-name with an object.
`bitcoin-cli` has been updated to support this by parsing `name=value` arguments
when the `-named` option is given.
Some examples:
`src/bitcoin-cli -named help command="help"`
`src/bitcoin-cli -named getblockhash height=0`
`src/bitcoin-cli -named getblock blockhash=000000000019d6689c085ae165831e934...`
`src/bitcoin-cli -named sendtoaddress address="(snip)" amount="1.0" subtractfeefromamount=true`
The order of arguments doesn't matter in this case. Named arguments are also
useful to leave out arguments that should stay at their default value. The
rarely-used arguments `comment` and `comment_to` to `sendtoaddress`, for
example, can be left out. However, this is not yet implemented for many RPC
calls, this is expected to land in a later release.
The RPC server remains fully backwards compatible with positional arguments.
### Opt into RBF When Sending
A new startup option, `-walletrbf`, has been added to allow users to have all
transactions sent opt into RBF support. The default value for this option is
currently `false`, so transactions will not opt into RBF by default. The new
`bumpfee` RPC can be used to replace transactions that opt into RBF.
### Sensitive Data Is No Longer Stored In Debug Console History
The debug console maintains a history of previously entered commands that can be
accessed by pressing the Up-arrow key so that users can easily reuse previously
entered commands. Commands which have sensitive information such as passphrases
and private keys will now have a `(...)` in place of the parameters when
accessed through the history.
### Retaining the Mempool Across Restarts
The mempool will be saved to the data directory prior to shutdown to a
`mempool.dat` file. This file preserves the mempool so that when the node
restarts the mempool can be filled with transactions without waiting for new
transactions to be created. This will also preserve any changes made to a
transaction through commands such as `prioritisetransaction` so that those
changes will not be lost.
### Final Alert
The Alert System was [disabled and deprecated](https://bitcoin.org/en/alert/2016-11-01-alert-retirement)
in Bitcoin Core 0.12.1 and removed in 0.13.0. The Alert System was retired with
a maximum sequence final alert which causes any nodes supporting the Alert
System to display a static hard-coded "Alert Key Compromised" message which also
prevents any other alerts from overriding it. This final alert is hard-coded
into this release so that all old nodes receive the final alert.
### GUI Changes
- After resetting the options by clicking the `Reset Options` button
in the options dialog or with the `-resetguioptions` startup option,
the user will be prompted to choose the data directory again. This
is to ensure that custom data directories will be kept after the
option reset which clears the custom data directory set via the choose
datadir dialog.
- Multiple peers can now be selected in the list of peers in the debug
window. This allows for users to ban or disconnect multiple peers
simultaneously instead of banning them one at a time.
- An indicator has been added to the bottom right hand corner of the main
window to indicate whether the wallet being used is a HD wallet. This
icon will be grayed out with an X on top of it if the wallet is not a
HD wallet.
### Low-level RPC changes
- `importprunedfunds` only accepts two required arguments. Some versions accept
an optional third arg, which was always ignored. Make sure to never pass more
than two arguments.
- The first boolean argument to `getaddednodeinfo` has been removed. This is
an incompatible change.
- RPC command `getmininginfo` loses the "testnet" field in favor of the more
generic "chain" (which has been present for years).
- A new RPC command `preciousblock` has been added which marks a block as
precious. A precious block will be treated as if it were received earlier
than a competing block.
- A new RPC command `importmulti` has been added which receives an array of
JSON objects representing the intention of importing a public key, a
private key, an address and script/p2sh
- Use of `getrawtransaction` for retrieving confirmed transactions with unspent
outputs has been deprecated. For now this will still work, but in the future
it may change to only be able to retrieve information about transactions in
the mempool or if `txindex` is enabled.
- A new RPC command `getmemoryinfo` has been added which will return
information
about the memory usage of Bitcoin Core. This was added in conjunction with
optimizations to memory management. See [Pull #8753](https://github.com/bitcoin/bitcoin/pull/8753)
for more information.
- A new RPC command `bumpfee` has been added which allows replacing an
unconfirmed wallet transaction that signaled RBF (see the `-walletrbf`
startup option above) with a new transaction that pays a higher fee, and
should be more likely to get confirmed quickly.
### HTTP REST Changes
- UTXO set query responses were changed to return status code `HTTP_BAD_REQUEST`
(400) instead of `HTTP_INTERNAL_SERVER_ERROR` (500) when requests contain
invalid parameters.
### Minimum Fee Rate Policies
Since the changes in 0.12 to automatically limit the size of the mempool and
improve the performance of block creation in mining code it has not been
important for relay nodes or miners to set `-minrelaytxfee`. With this release
the following concepts that were tied to this option have been separated out:
- incremental relay fee used for calculating BIP 125 replacement and mempool
limiting. (1000 satoshis/kB)
- calculation of threshold for a dust output. (effectively 3 * 1000 satoshis/kB)
- minimum fee rate of a package of transactions to be included in a block
created by the mining code. If miners wish to set this minimum they can use
the new `-blockmintxfee` option. (defaults to 1000 satoshis/kB)
The `-minrelaytxfee` option continues to exist but is recommended to be left
unset.
### Fee Estimation Changes
- Since 0.13.2 fee estimation for a confirmation target of 1 block has been
disabled. The fee slider will no longer be able to choose a target of 1 block.
This is only a minor behavior change as there was often insufficient
data for this target anyway. `estimatefee 1` will now always return -1 and
`estimatesmartfee 1` will start searching at a target of 2.
- The default target for fee estimation is changed to 6 blocks in both the GUI
(previously 25) and for RPC calls (previously 2).
### Removal of Priority Estimation
- Estimation of "priority" needed for a transaction to be included within a
target
number of blocks has been removed. The RPC calls are deprecated and will
either
return -1 or 1e24 appropriately. The format for `fee_estimates.dat` has also
changed to no longer save these priority estimates. It will automatically be
converted to the new format which is not readable by prior versions of the
software.
- Support for "priority" (coin age) transaction sorting for mining is
considered deprecated in Core and will be removed in the next major version.
This is not to be confused with the `prioritisetransaction` RPC which will
remain
supported by Core for adding fee deltas to transactions.
### P2P connection management
- Peers manually added through the `-addnode` option or `addnode` RPC now have
their own
limit of eight connections which does not compete with other inbound or
outbound
connection usage and is not subject to the limitation imposed by the
`-maxconnections`
option.
- New connections to manually added peers are performed more quickly.
### Introduction of assumed-valid blocks
- A significant portion of the initial block download time is spent verifying
scripts/signatures. Although the verification must pass to ensure the
security
of the system, no other result from this verification is needed: If the node
knew the history of a given block were valid it could skip checking scripts
for its ancestors.
- A new configuration option 'assumevalid' is provided to express this knowledge
to the software. Unlike the 'checkpoints' in the past this setting does not
force the use of a particular chain: chains that are consistent with it are
processed quicker, but other chains are still accepted if they'd otherwise
be chosen as best. Also unlike 'checkpoints' the user can configure which
block history is assumed true, this means that even outdated software can
sync more quickly if the setting is updated by the user.
- Because the validity of a chain history is a simple objective fact it is much
easier to review this setting. As a result the software ships with a default
value adjusted to match the current chain shortly before release. The use
of this default value can be disabled by setting -assumevalid=0
### Fundrawtransaction change address reuse
- Before 0.14, `fundrawtransaction` was by default wallet stateless. In
almost all cases `fundrawtransaction` does add a change-output to the
outputs of the funded transaction. Before 0.14, the used keypool key was
never marked as change-address key and directly returned to the keypool
(leading to address reuse). Before 0.14, calling `getnewaddress`
directly after `fundrawtransaction` did generate the same address as
the change-output address.
- Since 0.14, fundrawtransaction does reserve the change-output-key from
the keypool by default (optional by setting `reserveChangeKey`, default =
`true`)
- Users should also consider using `getrawchangeaddress()` in conjunction
with `fundrawtransaction`'s `changeAddress` option.
### Unused mempool memory used by coincache
- Before 0.14, memory reserved for mempool (using the `-maxmempool` option)
went unused during initial block download, or IBD. In 0.14, the UTXO DB cache
(controlled with the `-dbcache` option) borrows memory from the mempool
when there is extra memory available. This may result in an increase in
memory usage during IBD for those previously relying on only the `-dbcache`
option to limit memory during that time.
## 0.14.0 Change log
Detailed release notes follow. This overview includes changes that affect
behavior, not code moves, minor refactors and string updates. For convenience
in locating the code changes and accompanying discussion, both the pull request
and git merge commit are mentioned.
### RPC and other APIs
- \#8421 `b77bb95` httpserver: drop boost dependency (theuni)
- \#8638 `f061415` rest.cpp: change `HTTP_INTERNAL_SERVER_ERROR` to
`HTTP_BAD_REQUEST` (djpnewton)
- \#8272 `91990ee` Make the dummy argument to getaddednodeinfo optional (sipa)
- \#8722 `bb843ad` bitcoin-cli: More detailed error reporting (laanwj)
- \#6996 `7f71a3c` Add preciousblock RPC (sipa)
- \#8788 `97c7f73` Give RPC commands more information about the RPC request
(jonasschnelli)
- \#7948 `5d2c8e5` Augment getblockchaininfo bip9\_softforks data (mruddy)
- \#8980 `0e22855` importmulti: Avoid using boost::variant::operator!=, which is
only in newer boost versions (luke-jr)
- \#9025 `4d8558a` Getrawtransaction should take a bool for verbose (jnewbery)
- \#8811 `5754e03` Add support for JSON-RPC named arguments (laanwj)
- \#9520 `2456a83` Deprecate non-txindex getrawtransaction and better warning
(sipa)
- \#9518 `a65ced1` Return height of last block pruned by pruneblockchain RPC
(ryanofsky)
- \#9222 `7cb024e` Add 'subtractFeeFromAmount' option to 'fundrawtransaction'
(dooglus)
- \#8456 `2ef52d3` Simplified `bumpfee` command (mrbandrews)
- \#9516 `727a798` Bug-fix: listsinceblock: use fork point as reference for
blocks in reorg'd chains (kallewoof)
- \#9640 `7bfb770` Bumpfee: bugfixes for error handling and feerate calculation
(sdaftuar)
- \#9673 `8d6447e` Set correct metadata on bumpfee wallet transactions
(ryanofsky)
- \#9650 `40f7e27` Better handle invalid parameters to signrawtransaction
(TheBlueMatt)
- \#9682 `edc9e63` Require timestamps for importmulti keys (ryanofsky)
- \#9108 `d8e8b06` Use importmulti timestamp when importing watch only keys (on
top of #9682) (ryanofsky)
- \#9756 `7a93af8` Return error when importmulti called with invalid address
(ryanofsky)
- \#9778 `ad168ef` Add two hour buffer to manual pruning (morcos)
- \#9761 `9828f9a` Use 2 hour grace period for key timestamps in importmulti
rescans (ryanofsky)
- \#9474 `48d7e0d` Mark the minconf parameter to move as ignored (sipa)
- \#9619 `861cb0c` Bugfix: RPC/Mining: GBT should return 1 MB sizelimit before
segwit activates (luke-jr)
- \#9773 `9072395` Return errors from importmulti if complete rescans are not
successful (ryanofsky)
### Block and transaction handling
- \#8391 `37d83bb` Consensus: Remove ISM (NicolasDorier)
- \#8365 `618c9dd` Treat high-sigop transactions as larger rather than rejecting
them (sipa)
- \#8814 `14b7b3f` wallet, policy: ParameterInteraction: Don't allow 0 fee
(MarcoFalke)
- \#8515 `9bdf526` A few mempool removal optimizations (sipa)
- \#8448 `101c642` Store mempool and prioritization data to disk (sipa)
- \#7730 `3c03dc2` Remove priority estimation (morcos)
- \#9111 `fb15610` Remove unused variable `UNLIKELY_PCT` from fees.h (fanquake)
- \#9133 `434e683` Unset fImporting for loading mempool (morcos)
- \#9179 `b9a87b4` Set `DEFAULT_LIMITFREERELAY` = 0 kB/minute (MarcoFalke)
- \#9239 `3fbf079` Disable fee estimates for 1-block target (morcos)
- \#7562 `1eef038` Bump transaction version default to 2 (btcdrak)
- \#9313,#9367 If we don't allow free txs, always send a fee filter (morcos)
- \#9346 `b99a093` Batch construct batches (sipa)
- \#9262 `5a70572` Prefer coins that have fewer ancestors, sanity check txn
before ATMP (instagibbs)
- \#9288 `1ce7ede` Fix a bug if the min fee is 0 for FeeFilterRounder (morcos)
- \#9395 `0fc1c31` Add test for `-walletrejectlongchains` (morcos)
- \#9107 `7dac1e5` Safer modify new coins (morcos)
- \#9312 `a72f76c` Increase mempool expiry time to 2 weeks (morcos)
- \#8610 `c252685` Share unused mempool memory with coincache (sipa)
- \#9138 `f646275` Improve fee estimation (morcos)
- \#9408 `46b249e` Allow shutdown during LoadMempool, dump only when necessary
(jonasschnelli)
- \#9310 `8c87f17` Assert FRESH validity in CCoinsViewCache::BatchWrite
(ryanofsky)
- \#7871 `e2e624d` Manual block file pruning (mrbandrews)
- \#9507 `0595042` Fix use-after-free in CTxMemPool::removeConflicts() (sdaftuar)
- \#9380 `dd98f04` Separate different uses of minimum fees (morcos)
- \#9596 `71148b8` bugfix save feeDelta instead of priorityDelta in DumpMempool
(morcos)
- \#9371 `4a1dc35` Notify on removal (morcos)
- \#9519 `9b4d267` Exclude RBF replacement txs from fee estimation (morcos)
- \#8606 `e2a1a1e` Fix some locks (sipa)
- \#8681 `6898213` Performance Regression Fix: Pre-Allocate txChanged vector
(JeremyRubin)
- \#8223 `744d265` c++11: Use std::unique\_ptr for block creation (domob1812)
- \#9125 `7490ae8` Make CBlock a vector of shared\_ptr of CTransactions (sipa)
- \#8930 `93566e0` Move orphan processing to ActivateBestChain (TheBlueMatt)
- \#8580 `46904ee` Make CTransaction actually immutable (sipa)
- \#9240 `a1dcf2e` Remove txConflicted (morcos)
- \#8589 `e8cfe1e` Inline CTxInWitness inside CTxIn (sipa)
- \#9349 `2db4cbc` Make CScript (and prevector) c++11 movable (sipa)
- \#9252 `ce5c1f4` Release cs\_main before calling ProcessNewBlock, or processing
headers (cmpctblock handling) (sdaftuar)
- \#9283 `869781c` A few more CTransactionRef optimizations (sipa)
- \#9499 `9c9af5a` Use recent-rejects, orphans, and recently-replaced txn for
compact-block-reconstruction (TheBlueMatt)
- \#9813 `3972a8e` Read/write mempool.dat as a binary (paveljanik)
### P2P protocol and network code
- \#8128 `1030fa7` Turn net structures into dumb storage classes (theuni)
- \#8282 `026c6ed` Feeler connections to increase online addrs in the tried table
(EthanHeilman)
- \#8462 `53f8f22` Move AdvertiseLocal debug output to net category (Mirobit)
- \#8612 `84decb5` Check for compatibility with download in
FindNextBlocksToDownload (sipa)
- \#8594 `5b2ea29` Do not add random inbound peers to addrman (gmaxwell)
- \#8085 `6423116` Begin encapsulation (theuni)
- \#8715 `881d7ea` only delete CConnman if it's been created (theuni)
- \#8707 `f07424a` Fix maxuploadtarget setting (theuni)
- \#8661 `d2e4655` Do not set an addr time penalty when a peer advertises itself
(gmaxwell)
- \#8822 `9bc6a6b` Consistent checksum handling (laanwj)
- \#8936 `1230890` Report NodeId in misbehaving debug (rebroad)
- \#8968 `3cf496d` Don't hold cs\_main when calling ProcessNewBlock from a
cmpctblock (TheBlueMatt)
- \#9002 `e1d1f57` Make connect=0 disable automatic outbound connections
(gmaxwell)
- \#9050 `fcf61b8` Make a few values immutable, and use deterministic randomness
for the localnonce (theuni)
- \#8969 `3665483` Decouple peer-processing-logic from block-connection-logic
(#2) (TheBlueMatt)
- \#8708 `c8c572f` have CConnman handle message sending (theuni)
- \#8709 `1e50d22` Allow filterclear messages for enabling TX relay only
(rebroad)
- \#9045 `9f554e0` Hash P2P messages as they are received instead of at
process-time (TheBlueMatt)
- \#9026 `dc6b940` Fix handling of invalid compact blocks (sdaftuar)
- \#8996 `ab914a6` Network activity toggle (luke-jr)
- \#9131 `62af164` fNetworkActive is not protected by a lock, use an atomic
(jonasschnelli)
- \#8872 `0c577f2` Remove block-request logic from INV message processing
(TheBlueMatt)
- \#8690 `791b58d` Do not fully sort all nodes for addr relay (sipa)
- \#9128 `76fec09` Decouple CConnman and message serialization (theuni)
- \#9226 `3bf06e9` Remove fNetworkNode and pnodeLocalHost (gmaxwell)
- \#9352 `a7f7651` Attempt reconstruction from all compact block announcements
(sdaftuar)
- \#9319 `a55716a` Break addnode out from the outbound connection limits
(gmaxwell)
- \#9261 `2742568` Add unstored orphans with rejected parents to recentRejects
(morcos)
- \#9441 `8b66bf7` Massive speedup. Net locks overhaul (theuni)
- \#9375 `3908fc4` Relay compact block messages prior to full block connection
(TheBlueMatt)
- \#9400 `8a445c5` Set peers as HB peers upon full block validation (instagibbs)
- \#9561 `6696b46` Wake message handling thread when we receive a new block
(TheBlueMatt)
- \#9535 `82274c0` Split CNode::cs\_vSend: message processing and message sending
(TheBlueMatt)
- \#9606 `3f9f962` Consistently use GetTimeMicros() for inactivity checks
(sdaftuar)
- \#9594 `fd70211` Send final alert message to older peers after connecting
(gmaxwell)
- \#9626 `36966a1` Clean up a few CConnman cs\_vNodes/CNode things (TheBlueMatt)
- \#9609 `4966917` Fix remaining net assertions (theuni)
- \#9671 `7821db3` Fix super-unlikely race introduced in 236618061a445d2cb11e72
(TheBlueMatt)
- \#9730 `33f3b21` Remove bitseed.xf2.org form the dns seed list (jonasschnelli)
- \#9698 `2447c10` Fix socket close race (theuni)
- \#9708 `a06ede9` Clean up all known races/platform-specific UB at the time PR
was opened (TheBlueMatt)
- \#9715 `b08656e` Disconnect peers which we do not receive VERACKs from within
60 sec (TheBlueMatt)
- \#9720 `e87ce95` Fix banning and disallow sending messages before receiving
verack (theuni)
- \#9268 `09c4fd1` Fix rounding privacy leak introduced in #9260 (TheBlueMatt)
- \#9075 `9346f84` Decouple peer-processing-logic from block-connection-logic
(#3) (TheBlueMatt)
- \#8688 `047ded0` Move static global randomizer seeds into CConnman (sipa)
- \#9289 `d9ae1ce` net: drop boost::thread\_group (theuni)
### Validation
- \#9014 `d04aeba` Fix block-connection performance regression (TheBlueMatt)
- \#9299 `d52ce89` Remove no longer needed check for premature v2 txs (morcos)
- \#9273 `b68685a` Remove unused `CDiskBlockPos*` argument from ProcessNewBlock
(TheBlueMatt)
- \#8895 `b83264d` Better SigCache Implementation (JeremyRubin)
- \#9490 `e126d0c` Replace FindLatestBefore used by importmulti with
FindEarliestAtLeast (gmaxwell)
- \#9484 `812714f` Introduce assumevalid setting to skip validation presumed
valid scripts (gmaxwell)
- \#9511 `7884956` Don't overwrite validation state with corruption check
(morcos)
- \#9765 `1e92e04` Harden against mistakes handling invalid blocks (sdaftuar)
- \#9779 `3c02b95` Update nMinimumChainWork and defaultAssumeValid (gmaxwell)
- \#8524 `19b0f33` Precompute sighashes (sipa)
- \#9791 `1825a03` Avoid VLA in hash.h (sipa)
### Build system
- \#8238 `6caf3ee` ZeroMQ 4.1.5 && ZMQ on Windows (fanquake)
- \#8520 `b40e19c` Remove check for `openssl/ec.h` (laanwj)
- \#8617 `de07fdc` Include instructions to extract Mac OS X SDK on Linux using
7zip and SleuthKit (luke-jr)
- \#8566 `7b98895` Easy to use gitian building script (achow101)
- \#8604 `f256843` build,doc: Update for 0.13.0+ and OpenBSD 5.9 (laanwj)
- \#8640 `2663e51` depends: Remove Qt46 package (fanquake)
- \#8645 `8ea4440` Remove unused Qt 4.6 patch (droark)
- \#8608 `7e9ab95` Install manpages via make install, also add some autogenerated
manpages (nomnombtc)
- \#8781 `ca69ef4` contrib: delete `qt_translations.py` (MarcoFalke)
- \#8783 `64dc645` share: remove qt/protobuf.pri (MarcoFalke)
- \#8423 `3166dff` depends: expat 2.2.0, ccache 3.3.1, fontconfig 2.12.1
(fanquake)
- \#8791 `b694b0d` travis: cross-mac: explicitly enable gui (MarcoFalke)
- \#8820 `dc64141` depends: Fix Qt compilation with Xcode 8 (fanquake)
- \#8730 `489a6ab` depends: Add libevent compatibility patch for windows (laanwj)
- \#8819 `c841816` depends: Boost 1.61.0 (fanquake)
- \#8826 `f560d95` Do not include `env_win.cc` on non-Windows systems
(paveljanik)
- \#8948 `e077e00` Reorder Windows gitian build order to match Linux (Michagogo)
- \#8568 `078900d` new var `DIST_CONTRIB` adds useful things for packagers from
contrib (nomnombtc)
- \#9114 `21e6c6b` depends: Set `OSX_MIN_VERSION` to 10.8 (fanquake)
- \#9140 `018a4eb` Bugfix: Correctly replace generated headers and fail cleanly
(luke-jr)
- \#9156 `a8b2a82` Add compile and link options echo to configure (jonasschnelli)
- \#9393 `03d85f6` Include cuckoocache header in Makefile (MarcoFalke)
- \#9420 `bebe369` Fix linker error when configured with --enable-lcov (droark)
- \#9412 `53442af` Fix 'make deploy' for OSX (jonasschnelli)
- \#9475 `7014506` Let autoconf detect presence of `EVP_MD_CTX_new` (luke-jr)
- \#9513 `bbf193f` Fix qt distdir builds (theuni)
- \#9471 `ca615e6` depends: libevent 2.1.7rc (fanquake)
- \#9468 `f9117f2` depends: Dependency updates for 0.14.0 (fanquake)
- \#9469 `01c4576` depends: Qt 5.7.1 (fanquake)
- \#9574 `5ac6687` depends: Fix QT build on OSX (fanquake)
- \#9646 `720b579` depends: Fix cross build for qt5.7 (theuni)
- \#9705 `6a55515` Add options to override BDB cflags/libs (laanwj)
- \#8249 `4e1567a` Enable (and check for) 64-bit ASLR on Windows (laanwj)
- \#9758 `476cc47` Selectively suppress deprecation warnings (jonasschnelli)
- \#9783 `6d61a2b` release: bump gitian descriptors for a new 0.14 package cache
(theuni)
- \#9789 `749fe95` build: add --enable-werror and warn on vla's (theuni)
- \#9831 `99fd85c` build: force a c++ standard to be specified (theuni)
### GUI
- \#8192 `c503863` Remove URLs from About dialog translations (fanquake)
- \#8540 `36404ae` Fix random segfault when closing "Choose data directory"
dialog (laanwj)
- \#8517 `2468292` Show wallet HD state in statusbar (jonasschnelli)
- \#8463 `62a5a8a` Remove Priority from coincontrol dialog (MarcoFalke)
- \#7579 `0606f95` Show network/chain errors in the GUI (jonasschnelli)
- \#8583 `c19f8a4` Show XTHIN in GUI (rebroad)
- \#7783 `4335d5a` RPC-Console: support nested commands and simple value queries
(jonasschnelli)
- \#8672 `6052d50` Show transaction size in transaction details window (Cocosoft)
- \#8777 `fec6af7` WalletModel: Expose disablewallet (MarcoFalke)
- \#8371 `24f72e9` Add out-of-sync modal info layer (jonasschnelli)
- \#8885 `b2fec4e` Fix ban from qt console (theuni)
- \#8821 `bf8e68a` sync-overlay: Don't block during reindex (MarcoFalke)
- \#8906 `088d1f4` sync-overlay: Don't show progress twice (MarcoFalke)
- \#8918 `47ace42` Add "Copy URI" to payment request context menu (luke-jr)
- \#8925 `f628d9a` Display minimum ping in debug window (rebroad)
- \#8774 `3e942a7` Qt refactors to better abstract wallet access (luke-jr)
- \#8985 `7b1bfa3` Use pindexBestHeader instead of setBlockIndexCandidates for
NotifyHeaderTip() (jonasschnelli)
- \#8989 `d2143dc` Overhaul smart-fee slider, adjust default confirmation target
(jonasschnelli)
- \#9043 `273bde3` Return useful error message on ATMP failure (MarcoFalke)
- \#9088 `4e57824` Reduce ambiguity of warning message (rebroad)
- \#8874 `e984730` Multiple Selection for peer and ban tables (achow101)
- \#9145 `924745d` Make network disabled icon 50% opaque (MarcoFalke)
- \#9130 `ac489b2` Mention the new network toggle functionality in the tooltip
(paveljanik)
- \#9218 `4d955fc` Show progress overlay when clicking spinner icon (laanwj)
- \#9280 `e15660c` Show ModalOverlay by pressing the progress bar, allow hiding
(jonasschnelli)
- \#9296 `fde7d99` Fix missed change to WalletTx structure (morcos)
- \#9266 `2044e37` Bugfix: Qt/RPCConsole: Put column enum in the right places
(luke-jr)
- \#9255 `9851a84` layoutAboutToChange signal is called layoutAboutToBeChanged
(laanwj)
- \#9330 `47e6a19` Console: add security warning (jonasschnelli)
- \#9329 `db45ad8` Console: allow empty arguments (jonasschnelli)
- \#8877 `6dc4c43` Qt RPC console: history sensitive-data filter, and saving
input line when browsing history (luke-jr)
- \#9462 `649cf5f` Do not translate tilde character (MarcoFalke)
- \#9457 `123ea73` Select more files for translation (MarcoFalke)
- \#9413 `fd7d8c7` CoinControl: Allow non-wallet owned change addresses
(jonasschnelli)
- \#9461 `b250686` Improve progress display during headers-sync and peer-finding
(jonasschnelli)
- \#9588 `5086452` Use nPowTargetSpacing constant (MarcoFalke)
- \#9637 `d9e4d1d` Fix transaction details output-index to reflect vout index
(jonasschnelli)
- \#9718 `36f9d3a` Qt/Intro: Various fixes (luke-jr)
- \#9735 `ec66d06` devtools: Handle Qt formatting characters edge-case in
update-translations.py (laanwj)
- \#9755 `a441db0` Bugfix: Qt/Options: Restore persistent "restart required"
notice (luke-jr)
- \#9817 `7d75a5a` Fix segfault crash when shutdown the GUI in disablewallet mode
(jonasschnelli)
### Wallet
- \#8152 `b9c1cd8` Remove `CWalletDB*` parameter from CWallet::AddToWallet
(pstratem)
- \#8432 `c7e05b3` Make CWallet::fFileBacked private (pstratem)
- \#8445 `f916700` Move CWallet::setKeyPool to private section of CWallet
(pstratem)
- \#8564 `0168019` Remove unused code/conditions in ReadAtCursor (jonasschnelli)
- \#8601 `37ac678` Add option to opt into full-RBF when sending funds (rebase,
original by petertodd) (laanwj)
- \#8494 `a5b20ed` init, wallet: ParameterInteraction() iff wallet enabled
(MarcoFalke)
- \#8760 `02ac669` init: Get rid of some `ENABLE_WALLET` (MarcoFalke)
- \#8696 `a1f8d3e` Wallet: Remove last external reference to CWalletDB (pstratem)
- \#8768 `886e8c9` init: Get rid of fDisableWallet (MarcoFalke)
- \#8486 `ab0b411` Add high transaction fee warnings (MarcoFalke)
- \#8851 `940748b` Move key derivation logic from GenerateNewKey to
DeriveNewChildKey (pstratem)
- \#8287 `e10af96` Set fLimitFree = true (MarcoFalke)
- \#8928 `c587577` Fix init segfault where InitLoadWallet() calls ATMP before
genesis (TheBlueMatt)
- \#7551 `f2d7056` Add importmulti RPC call (pedrobranco)
- \#9016 `0dcb888` Return useful error message on ATMP failure (instagibbs)
- \#8753 `f8723d2` Locked memory manager (laanwj)
- \#8828 `a4fd8df` Move CWalletDB::ReorderTransactions to CWallet (pstratem)
- \#8977 `6a1343f` Refactor wallet/init interaction (Reaccept wtx, flush thread)
(jonasschnelli)
- \#9036 `ed0cc50` Change default confirm target from 2 to 6 (laanwj)
- \#9071 `d1871da` Declare wallet.h functions inline (sipa)
- \#9132 `f54e460` Make strWalletFile const (jonasschnelli)
- \#9141 `5ea5e04` Remove unnecessary calls to CheckFinalTx (jonasschnelli)
- \#9165 `c01f16a` SendMoney: use already-calculated balance (instagibbs)
- \#9311 `a336d13` Flush wallet after abandontransaction (morcos)
- \#8717 `38e4887` Addition of ImmatureCreditCached to MarkDirty()
(spencerlievens)
- \#9446 `510c0d9` SetMerkleBranch: remove unused code, remove cs\_main lock
requirement (jonasschnelli)
- \#8776 `2a524b8` Wallet refactoring leading up to multiwallet (luke-jr)
- \#9465 `a7d55c9` Do not perform ECDSA signing in the fee calculation inner loop
(gmaxwell)
- \#9404 `12e3112` Smarter coordination of change and fee in CreateTransaction
(morcos)
- \#9377 `fb75cd0` fundrawtransaction: Keep change-output keys by default, make
it optional (jonasschnelli)
- \#9578 `923dc44` Add missing mempool lock for CalculateMemPoolAncestors
(TheBlueMatt)
- \#9227 `02464da` Make nWalletDBUpdated atomic to avoid a potential race
(pstratem)
- \#9764 `f8af89a` Prevent "overrides a member function but is not marked
'override'" warnings (laanwj)
- \#9771 `e43a585` Add missing cs\_wallet lock that triggers new lock held
assertion (ryanofsky)
- \#9316 `3097ea4` Disable free transactions when relay is disabled (MarcoFalke)
- \#9615 `d2c9e4d` Wallet incremental fee (morcos)
- \#9760 `40c754c` Remove importmulti always-true check (ryanofsky)
### Tests and QA
- \#8270 `6e5e5ab` Tests: Use portable #! in python scripts (/usr/bin/env)
(ChoHag)
- \#8534,#8504 Remove java comparison tool (laanwj,MarcoFalke)
- \#8482 `740cff5` Use single cache dir for chains (MarcoFalke)
- \#8450 `21857d2` Replace `rpc_wallet_tests.cpp` with python RPC unit tests
(pstratem)
- \#8671 `ddc3080` Minimal fix to slow prevector tests as stopgap measure
(JeremyRubin)
- \#8680 `666eaf0` Address Travis spurious failures (theuni)
- \#8789 `e31a43c` pull-tester: Only print output when failed (MarcoFalke)
- \#8810 `14e8f99` tests: Add exception error message for JSONRPCException
(laanwj)
- \#8830 `ef0801b` test: Add option to run bitcoin-util-test.py manually
(jnewbery)
- \#8881 `e66cc1d` Add some verbose logging to bitcoin-util-test.py (jnewbery)
- \#8922 `0329511` Send segwit-encoded blocktxn messages in p2p-compactblocks
(TheBlueMatt)
- \#8873 `74dc388` Add microbenchmarks to profile more code paths (ryanofsky)
- \#9032 `6a8be7b` test: Add format-dependent comparison to bctest (laanwj)
- \#9023 `774db92` Add logging to bitcoin-util-test.py (jnewbery)
- \#9065 `c9bdf9a` Merge `doc/unit-tests.md` into `src/test/README.md` (laanwj)
- \#9069 `ed64bce` Clean up bctest.py and bitcoin-util-test.py (jnewbery)
- \#9095 `b8f43e3` test: Fix test\_random includes (MarcoFalke)
- \#8894 `faec09b` Testing: Include fRelay in mininode version messages
(jnewbery)
- \#9097 `e536499` Rework `sync_*` and preciousblock.py (MarcoFalke)
- \#9049 `71bc39e` Remove duplicatable duplicate-input check from
CheckTransaction (TheBlueMatt)
- \#9136 `b422913` sync\_blocks cleanup (ryanofsky)
- \#9151 `4333b1c` proxy\_test: Calculate hardcoded port numbers (MarcoFalke)
- \#9206 `e662d28` Make test constant consistent with consensus.h (btcdrak)
- \#9139 `0de7fd3` Change sync\_blocks to pick smarter maxheight (on top of
#9196) (ryanofsky)
- \#9100 `97ec6e5` tx\_valid: re-order inputs to how they are encoded (dcousens)
- \#9202 `e56cf67` bench: Add support for measuring CPU cycles (laanwj)
- \#9223 `5412c08` unification of Bloom filter representation (s-matthew-english)
- \#9257 `d7ba4a2` Dump debug logs on travis failures (sdaftuar)
- \#9221 `9e4bb31` Get rid of duplicate code (MarcoFalke)
- \#9274 `919db03` Use cached utxo set to fix performance regression (MarcoFalke)
- \#9276 `ea33f19` Some minor testing cleanups (morcos)
- \#9291 `8601784` Remove mapOrphanTransactionsByPrev from DoS\_tests (sipa)
- \#9309 `76fcd9d` Wallet needs to stay unlocked for whole test (morcos)
- \#9172 `5bc209c` Resurrect pstratem's "Simple fuzzing framework" (laanwj)
- \#9331 `c6fd923` Add test for rescan feature of wallet key import RPCs
(ryanofsky)
- \#9354 `b416095` Make fuzzer actually test CTxOutCompressor (sipa)
- \#9390,#9416 travis: make distdir (MarcoFalke)
- \#9308 `0698639` test: Add CCoinsViewCache Access/Modify/Write tests
(ryanofsky)
- \#9406 `0f921e6` Re-enable a blank v1 Tx JSON test (droark)
- \#9435 `dbc8a8c` Removed unused variable in test, fixing warning (ryanofsky)
- \#9436 `dce853e` test: Include tx data in `EXTRA_DIST` (MarcoFalke)
- \#9525 `02e5308` test: Include tx data in `EXTRA_DIST` (MarcoFalke)
- \#9498 `054d664` Basic CCheckQueue Benchmarks (JeremyRubin)
- \#9554 `0b96abc` test: Avoid potential NULL pointer dereference in
`addrman_tests.cpp` (practicalswift)
- \#9628 `f895023` Increase a sync\_blocks timeout in pruning.py (sdaftuar)
- \#9638 `a7ea2f8` Actually test assertions in pruning.py (MarcoFalke)
- \#9647 `e99f0d7` Skip RAII event tests if libevent is built without
`event_set_mem_functions` (luke-jr)
- \#9691 `fc67cd2` Init ECC context for `test_bitcoin_fuzzy` (gmaxwell)
- \#9712 `d304fef` bench: Fix initialization order in registration (laanwj)
- \#9707 `b860915` Fix RPC failure testing (jnewbery)
- \#9269 `43e8150` Align struct COrphan definition (sipa)
- \#9820 `599c69a` Fix pruning test broken by 2 hour manual prune window
(ryanofsky)
- \#9824 `260c71c` qa: Check return code when stopping nodes (MarcoFalke)
- \#9875 `50953c2` tests: Fix dangling pwalletMain pointer in wallet tests
(laanwj)
- \#9839 `eddaa6b` \[qa] Make import-rescan.py watchonly check reliable
(ryanofsky)
### Documentation
- \#8332 `806b9e7` Clarify witness branches in transaction.h serialization
(dcousens)
- \#8935 `0306978` Documentation: Building on Windows with WSL (pooleja)
- \#9144 `c98f6b3` Correct waitforblockheight example help text (fanquake)
- \#9407 `041331e` Added missing colons in when running help command (anditto)
- \#9378 `870cd2b` Add documentation for CWalletTx::fFromMe member (ryanofsky)
- \#9297 `0b73807` Various RPC help outputs updated (Mirobit)
- \#9613 `07421cf` Clarify getbalance help string to explain interaction with
bumpfee (ryanofsky)
- \#9663 `e30d928` Clarify listunspent amount description (instagibbs)
- \#9396 `d65a13b` Updated listsinceblock rpc documentation (accraze)
- \#8747 `ce43630` rpc: Fix transaction size comments and RPC help text
(jnewbery)
- \#8058 `bbd9740` Doc: Add issue template (AmirAbrams)
- \#8567 `85d4e21` Add default port numbers to REST doc (djpnewton)
- \#8624 `89de153` build: Mention curl (MarcoFalke)
- \#8786 `9da7366` Mandatory copyright agreement (achow101)
- \#8823 `7b05af6` Add privacy recommendation when running hidden service
(laanwj)
- \#9433 `caa2f10` Update the Windows build notes (droark)
- \#8879 `f928050` Rework docs (MarcoFalke)
- \#8887 `61d191f` Improve GitHub issue template (fanquake)
- \#8787 `279bbad` Add missing autogen to example builds (AmirAbrams)
- \#8892 `d270c30` Add build instructions for FreeBSD (laanwj)
- \#8890 `c71a654` Update Doxygen configuration file (fanquake)
- \#9207 `fa1f944` Move comments above bash command in build-unix (AmirAbrams)
- \#9219 `c4522e7` Improve windows build instructions using Linux subsystem
(laanwj)
- \#8954 `932d02a` contrib: Add README for pgp keys (MarcoFalke)
- \#9093 `2fae5b9` release-process: Mention GitHub release and archived release
notes (MarcoFalke)
- \#8743 `bae178f` Remove old manpages from contrib/debian in favour of doc/man
(fanquake)
- \#9550 `4105cb6` Trim down the XP notice and say more about what we support
(gmaxwell)
- \#9246 `9851498` Developer docs about existing subtrees (gmaxwell)
- \#9401 `c2ea1e6` Make rpcauth help message clearer, add example in example
.conf (instagibbs)
- \#9022,#9033 Document dropping OS X 10.7 support (fanquake, MarcoFalke)
- \#8771 `bc9e3ab` contributing: Mention not to open several pulls (luke-jr)
- \#8852 `7b784cc` Mention Gitian building script in doc (Laudaa) (laanwj)
- \#8915 `03dd707` Add copyright/patent issues to possible NACK reasons
(petertodd)
- \#8965 `23e03f8` Mention that PPA doesn't support Debian (anduck)
- \#9115 `bfc7aad` Mention reporting security issues responsibly (paveljanik)
- \#9840 `08e0690` Update sendfrom RPC help to correct coin selection
misconception (ryanofsky)
- \#9865 `289204f` Change bitcoin address in RPC help message (marijnfs)
### Miscellaneous
- \#8274 `7a2d402` util: Update tinyformat (laanwj)
- \#8291 `5cac8b1` util: CopyrightHolders: Check for untranslated substitution
(MarcoFalke)
- \#8557 `44691f3` contrib: Rework verifybinaries (MarcoFalke)
- \#8621 `e8ed6eb` contrib: python: Don't use shell=True (MarcoFalke)
- \#8813 `fb24d7e` bitcoind: Daemonize using daemon(3) (laanwj)
- \#9004 `67728a3` Clarify `listenonion` (unsystemizer)
- \#8674 `bae81b8` tools for analyzing, updating and adding copyright headers in
source files (isle2983)
- \#8976 `8c6218a` libconsensus: Add input validation of flags (laanwj)
- \#9112 `46027e8` Avoid ugly exception in log on unknown inv type (laanwj)
- \#8837 `2108911` Allow bitcoin-tx to parse partial transactions (jnewbery)
- \#9204 `74ced54` Clarify CreateTransaction error messages (instagibbs)
- \#9265 `31bcc66` bitcoin-cli: Make error message less confusing (laanwj)
- \#9303 `72bf1b3` Update comments in ctaes (sipa)
- \#9417 `c4b7d4f` Do not evaluate hidden LogPrint arguments (sipa)
- \#9506 `593a00c` RFC: Improve style for if indentation (sipa)
- \#8883 `d5d4ad8` Add all standard TXO types to bitcoin-tx (jnewbery)
- \#9531 `23281a4` Release notes for estimation changes (morcos)
- \#9486 `f62bc10` Make peer=%d log prints consistent (TheBlueMatt)
- \#9552 `41cb05c` Add IPv6 support to qos.sh (jamesmacwhite)
- \#9542 `e9e7993` Docs: Update CONTRIBUTING.md (jnewbery)
- \#9649 `53ab12d` Remove unused clang format dev script (MarcoFalke)
- \#9625 `77bd8c4` Increase minimum debug.log size to 10MB after shrink (morcos)
- \#9070 `7b22e50` Lockedpool fixes (kazcw)
- \#8779 `7008e28` contrib: Delete spendfrom (MarcoFalke)
- \#9587,#8793,#9496,#8191,#8109,#8655,#8472,#8677,#8981,#9124 Avoid shadowing
of variables (paveljanik)
- \#9063 `f2a6e82` Use deprecated `MAP_ANON` if `MAP_ANONYMOUS` is not defined
(paveljanik)
- \#9060 `1107653` Fix bloom filter init to isEmpty = true (robmcl4)
- \#8613 `613bda4` LevelDB 1.19 (sipa)
- \#9225 `5488514` Fix some benign races (TheBlueMatt)
- \#8736 `5fa7b07` base58: Improve DecodeBase58 performance (wjx)
- \#9039 `e81df49` Various serialization simplifcations and optimizations (sipa)
- \#9010 `a143b88` Split up AppInit2 into multiple phases, daemonize after
datadir lock errors (laanwj)
- \#9230 `c79e52a` Fix some benign races in timestamp logging (TheBlueMatt)
- \#9183,#9260 Mrs Peacock in The Library with The Candlestick (killed
main.{h,cpp}) (TheBlueMatt)
- \#9236 `7f72568` Fix races for strMiscWarning and `fLargeWork*Found`, make QT
runawayException use GetWarnings (gmaxwell)
- \#9243 `7aa7004` Clean up mapArgs and mapMultiArgs Usage (TheBlueMatt)
- \#9387 `cfe41d7` RAII of libevent stuff using unique ptrs with deleters
(kallewoof)
- \#9472 `fac0f30` Disentangle progress estimation from checkpoints and update it
(sipa)
- \#9512 `6012967` Fix various things -fsanitize complains about (sipa)
- \#9373,#9580 Various linearization script issues (droark)
- \#9674 `dd163f5` Lock debugging: Always enforce strict lock ordering (try or
not) (TheBlueMatt)
- \#8453,#9334 Update to latest libsecp256k1 (laanwj,sipa)
- \#9656 `7c93952` Check verify-commits on pushes to master (TheBlueMatt)
- \#9679 `a351162` Access WorkQueue::running only within the cs lock
(TheBlueMatt)
- \#9777 `8dee822` Handle unusual maxsigcachesize gracefully (jnewbery)
- \#8863,#8807 univalue: Pull subtree (MarcoFalke)
- \#9798 `e22c067` Fix Issue #9775 (Check returned value of fopen) (kirit93)
- \#9856 `69832aa` Terminate immediately when allocation fails (theuni)
## Credits
Thanks to everyone who directly contributed to this release:
- accraze
- adlawren
- Alex Morcos
- Alexey Vesnin
- Amir Abrams
- Anders Øyvind Urke-Sætre
- Anditto Heristyo
- Andrew Chow
- anduck
- Anthony Towns
- Brian Deery
- BtcDrak
- Chris Moore
- Chris Stewart
- Christian Barcenas
- Christian Decker
- Cory Fields
- crowning-
- CryptAxe
- CryptoVote
- Dagur Valberg Johannsson
- Daniel Cousens
- Daniel Kraft
- Derek Miller
- djpnewton
- Don Patterson
- Doug
- Douglas Roark
- Ethan Heilman
- fsb4000
- Gaurav Rana
- Geoffrey Tsui
- Greg Walker
- Gregory Maxwell
- Gregory Sanders
- Hampus Sjöberg
- isle2983
- Ivo van der Sangen
- James White
- Jameson Lopp
- Jeremy Rubin
- Jiaxing Wang
- jnewbery
- John Newbery
- Johnson Lau
- Jon Lund Steffensen
- Jonas Schnelli
- jonnynewbs
- Jorge Timón
- Justin Camarena
- Karl-Johan Alm
- Kaz Wesley
- kirit93
- Koki Takahashi
- Lauda
- leijurv
- lizhi
- Luke Dashjr
- maiiz
- MarcoFalke
- Marijn Stollenga
- Marty Jones
- Masahiko Hyuga
- Matt Corallo
- Matthew King
- matthias
- Micha
- Michael Ford
- Michael Rotarius
- Mitchell Cash
- mrbandrews
- mruddy
- Nicolas DORIER
- nomnombtc
- Patrick Strateman
- Pavel Janík
- Pedro Branco
- Peter Todd
- Pieter Wuille
- poole_party
- practicalswift
- R E Broadley
- randy-waterhouse
- Richard Kiss
- Robert McLaughlin
- rodasmith
- Russell Yanofsky
- S. Matthew English
- Sev
- Spencer Lievens
- Stanislas Marion
- Steven
- Suhas Daftuar
- Thomas Snider
- UdjinM6
- unsystemizer
- whythat
- Will Binns
- Wladimir J. van der Laan
- wodry
- Zak Wilcox
As well as everyone that helped translating on
[Transifex](https://www.transifex.com/projects/p/bitcoin/).

View file

@ -1,157 +0,0 @@
---
# This file is licensed under the MIT License (MIT) available on
# http://opensource.org/licenses/MIT.
type: posts
layout: post
category: blog
title: "Bitcoin Core Version 0.14.1 Released"
permalink: /en/posts/bitcoin-core-version-0-14-1-released.html
date: 2017-04-22
author: |
<a href="https://github.com/wbnns">Will Binns</a>
---
{:.center}
![Bitcoin Core Version 0.14.1](/img/blog/free/bitcoin-core-0141.png)
[Bitcoin Core version 0.14.1 is now available](https://bitcoin.org/en/download).
This is a new minor version release, including various bugfixes and performance improvements, as well as updated translations.
Please report bugs using the [issue tracker on GitHub](https://github.com/bitcoin/bitcoin/issues).
[Subscribe here](https://bitcoincore.org/en/list/announcements/join/) to receive
security and update notifications.
## Compatibility
Bitcoin Core is extensively tested on multiple operating systems using
the Linux kernel, macOS 10.8+, and Windows Vista and later.
Microsoft ended support for Windows XP on [April 8th,
2014](https://www.microsoft.com/en-us/WindowsForBusiness/end-of-xp-support),
No attempt is made to prevent installing or running the software on Windows XP,
you can still do so at your own risk but be aware that there are known
instabilities and issues. Please do not report issues about Windows XP to the
[issue tracker](https://github.com/bitcoin/bitcoin/issues).
Bitcoin Core should also work on most other Unix-like systems but is not
frequently tested on them.
## Notable changes
### RPC changes
- The first positional argument of `createrawtransaction` was renamed from
`transactions` to `inputs`.
- The argument of `disconnectnode` was renamed from `node` to `address`.
These interface changes break compatibility with 0.14.0, when the named
arguments functionality, introduced in 0.14.0, is used. Client software
using these calls with named arguments needs to be updated.
### Mining
In previous versions, getblocktemplate required segwit support from downstream
clients/miners once the feature activated on the network. In this version, it
now supports non-segwit clients even after activation, by removing all segwit
transactions from the returned block template. This allows non-segwit miners to
continue functioning correctly even after segwit has activated.
Due to the limitations in previous versions, getblocktemplate also recommended
non-segwit clients to not signal for the segwit version-bit. Since this is no
longer an issue, getblocktemplate now always recommends signalling segwit for
all miners. This is safe because ability to enforce the rule is the only
required criteria for safe activation, not actually producing segwit-enabled
blocks.
### UTXO memory accounting
Memory usage for the UTXO cache is being calculated more accurately, so that
the configured limit (`-dbcache`) will be respected when memory usage peaks
during cache flushes. The memory accounting in prior releases is estimated to
only account for half the actual peak utilization.
The default `-dbcache` has also been changed in this release to 450MiB. Users
who currently set `-dbcache` to a high value (e.g. to keep the UTXO more fully
cached in memory) should consider increasing this setting in order to achieve
the same cache performance as prior releases. Users on low-memory systems
(such as systems with 1GB or less) should consider specifying a lower value for
this parameter.
Additional information relating to running on low-memory systems can be found
here:
[reducing-bitcoind-memory-usage.md](https://gist.github.com/laanwj/efe29c7661ce9b6620a7).
## 0.14.1 Change log
Detailed release notes follow. This overview includes changes that affect
behavior, not code moves, refactors and string updates. For convenience in locating
the code changes and accompanying discussion, both the pull request and
git merge commit are mentioned.
### RPC and other APIs
- \#10084 `142fbb2` Rename first named arg of createrawtransaction (MarcoFalke)
- \#10139 `f15268d` Remove auth cookie on shutdown (practicalswift)
- \#10146 `2fea10a` Better error handling for submitblock (rawodb, gmaxwell)
- \#10144 `d947afc` Prioritisetransaction wasn't always updating ancestor fee (sdaftuar)
- \#10204 `3c79602` Rename disconnectnode argument (jnewbery)
### Block and transaction handling
- \#10126 `0b5e162` Compensate for memory peak at flush time (sipa)
- \#9912 `fc3d7db` Optimize GetWitnessHash() for non-segwit transactions (sdaftuar)
- \#10133 `ab864d3` Clean up calculations of pcoinsTip memory usage (morcos)
### P2P protocol and network code
- \#9953/\#10013 `d2548a4` Fix shutdown hang with >= 8 -addnodes set (TheBlueMatt)
- \#10176 `30fa231` net: gracefully handle NodeId wrapping (theuni)
### Build system
- \#9973 `e9611d1` depends: fix zlib build on osx (theuni)
### GUI
- \#10060 `ddc2dd1` Ensure an item exists on the rpcconsole stack before adding (achow101)
### Mining
- \#9955/#10006 `569596c` Don't require segwit in getblocktemplate for segwit signalling or mining (sdaftuar)
- \#9959/#10127 `b5c3440` Prevent slowdown in CreateNewBlock on large mempools (sdaftuar)
### Tests and QA
- \#10157 `55f641c` Fix the `mempool_packages.py` test (sdaftuar)
### Miscellaneous
- \#10037 `4d8e660` Trivial: Fix typo in help getrawtransaction RPC (keystrike)
- \#10120 `e4c9a90` util: Work around (virtual) memory exhaustion on 32-bit w/ glibc (laanwj)
- \#10130 `ecc5232` bitcoin-tx input verification (awemany, jnewbery)
## Credits
Thanks to everyone who directly contributed to this release:
- Alex Morcos
- Andrew Chow
- Awemany
- Cory Fields
- Gregory Maxwell
- James Evans
- John Newbery
- MarcoFalke
- Matt Corallo
- Pieter Wuille
- practicalswift
- rawodb
- Suhas Daftuar
- Wladimir J. van der Laan
As well as everyone that helped translating on
[Transifex](https://www.transifex.com/projects/p/bitcoin/).

View file

@ -1,117 +0,0 @@
---
# This file is licensed under the MIT License (MIT) available on
# http://opensource.org/licenses/MIT.
type: posts
layout: post
category: blog
title: "Bitcoin Core Version 0.14.2 Released"
permalink: /en/posts/bitcoin-core-version-0-14-2-released.html
date: 2017-06-17
author: |
<a href="https://github.com/wbnns">Will Binns</a>
---
{:.center}
![Bitcoin Core Version 0.14.2](/img/blog/free/bitcoin-core-0142.png)
[Bitcoin Core version 0.14.2 is now available](https://bitcoin.org/en/download).
This is a new minor version release, including various bugfixes and
performance improvements, as well as updated translations.
Please report bugs using the [issue tracker on GitHub](https://github.com/bitcoin/bitcoin/issues).
[Subscribe here](https://bitcoincore.org/en/list/announcements/join/) to receive
security and update notifications.
## Compatibility
Bitcoin Core is extensively tested on multiple operating systems using
the Linux kernel, macOS 10.8+, and Windows Vista and later.
Microsoft ended support for Windows XP on [April 8th,
2014](https://www.microsoft.com/en-us/WindowsForBusiness/end-of-xp-support),
No attempt is made to prevent installing or running the software on Windows XP,
you can still do so at your own risk but be aware that there are known
instabilities and issues. Please do not report issues about Windows XP to the
[issue tracker](https://github.com/bitcoin/bitcoin/issues).
Bitcoin Core should also work on most other Unix-like systems but is not
frequently tested on them.
## Notable changes
### miniupnp CVE-2017-8798
Bundled miniupnpc was updated to 2.0.20170509. This fixes an integer signedness error
(present in MiniUPnPc v1.4.20101221 through v2.0) that allows remote attackers
(within the LAN) to cause a denial of service or possibly have unspecified
other impact.
This only affects users that have explicitly enabled UPnP through the GUI
setting or through the `-upnp` option, as since the last UPnP vulnerability
(in Bitcoin Core 0.10.3) it has been disabled by default.
If you use this option, it is recommended to upgrade to this version as soon as
possible.
## Known Bugs
Since 0.14.0 the approximate transaction fee shown in Bitcoin-Qt when using coin
control and smart fee estimation does not reflect any change in target from the
smart fee slider. It will only present an approximate fee calculated using the
default target. The fee calculated using the correct target is still applied to
the transaction and shown in the final send confirmation dialog.
## 0.14.2 Change log
Detailed release notes follow. This overview includes changes that affect
behavior, not code moves, refactors and string updates. For convenience in locating
the code changes and accompanying discussion, both the pull request and
git merge commit are mentioned.
### RPC and other APIs
- \#10410 `321419b` Fix importwallet edge case rescan bug (ryanofsky)
### P2P protocol and network code
- \#10424 `37a8fc5` Populate services in GetLocalAddress (morcos)
- \#10441 `9e3ad50` Only enforce expected services for half of outgoing connections (theuni)
### Build system
- \#10414 `ffb0c4b` miniupnpc 2.0.20170509 (fanquake)
- \#10228 `ae479bc` Regenerate bitcoin-config.h as necessary (theuni)
### Miscellaneous
- \#10245 `44a17f2` Minor fix in build documentation for FreeBSD 11 (shigeya)
- \#10215 `0aee4a1` Check interruptNet during dnsseed lookups (TheBlueMatt)
### GUI
- \#10231 `1e936d7` Reduce a significant cs_main lock freeze (jonasschnelli)
### Wallet
- \#10294 `1847642` Unset change position when there is no change (instagibbs)
## Credits
Thanks to everyone who directly contributed to this release:
- Alex Morcos
- Cory Fields
- fanquake
- Gregory Sanders
- Jonas Schnelli
- Matt Corallo
- Russell Yanofsky
- Shigeya Suzuki
- Wladimir J. van der Laan
As well as everyone that helped translating on
[Transifex](https://www.transifex.com/projects/p/bitcoin/).

View file

@ -1,29 +0,0 @@
---
# This file is licensed under the MIT License (MIT) available on
# http://opensource.org/licenses/MIT.
layout: base
lang: en
title: Bitcoin.org Site Blog - Bitcoin
id: site-blog
---
<link rel="alternate" type="application/atom+xml" href="/en/rss/blog.xml" title="Bitcoin.org Site Blog">
<div class="home">
<h1 class="page-heading">Bitcoin.org Site Blog</h1>
<p class="summary">Discover what's new on Bitcoin.org or <a type="application/atom+xml" href="/en/rss/blog.xml">subscribe to the RSS feed <img src="/img/icons/icon_rss.svg" alt="rss" class="rssicon"></a></p>
<ul class="post-list">
{% for post in site.posts %}
<li>
<a class="post-link" href="{{ post.url | remove: '.html' }}">{{ post.title }}</a>
-
<span class="post-meta">{{ post.date | date: "%b %-d, %Y" }}</span>
</li>
{% endfor %}
</ul>
</div>

View file

@ -1,34 +0,0 @@
---
# This file is licensed under the MIT License (MIT) available on
# http://opensource.org/licenses/MIT.
layout: null
lang: en
---
<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Bitcoin.org Site Blog</title>
<description>News about Bitcoin.org</description>
<link>{{ site.url }}{{ site.baseurl }}/</link>
<atom:link href="{{ "/en/rss/blog.xml" | prepend: site.baseurl | prepend: site.url }}" rel="self" type="application/rss+xml"/>
<pubDate>{{ site.time | date_to_rfc822 }}</pubDate>
<lastBuildDate>{{ site.time | date_to_rfc822 }}</lastBuildDate>
<generator>Jekyll v{{ jekyll.version }}</generator>
{% for post in site.posts limit:5 %}
<item>
<title>{{ post.title | xml_escape }}</title>
<description>{{ post.content | xml_escape }}</description>
<pubDate>{{ post.date | date_to_rfc822 }}</pubDate>
<link>{{ post.url | remove: '.html' | prepend: site.baseurl | prepend: site.url }}</link>
<guid isPermaLink="true">{{ post.url | remove: '.html' | prepend: site.baseurl | prepend: site.url }}</guid>
{% for tag in post.tags %}
<category>{{ tag | xml_escape }}</category>
{% endfor %}
{% for cat in post.categories %}
<category>{{ cat | xml_escape }}</category>
{% endfor %}
</item>
{% endfor %}
</channel>
</rss>