Skip to content
Branch: master
Clone or download
Latest commit 82a7a5c Feb 25, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
bopu-docs first commit Feb 25, 2019
build-aux/m4 first commit Feb 25, 2019
contrib first commit Feb 25, 2019
depends first commit Feb 25, 2019
doc first commit Feb 25, 2019
qa first commit Feb 25, 2019
share first commit Feb 25, 2019
src first commit Feb 25, 2019
CONTRIBUTING.md first commit Feb 25, 2019
COPYING first commit Feb 25, 2019
INSTALL first commit Feb 25, 2019
Makefile.am first commit Feb 25, 2019
Makefile.in first commit Feb 25, 2019
README.md first commit Feb 25, 2019
autogen.sh first commit Feb 25, 2019
configure.ac first commit Feb 25, 2019
libbopuconsensus.pc.in first commit Feb 25, 2019

README.md

BopuCoin Core staging tree 2.2.3

master: Build Status develop: Build Status

https://bopucoin.com/

What is BopuCoin?

BopuCoin is an experimental new digital currency that enables anonymous, instant payments to anyone, anywhere in the world. BopuCoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. BopuCoin Core is the name of the open source software which enables the use of this currency.

For more information, as well as an immediately useable, binary version of the BopuCoin Core software, see https://bopucoin.com/

License

BopuCoin 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 meant to be stable. Development is normally done in separate branches. Tags are created to indicate new official, stable release versions of BopuCoin Core.

The contribution workflow is described in CONTRIBUTING.md.

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 and Linux, OS X, 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.

You can’t perform that action at this time.