Backpackercoin Core integration/staging tree
What is Backpackercoin?
Backpackercoin is an experimental digital asset currency that enables instantly transfer digital asset as payments to anyone, anywhere in the world. Backpackercoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Backpackercoin Core is the name of open source software which enables the use of this currency.
Backpackercoin Core is built on top of Bitcoin Core. The difference between the two is the consensus algorithm: Backpackercoin Core uses both Proof of Stake and Proof of Work consensus, whilst Bitcoin Core uses Proof of Work. Using Proof of Stake as a consensus algorithm is allowing it not only to scale better and be orders of magnitude more efficient in terms of power consumption, but it is also lowering the entry barrier for contributing to the creation of new blocks.
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 Backpackercoin Core.
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.
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:
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.