No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
Pull request Compare This branch is 8 commits ahead of wmikrut:master.
Latest commit 73bc565 Sep 4, 2017
Failed to load latest commit information.
.tx C-Bit 1.0 May 23, 2017
build-aux/m4 C-Bit 1.0 May 23, 2017
contrib C-Bit 1.0 May 23, 2017
depends C-Bit 1.0 May 23, 2017
doc C-Bit 1.0 May 23, 2017
qa C-Bit 1.0 May 23, 2017
share fixed output files May 24, 2017
src Working IBD Sep 4, 2017
.gitattributes C-Bit 1.0 May 23, 2017
.gitignore C-Bit 1.0 May 23, 2017
.travis.yml C-Bit 1.0 May 23, 2017 C-Bit 1.0 May 23, 2017
COPYING C-Bit 1.0 May 23, 2017
INSTALL C-Bit 1.0 May 23, 2017 C-Bit 1.0 May 23, 2017 C-Bit 1.0 May 23, 2017 C-Bit 1.0 May 23, 2017
c-bit.png C-Bit 1.0 May 23, 2017 fixed output files May 24, 2017 C-Bit 1.0 May 23, 2017

c-bit C-Bit Core integration/staging tree

Build Status

What is C-Bit?

C-Bit is an experimental new digital currency that enables instant payments to anyone, anywhere in the world. C-Bit uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. C-Bit 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 C-Bit Core software, see


C-Bit 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 C-Bit Core.

The contribution workflow is described in

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

C-Bit IRC can be found on Freenode at #cbit


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/

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

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.