No description, website, or topics provided.
Clone or download
Pull request Compare This branch is 710 commits ahead, 3846 commits behind bitcoin:master.
rangershi and Ben002 last log his err
change version to 17.6
Latest commit 664e852 Oct 16, 2018

README.md

Super Bitcoin

http://superbtc.org

What is Super Bitcoin?

Super Bitcoin is an experimental hard fork of Bitcoin, which is also an experimental digital currency. Super Bitcoin tries to implement, test, improve, and innovate features that Bitcoin society members have long proposed or requested, the results of which could in turn be valuable to Bitcoin itself.

License

Super Bitcoin 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 Super Bitcoin .

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