Kevacoin source tree
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Pieter Wuille 5b2ea29cf4
Merge #8594: Do not add random inbound peers to addrman.
8 years ago
.github Adds issue template. [skip ci] 8 years ago
.tx tx: change slug to `bitcoin.qt-translation-013x` 8 years ago
build-aux/m4 build: Fix Qt5PlatformSupport check without pkg-config 8 years ago
contrib Merge #8557: [contrib] Rework verifybinaries 8 years ago
depends Remove unused Qt 4.6 patch. 8 years ago
doc Make the dummy argument to getaddednodeinfo optional 8 years ago
qa rest.cpp: change HTTP_INTERNAL_SERVER_ERROR to HTTP_BAD_REQUEST 8 years ago
share Merge #8270: Tests: Use portable #! in python scripts (/usr/bin/env) 8 years ago
src Merge #8594: Do not add random inbound peers to addrman. 8 years ago
.gitattributes Separate protocol versioning from clientversion 10 years ago
.gitignore [qa] Use single cache dir for chains 8 years ago
.travis.yml [travis] Drop java 8 years ago
CONTRIBUTING.md contributing.md: Fix formatting 9 years ago
COPYING Update license year range to 2016 9 years ago
INSTALL Prettify some /Contrib READMEs 11 years ago
Makefile.am test: Remove java comparison tool 8 years ago
README.md readme: Omit phrasing; 'new' 9 years ago
autogen.sh autogen.sh: warn about needing autoconf if autoreconf is not found 9 years ago
configure.ac build: Updates for OpenBSD 8 years ago
libbitcoinconsensus.pc.in Unify package name to as few places as possible without major changes 9 years ago

README.md

Bitcoin Core integration/staging tree

Build Status

https://bitcoincore.org

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 https://bitcoin.org/en/download, or read the original whitepaper.

License

Bitcoin Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

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 CONTRIBUTING.md.

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-core-dev.

Testing

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

There are also regression and integration tests of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.py

The Travis CI system makes sure that every pull request is built for Windows, Linux, and OS X, 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.

Translations

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.