Skip to content
This repository has been archived by the owner on Mar 13, 2024. It is now read-only.


Repository files navigation

Build Status Version Release date Status Platforms Downloads Repo size Issues Open PRs Closed PRs Commits Contributors Last Commit License Gitter

Development is now occurring on the DigiByte-Core repo

As of 2020, development has now moved to the DigiByte-Core organization, under the digibyte repo

You can find more over at

What is DigiByte?

DigiByte (DGB) is a highly secure, decentralized, distributed and time-tested global blockchain that was founded in early 2014 with a focus on cyber security, payments & secure communications technologies.

For more information, as well as an immediately useable, binary version of the DigiByte Core software, see

DigiByte FAQ

Launch Date: January 10th, 2014

Blockchain Type: Public, Decentralized, UTXO based, Multi-Algorithm

Ticker Symbol: DGB

Genesis Block Hash: "USA Today: 10/Jan/2014, Target: Data stolen from up to 110M customers"

Max Total Supply: 21 Billion DigiBytes in 21 Years (2035)

Current Supply: 14,293,304,147 DGB (May 2021)

Block Reward Reduction: 1% Monthly

Current Block Reward: 520 DGB (May 2021)

Mining Algorithms: Five individual: SHA256, Scrypt, Odocrypt, Skein & Qubit

Block Interval: 15 Second Blocks (75 seconds per algo)

Algo Block Share: 20% Block Share Per Algo (5)

Difficulty Retarget: Every 1 Block, 5 Separate Difficulties, independent difficulty for each Mining Algo

SegWit Support: Yes. First major altcoin to successfully activate Segwit. (April 2017)

Hardforks: 5. DigiShield, MultiAlgo, MultiShield, DigiSpeed, Odocrypt

Softforks: 3. SegWit, CSV, NVersionBits

You can mine DigiByte on one of five separate mining algorithms. Each algo averages out to mine 20% of new blocks. This allows for much greater decentralization than other blockchains. An attacker with 99% of of any individual algorithm would still be unable to hardfork the blockchain, making DigiByte much more secure against PoW attacks than other blockchains.

DigiShield Hardfork: Block 67,200, Feb. 28th, 2014

MultiAlgo Hardfork: Block 145k, Sep. 1st 2014

MultiShield Hardfork: Block 400k, Dec. 10th 2014

DigiSpeed Hardfork: Block 1,430,000 Dec. 4th 2015

Odocrypt Hardfork: Block 9,112,320 July 22nd 2019

DigiByte vs Bitcoin


  • 5 DigiByte mining algorithms vs. 1 Bitcoin mining algorithm.
  • DigiByte mining is much more decentralized.
  • DigiByte mining algorithms can be changed out in the future to prevent centralization.


  • DigiByte transactions occur much faster than Bitcoin transactions.
  • 1-2 second transaction notifications.
  • 15 second DigiByte blocks vs. 10 minute Bitcoin blocks.
  • DigiByte has 6x block confirmations 1.5 minutes vs. 1 hour with Bitcoin.

Transaction Volume:

  • DigiByte can handle many more transactions per second.
  • Bitcoin can only handle 3-4 transactions per second.
  • DigiByte currently can handle 560+ transactions per second.

Total Supply:

  • 21 billion DigiBytes will be created over 21 years.
  • Only 21 million Bitcoin will be created over 140 years.
  • 1000:1 ratio. 1000 DigiByte for every Bitcoin.

Marketability & Usability:

  • DigiByte is an easy brand to market to consumers.
  • DigiBytes are much cheaper to acquire.


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

Development Process

The develop branch is regularly built and tested, but is not guaranteed to be completely stable. Additionally, the develop branch represents ongoing development from which candidate releases will be cut. The master branch represents the current stable version currently in production. Tags are created regularly to indicate new official, stable release versions of DigiByte Core. Finally, feature/{a-new-feature} branches represent current development destined for future releases.

The contribution workflow is described in


Automated Testing

Developers are required to write unit tests for new code, and to submit new unit tests for any old code that is changed. 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/

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/

The Travis CI system makes sure that every pull request is built for Windows, Linux, and macOS, and that unit/sanity tests are run automatically.

Manual Quality Assurance (QA) Testing

Changes are required be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. A test plan must be included with the pull request description if testing the changes is not straightforward.