No description, website, or topics provided.
Branch: master
Clone or download
Latest commit 6ebefc1 Dec 21, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
build-aux/m4
contrib Basex 2.0.0.1 🎉 Dec 21, 2018
depends Basex 2.0.0.1 🎉 Dec 21, 2018
doc Basex 2.0.0.1 🎉 Dec 21, 2018
qa Basex 2.0.0.1 🎉 Dec 21, 2018
share Basex 2.0.0.1 🎉 Dec 21, 2018
src Basex 2.0.0.1 🎉 Dec 21, 2018
CONTRIBUTING.md Basex 2.0.0.1 🎉 Dec 21, 2018
COPYING
INSTALL
Makefile.am Basex 2.0.0.1 🎉 Dec 21, 2018
README.md Basex 2.0.0.1 🎉 Dec 21, 2018
autogen.sh Basex 2.0.0.1 🎉 Dec 21, 2018
configure.ac
pkg.m4 Basex 2.0.0.1 🎉 Dec 21, 2018

README.md

Basex

Basex (BSA) is a sustainable cryptocurrency modeled after Satoshi Nakamoto’s vision for Bitcoin. It is a decentralized, peer-to-peer transactional currency designed to offer a solution to the problem posed by the exponential increase in energy consumed by Bitcoin and other proof-of-work currencies. Proof-of-work mining is environmentally unsustainable due to the electricity used by high-powered mining hardware. Basex utilizes the energy efficient proof-of-stake algorithm inspired by PIVX/DASH, can be mined on any computer, and will never require specialized mining equipment.

License

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

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 and Linux, OS X, and that unit and sanity tests are automatically run.

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.