Skip to content
A Bitcoin Fork which supports encrypted reference lines
Branch: master
Clone or download
Pull request Compare This branch is 1 commit behind cadkas:master.
Latest commit 33e8bb6 Oct 15, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.tx First release based on Bitcoin Core v0.16 May 12, 2018
build-aux/m4 First release based on Bitcoin Core v0.16 May 12, 2018
contrib First release based on Bitcoin Core v0.16 May 12, 2018
depends Depends fixed May 12, 2018
doc Makefile was missing May 12, 2018
share
src Bug fix Oct 15, 2018
test First release based on Bitcoin Core v0.16 May 12, 2018
.gitignore Makefile was missing May 12, 2018
.travis.yml
CONTRIBUTING.md First release based on Bitcoin Core v0.16 May 12, 2018
COPYING First release based on Bitcoin Core v0.16 May 12, 2018
INSTALL.md First release based on Bitcoin Core v0.16 May 12, 2018
Makefile Makefile was missing May 12, 2018
Makefile.am First release based on Bitcoin Core v0.16 May 12, 2018
README.md First release based on Bitcoin Core v0.16 May 12, 2018
autogen.sh First release based on Bitcoin Core v0.16 May 12, 2018
configure.ac First release based on Bitcoin Core v0.16 May 12, 2018
libbitcoinrecoconsensus.pc.in First release based on Bitcoin Core v0.16 May 12, 2018

README.md

Bitcoinreco Core integration/staging tree

https://bitcoinreco.com

What is Bitcoinreco?

Bitcoinreco is a Bitcoin Fork which supports encrypted reference lines.

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

License

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

Translations

Changes to translations as well as new translations can be submitted to Bitcoinreco Core's Transifex page.

Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.

Translators should also subscribe to the mailing list.

You can’t perform that action at this time.