Skip to content
C++ Python C M4 Makefile Shell Other
Branch: master
Clone or download
Pull request Compare This branch is 386 commits ahead, 1392 commits behind DriveNetTESTDRIVE:master.
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.
.github
.tx
build-aux/m4
contrib
depends
doc
share
src
test
.gitattributes
.gitignore
.travis.yml
CONTRIBUTING.md
COPYING
DriveNet.pro
INSTALL.md
Makefile.am
README.md
autogen.sh
configure.ac
libdrivenetconsensus.pc.in

README.md

DriveNet

Learn more about Drivechains here: http://drivechain.info

Start helping here: https://github.com/drivechain-project/bitcoin/issues

For an example sidechain implementation, see: https://github.com/drivechain-project/bitcoin/tree/sidechainBMM

What is DriveNet?

TODO

License

Bitcoin Core (and DriveNet) are 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 Bitcoin Core.

The contribution workflow is described in CONTRIBUTING.md.

The developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.

Developer IRC can be found on Freenode at #bitcoin-core-dev.

Testing

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.

You can’t perform that action at this time.