bitcoin hard fork
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.tx
build-aux/m4
contrib
depends
doc
share
src
test
.gitattributes
.gitignore
.travis.yml
CONTRIBUTING.md
COPYING
INSTALL.md
LICENSE
Makefile.am
README.md
autogen.sh
configure.ac
libbitcoinconsensus.pc.in

README.md

BitClassic coin Core integration/staging tree

http://bicc.io

What is BitClassic coin?

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

License

BitClassic coin 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 BitClassic coin Core.

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.