Skip to content
BLAST Core integration/staging tree
C++ C Python M4 Makefile Shell Other
Branch: master
Clone or download
Pull request Compare This branch is 7 commits ahead of cryptoBLAST:master.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Update BLAST branding and BLAST parameters, update tests, fix broken … Jul 3, 2019
.tx Branding: BLAST Apr 1, 2019
assets Update BLAST branding and BLAST parameters, update tests, fix broken … Jul 3, 2019
binaries Update BLAST branding and BLAST parameters, update tests, fix broken … Jul 3, 2019
build-aux/m4 Branding: BLAST Apr 1, 2019
contrib Update naming for some blast resources, fix Makefile whitespace, MN c… Jul 18, 2019
depends Update BLAST branding and BLAST parameters, update tests, fix broken … Jul 3, 2019
doc Image updates, image processing, display fixes, naming update, add se… Jul 23, 2019
roadmap Update BLAST branding and BLAST parameters, update tests, fix broken … Jul 3, 2019
share Image updates, image processing, display fixes, naming update, add se… Jul 23, 2019
src Disconnect from v1 peers (pre-asset/masternode proto version) Oct 15, 2019
static-builds Update BLAST branding and BLAST parameters, update tests, fix broken … Jul 3, 2019
test Image updates, image processing, display fixes, naming update, add se… Jul 23, 2019
.gitattributes Initial fork of Bitcoin 0.15 Oct 26, 2017
.gitignore Branding: BLAST - naming fixes Apr 8, 2019
.pydevproject fixing pythong comment for copyright Nov 22, 2017
.travis.yml Branding: BLAST Apr 1, 2019
CONTRIBUTING.md Update BLAST branding and BLAST parameters, update tests, fix broken … Jul 3, 2019
COPYING Update BLAST branding and BLAST parameters, update tests, fix broken … Jul 3, 2019
INSTALL.md Update BLAST branding and BLAST parameters, update tests, fix broken … Jul 3, 2019
Makefile.am Branding: BLAST Apr 1, 2019
README.md Update BLAST branding and BLAST parameters, update tests, fix broken … Jul 3, 2019
autogen.sh Initial raven source commit Jul 27, 2018
configure.ac Bump minor version Oct 2, 2019
libbitcoinconsensus.pc.in Branding: BLAST Apr 1, 2019

README.md

BLAST Core integration/staging tree

https://blastblastblast.com

What is BLAST?

BLAST is an experimental digital currency that enables instant payments to anyone, anywhere in the world. BLAST uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network.

License

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

Testnet is now up and running and available to use during development. There is an issue when connecting to the testnet that requires the use of the -maxtipage parameter in order to connect to the test network initially. After the initial launch the -maxtipage parameter is not required.

Use this command to initially start blastd on the testnet. ./blastd -testnet -maxtipage=259200

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

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.