What is DigiByte?

DigiByte (DGB) is a rapidly growing four year old decentralized global blockchain 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 https://digibyte.io

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: 8,107,031,908 DGB (May 2017)

Yearly Supply Inflation: 12% in 2017

Block Reward Reduction: 1% Monthly

Current Block Reward 891 DGB

Mining Algorithms: Five (Sha256, Scrypt, Groestl, Skein & Qubit)

Block Timing: 15 Second Blocks, (1.5 Minutes per algo)

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

Difficulty Retarget Every 1 Block, 5 Separate Difficulties, 1 For Each Mining Algo

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

Hardforks 4. DigiShield, MultiAlgo, MultiShield, DigiSpeed

Softforks 3. SegWit, CSV, NVersionBips

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. In order for an attacker to hardfork DigiByte the attacker would need to control 93% of the hashrate on 1 algo, and 51% of the other 4 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

DigiByte vs Bitcoin

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

Speed: DigiByte transactions occur much faster than Bitcoin transactions. 1-3 second transaction notifications. 15 second DigiByte blocks vs. 10 minute Bitcoin blocks. DigiBytes are confirmed after 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 280+ transactions per second. The 2015 DigiSpeed hardfork introduced changes that double the capacity of the network every two years.

Total Supply: More DigiBytes, lower price, more micro transactions, better price stability. 21 billion DigiBytes will be created over 21 years. Only 21 million Bitcoins will be created over 140 years. 1:1000 ratio. 1 Bitcoin for every 1000 DigiBytes.

Flexibility: Ability to quickly add new features. DigiByte can add new features & upgrades much quicker than Bitcoin. Future DigiByte upgrades will push transaction limit to several thousand per second.

Marketability & Usability: DigiByte is an easy brand to market to consumers. DigiBytes are much cheaper to acquire.

License

DigiByte 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 DigiByte Core.

The contribution workflow is described in CONTRIBUTING.md.

Testing

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

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.