Skip to content
Bluecoin source tree
C++ Python C M4 Makefile Shell Other
Branch: master
Clone or download
Pull request Compare This branch is 33 commits ahead, 5 commits behind litecoin-project:master.
JUDOKICK Version bump and tag for release
Small cosmetic changes for forms. Version tag for release
Latest commit b118ddc Jun 27, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Language Refactor May 3, 2019
.tx tx: Update transifex slug 016x→017x Aug 2, 2018
build-aux/m4 Refactor May 3, 2019
contrib Version bump and tag for release Jun 27, 2019
depends
doc Cosmetic Qt Changes May 5, 2019
share Replaced All Pixmaps with bluecoin images May 19, 2019
src
test Scripting Refactoring May 3, 2019
.gitattributes LineEndings May 3, 2019
.gitignore
.travis.yml Scripting Refactoring May 3, 2019
CONTRIBUTING.md Language Refactor May 3, 2019
COPYING Refactor May 3, 2019
INSTALL.md Language Refactor May 3, 2019
Makefile.am
README.md Updated Home Readme May 3, 2019
autogen.sh Block Validation Change May 17, 2019
configure.ac Version bump and tag for release Jun 27, 2019
libbitcoinconsensus.pc.in Unify package name to as few places as possible without major changes Dec 14, 2015

README.md

Bluecoin Core integration/staging tree

Build Status

https://bluecoin.org

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 https://bluecoin.org.

License

Bluecoin 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 Bluecoin 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 #bluecoin-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. Further details on running and extending unit tests can be found in /src/test/README.md.

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/test_runner.py

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.

Translations

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.

You can’t perform that action at this time.