Skip to content
Bitcoin Knots enhanced Bitcoin node/wallet software
Branch: 0.18.x-knots
Clone or download
Pull request Compare This branch is 494 commits ahead, 1043 commits behind bitcoin:master.
Latest commit 5e1c2d1 May 2, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Knots branding for README and GitHub issue templates Apr 26, 2019
.travis Travis: Include dependencies for building icons Apr 26, 2019
.tx qt: Pre-0.18 split-off translations update Feb 4, 2019
build-aux/m4 Merge 14137 via win_taskbar_progress-0.18+knots May 2, 2019
build_msvc Merge knots_branding-0.18 May 2, 2019
contrib Merge knots_branding-0.18 May 2, 2019
depends Merge 14137 via win_taskbar_progress-0.18+knots May 2, 2019
doc Update manpages May 2, 2019
share Merge knots_branding-0.18 May 2, 2019
src Update translations May 2, 2019
test Merge knots_branding-0.18 May 2, 2019
.appveyor.yml appveyor: Don't build debug libraries instead of "build and delete" Feb 28, 2019
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore gitignore: add *.plist (clang-check) Apr 16, 2019
.python-version [test] Travis: enforce Python 3.4 support in functional tests Dec 12, 2018
.travis.yml Travis: Include dependencies for building icons Apr 26, 2019 Knots branding for README and GitHub issue templates Apr 26, 2019
COPYING [Trivial] Update license year range to 2019 Dec 31, 2018 Knots branding for README and GitHub issue templates Apr 26, 2019 nsis-header.bmp: Generate from SVG Apr 26, 2019 Knots branding for README and GitHub issue templates Apr 26, 2019 Add "export LC_ALL=C" to all shell scripts Jun 14, 2018 Merge knots_branding-0.18 May 2, 2019 Unify package name to as few places as possible without major changes Dec 14, 2015

Bitcoin Knots

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 Knots 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 Knots software, see or read the original whitepaper.


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

Development Process

Development generally takes place as part of Bitcoin Core, and is merged into Knots for each release.

Even if your pull request to Core is closed, or if your feature is not suitable for Core (eg, because it builds on a features not supported in Core; relies on centralised services; etc), it may still be eligible for inclusion in Bitcoin Knots. In this case, a pull request may be opened on the Knots GitHub for review and consideration. When accepted, you are expected to maintain the submitted branch in your own repository, and it will be automatically merged into new releases of Knots.

The developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.

Developer IRC can be found on Freenode at #bitcoin-dev.


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.

You can’t perform that action at this time.