Bitcoin Core integration/staging tree
Clone or download
MarcoFalke Merge #13152: [rpc] Add getnodeaddresses RPC command
a2eb6f5 [rpc] Add getnodeaddresses RPC command (chris-belcher)

Pull request description:

  Implements issue #9463

  New getnodeaddresses call gives access via RPC to the peers known by the node. It may be useful for bitcoin wallets to broadcast their transactions over tor for improved privacy without using the centralized DNS seeds. getnodeaddresses is very similar to the getaddr p2p method.

  Please advise me on the best approach for writing an automated test. By my reading the getaddr p2p method also isn't really tested.

Tree-SHA512: ad03abf518847476495b76a2f5394b8030aa86654429167fa618e21460abb505c10ef9817ec1b80472320d41d0aff5dc94a8efce023aaaaf5e81386aa92b852b
Latest commit d262789 Sep 19, 2018
Failed to load latest commit information.
.github Make default issue text all comments to make issues more readable Nov 16, 2017
.travis travis: Run feature_dbcrash functional tests in cron job Sep 16, 2018
.tx tx: Update transifex slug 016x→017x Aug 2, 2018
build-aux/m4 Merge #13095: build: update ax_boost_chrono/unit_test_framework Jul 26, 2018
build_msvc appveyor: Use clcache to speed up build Sep 3, 2018
contrib Merge #13954: Warn (don't fail!) on spelling errors. Fix typos report… Sep 5, 2018
depends [depends, zmq, doc] upgrade zeromq to 4.2.5 and avoid deprecated zero… Sep 11, 2018
doc Merge #13152: [rpc] Add getnodeaddresses RPC command Sep 18, 2018
share Merge #14018: Bugfix: NSIS: Exclude Makefile* from docs Aug 22, 2018
src Merge #13152: [rpc] Add getnodeaddresses RPC command Sep 18, 2018
test Merge #13152: [rpc] Add getnodeaddresses RPC command Sep 18, 2018
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore [build] .gitignore: add QT Creator artifacts Dec 22, 2017
.travis.yml travis: add CXXFLAGS=-Wnopsabi at ARM job Aug 27, 2018 doc: add note to contributor docs about warranted PR's Jul 30, 2018
COPYING [Trivial] Update license year range to 2018 Dec 31, 2017 Update INSTALL landing redirection notice for build instructions. Oct 5, 2016 contrib: Remove debian and rpm subfolders Jul 30, 2018 doc: Adjust links Jul 22, 2018
appveyor.yml appveyor: Use clcache to speed up build Sep 3, 2018 Add "export LC_ALL=C" to all shell scripts Jun 14, 2018 Merge #14127: build: avoid getifaddrs when unavailable Sep 10, 2018 Unify package name to as few places as possible without major changes Dec 14, 2015

Bitcoin Core integration/staging tree

Build Status

What is Bitcoin?

Bitcoin is an experimental digital currency that enables instant payments to anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Bitcoin Core is the name of open source software which enables the use of this currency.

For more information, as well as an immediately useable, binary version of the Bitcoin Core software, see, or read the original whitepaper.


Bitcoin Core is released under the terms of the MIT license. See COPYING for more information or see

Development Process

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of Bitcoin Core.

The contribution workflow is described in


Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.

Automated Testing

Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code. Unit tests can be compiled and run (assuming they weren't disabled in configure) with: make check. Further details on running and extending unit tests can be found in /src/test/

There are also regression and integration tests, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: test/functional/

The Travis CI system makes sure that every pull request is built for Windows, Linux, and macOS, and that unit/sanity tests are run automatically.

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.


Changes to translations as well as new translations can be submitted to Bitcoin Core's Transifex page.

Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.

Translators should also subscribe to the mailing list.