Revolution of decentralized consensus began from Bitcoin. We see the future of the world. Although we Japan lost in internet revolution, we do try to gain no.1 in the world in blockchain revolution from Japan. C0ban is named after Middle Ages Samurai coin called Koban. We think we have still lots of issues on blockchain, crypto currency, and decentralized algorithm. C0ban is the first challenge for us to spread the technology to the world. Though the project, we will be pleased if we could provide a trigger to people to feel the revolutionary world of decentralized consensus.
For more information, please visit c0ban Project.
c0ban Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.
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 c0ban Core.
The contribution workflow is described in CONTRIBUTING.md.
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: 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.
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.