Skip to content
bcx
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github bitcoinx init repo Jan 15, 2018
.tx bitcoinx init repo Jan 15, 2018
build-aux/m4 add smart contract Jun 11, 2018
contrib Fix OSX dmg issue (10.12 to 10.14) Oct 29, 2018
depends Modify the url of the qt package Oct 12, 2018
doc doc: Add release notes about the contract rpc interface (#48) Jul 26, 2018
share
src Fix for Incorrect application name when passing -regtest (#81) Jan 24, 2019
test
.gitattributes
.gitignore add contract UI (#67) Oct 8, 2018
.gitmodules add smart contract Jun 11, 2018
.travis.yml some little fix (#77) Jan 14, 2019
CONTRIBUTING.md bitcoinx init repo Jan 15, 2018
COPYING
INSTALL.md bitcoinx init repo Jan 15, 2018
Makefile.am
README.md
autogen.sh
configure.ac remove the macport support on macos (#80) Jan 21, 2019
libbitcoinconsensus.pc.in bitcoinx init repo Jan 15, 2018

README.md

BitcoinX Core integration/staging tree

Build Status

https://bcx.org

What is BitcoinX?

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

License

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

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.

You can’t perform that action at this time.