Skip to content


Folders and files

Last commit message
Last commit date

Latest commit



9 Commits

Repository files navigation

BlazerCoin integration/staging tree

  • Copyright (c) 2009-2013 Bitcoin Developers
  • Copyright (c) 2011-2013 Litecoin Developers
  • Copyright (c) 2017 BlazerCoin Developers

What is BlazerCoin?

BlazerCoin is a cryptocurrency that uses scrypt as its proof-of-work algorithm.

  • 3 Minute block targets
  • DGW3 Difficulty Re-target every block
  • No Halving
  • 294,336,000 Total coins to be created (294 Million)
  • 3MB Blocksize Limit

Reward Base

  • 84 coins per block
  • Pre-mine of 564,480 for Development & Bounties

Extra Info

  • Ticker: BLAZR
  • RPCport: 8212
  • P2Pport: 8213


Use addnode= for Connection/Synchronization

For more information see the Official BlazerCoin Bitcointalk Thread.


BlazerCoin is released under the terms of the MIT license. See COPYING for more information or see

Development process

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

If it is a simple/trivial/non-controversial change, then one of the BlazerCoin development team members simply pulls it.

If it is a more complicated or potentially controversial change, then the patch submitter will be asked to start a discussion (if they haven't already) on the mailing list.

The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if the code doesn't match the project's coding conventions (see doc/coding.txt) or are controversial.

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


Testing and code review is the bottleneck for development; we get more pull requests than we can review and test. Please be patient and help out, 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 for the core code are in src/test/. To compile and run them:

cd src; make -f makefile.unix test

Unit tests for the GUI code are in src/qt/test/. To compile and run them:

qmake BITCOIN_QT_TEST=1 -o Makefile.test
make -f Makefile.test


No description, website, or topics provided.







No releases published


No packages published