No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
bluecoiner Version #
Latest commit 669ec70 Oct 2, 2017
Failed to load latest commit information.
.github First Commit Sep 10, 2017
.tx First Commit Sep 10, 2017
build-aux/m4 First Commit Sep 10, 2017
contrib Add gitian files Sep 11, 2017
depends Add gitian files Sep 11, 2017
doc First Commit Sep 10, 2017
qa First Commit Sep 10, 2017
share Change icons Oct 2, 2017
src Changes in validation Oct 2, 2017
.gitattributes First Commit Sep 10, 2017
.gitignore First Commit Sep 10, 2017
.travis.yml First Commit Sep 10, 2017 First Commit Sep 10, 2017
COPYING First Commit Sep 10, 2017 First Commit Sep 10, 2017 First Commit Sep 10, 2017 First Commit Sep 10, 2017 First Commit Sep 10, 2017 Version # Oct 2, 2017 First Commit Sep 10, 2017

Bluecoin Core integration/staging tree

Build Status

What is Bluecoin?

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


Bluecoin 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 Bluecoin 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.

Developer IRC can be found on Freenode at #bluecoin-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 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/

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.


We only accept translation fixes that are submitted through Bitcoin Core's Transifex page. Translations are converted to Bluecoin periodically.

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.