Skip to content
BiblePay
Branch: master
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 v1.0 Jul 18, 2017
bible-docs v1.0 Jul 18, 2017
build-aux 1.0.4.4c-Non-Mandatory Sep 30, 2017
contrib 1.1.7.6-Leisure Upgrade Dec 31, 2018
depends
doc
qa 1.0.7.7-Mandatory Upgrade Jan 12, 2018
share
src 1.2.0.1-Mandatory Upgrade Mar 15, 2019
.gitattributes
.gitignore
.travis.yml v1.0 Jul 18, 2017
BuildBiblePay.txt
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md Apr 16, 2018
CONTRIBUTING.md
COPYING
INSTALL Updated URLs to current locations & update PrivateSend denominations Oct 28, 2018
InstallingIPFS_Ubuntu64.md
Makefile.am
README.md
autogen.sh FILE PERM EXEC Sep 18, 2017
build-osx-new.md
configure.ac 1.2.0.1-Mandatory Upgrade Mar 15, 2019
libbitcoinconsensus.pc.in
macOS_bundle.sh

README.md

Biblepay Core staging tree 0.12.1

master: Build Status v0.12.0.x: Build Status v0.12.1.x: Build Status

https://www.Biblepay.org

What is Biblepay?

Biblepay is an experimental new digital currency that enables anonymous, instant payments to anyone, anywhere in the world. Biblepay uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Biblepay Core is the name of the open source software which enables the use of this currency.

For more information, as well as an immediately useable, binary version of the Biblepay Core software, see https://www.biblepay.org/#downloads

License

Biblepay 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 meant to be stable. Development is normally done in separate branches. Tags are created to indicate new official, stable release versions of Biblepay 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

There are also regression and integration tests of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.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 Biblepay 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 follow the forum.

You can’t perform that action at this time.