Neobytes - Reinventing Cryptocurrency https://neobytes.network/
Go to file
Wladimir J. van der Laan f297042cae
Merge pull request #6637
95acf3c remove $(@F) and subdirs from univalue make (Jonas Schnelli)
9623e93 [Univalue] add univalue over subtree (Jonas Schnelli)
2f9f082 Squashed 'src/univalue/' content from commit 87d9045 (Jonas Schnelli)
0917306 remove univalue, prepare for subtree (Jonas Schnelli)
2015-10-01 16:36:15 +02:00
.tx Change transifex slug to translation-011x 2015-05-01 14:25:02 +02:00
build-aux/m4 Squashed 'src/univalue/' content from commit 87d9045 2015-10-01 10:37:19 +02:00
contrib Fix debian/copyright list to be non-comma-separated. 2015-09-25 16:00:07 -07:00
depends Merge pull request #6619 2015-09-25 16:29:24 +02:00
doc Merge pull request #6731 2015-10-01 06:02:14 -04:00
qa Merge pull request #6686 2015-10-01 16:22:26 +02:00
share [trivial] Remove obsolete pixmaps 2015-09-13 17:57:25 +02:00
src Merge pull request #6637 2015-10-01 16:36:15 +02:00
.gitattributes Separate protocol versioning from clientversion 2014-10-29 00:24:40 -04:00
.gitignore Squashed 'src/univalue/' content from commit 87d9045 2015-10-01 10:37:19 +02:00
.travis.yml travis: install a recent libzmq and pyzmq for tests 2015-10-01 15:40:57 +02:00
autogen.sh Squashed 'src/univalue/' content from commit 87d9045 2015-10-01 10:37:19 +02:00
configure.ac [Univalue] add univalue over subtree 2015-10-01 10:49:57 +02:00
CONTRIBUTING.md Add PR title prefix for trivial changes [skip ci] 2015-09-30 08:44:51 +02:00
COPYING Squashed 'src/univalue/' content from commit 87d9045 2015-10-01 10:37:19 +02:00
INSTALL Prettify some /Contrib READMEs 2013-10-21 20:07:31 -04:00
libbitcoinconsensus.pc.in libbitcoinconsensus: Add pkg-config support 2014-11-20 21:23:34 +00:00
Makefile.am Squashed 'src/univalue/' content from commit 87d9045 2015-10-01 10:37:19 +02:00
README.md doc: Change #bitcoin-dev IRC channel to #bitcoin-core-dev 2015-09-30 17:09:35 +02:00

Bitcoin Core integration/staging tree

Build Status

https://www.bitcoin.org

What is Bitcoin?

Bitcoin is an experimental new 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://www.bitcoin.org/en/download.

License

Bitcoin Core is released under the terms of the MIT license. See COPYING for more information or see http://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.

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 with: qa/pull-tester/rpc-tests.sh

Every pull request is built for both Windows and Linux on a dedicated server, and unit and sanity tests are automatically run. The binaries produced may be used for manual QA testing — a link to them will appear in a comment on the pull request posted by BitcoinPullTester. See https://github.com/TheBlueMatt/test-scripts for the build/test scripts.

Manual Quality Assurance (QA) Testing

Large changes should have a test plan, and should be tested by somebody other than the developer who wrote the code. See https://github.com/bitcoin/QA/ for how to create a test plan.

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.