
DigiByte dgb
What is DigiByte?
DigiByte (DGB) is an open-source, public, decentralized blockchain launched on January 10, 2014. It uses a Bitcoin-style UTXO ledger and Proof-of-Work rather than a smart-contract virtual machine, emphasizing security, permissionless participation, and long-term decentralization. The native currency is DGB, used for payments, transaction fees, mining rewards, and ecosystem applications. Official materials describe the project as community-driven, with development under the MIT License and no central controlling organization.
The chain targets roughly 15-second block production and has a 21 billion DGB maximum supply. Issuance is through mining block rewards; rewards decrease by approximately 1% each month, with issuance expected toward about 2035. The 2014 launch had no ICO; the official integration guide documents a disclosed 0.5% premine (105 million coins), split between giveaways/community distribution and development.
DigiByte extends the base chain with DigiAssets for tokenized assets and Digi-ID for passwordless authentication using cryptographic signatures. The current official site also describes DigiDollar as a native, non-custodial USD-pegged stablecoin backed by time-locked DGB reserves. These applications are layered over the UTXO network rather than requiring a general-purpose execution VM.
What problem does DigiByte solve?
DigiByte addresses slow settlement, fee spikes, mining concentration, unstable block intervals when hash power changes, and privacy leakage from transaction propagation. Its 15-second target and UTXO design aim to make payments and asset transfers responsive while keeping validation deterministic.
Mining concentration and hash-rate volatility are addressed through five parallel PoW algorithms (SHA-256d, Scrypt, Skein, Qubit, and Odocrypt), with each intended to mine about 20% of blocks. DigiShield/MultiShield retargets difficulty every block for each algorithm. Dandelion/Dandelion++ routing is intended to make transaction-origin IP inference harder.
The design accepts tradeoffs: DigiByte has no general-purpose smart-contract VM, favoring simpler UTXO execution and conservative upgrades over expressive on-chain computation. Multi-algorithm PoW does not remove market, custody, software, or confirmation risks.
How does DigiByte work?
DigiByte nodes maintain a public UTXO ledger. Transactions consume unspent outputs and create new outputs, allowing independent verification. Miners compete under Proof-of-Work to assemble valid transactions into blocks; a block is targeted approximately every 15 seconds. Full nodes independently check transaction and block rules.
Mining is split across SHA-256d, Scrypt, Skein, Qubit, and Odocrypt. Each has its own difficulty and is intended to receive 20% of blocks. DigiShield/MultiShield adjusts difficulty every block. Odocrypt morphs every 10 days on mainnet, according to the integration guide.
Dandelion routing sends transactions through a randomized stem path before wider diffusion, reducing straightforward linkage between a transaction and its originating node/IP. SegWit is supported, with D-prefix legacy, S-prefix wrapped/multisig, and dgb1 native Bech32 addresses documented for integration.
DigiAssets provides asset issuance/transfer and metadata, while Digi-ID uses a device-held key to sign a site challenge instead of transmitting a password to a centralized broker. Developers can run DigiByte Core, use RPC/Insight infrastructure, and integrate wallets or services with documented ports and address formats.
Key facts
- Ticker DGB; precision 10^-8 (digiSatoshi/digis).
- Public UTXO Proof-of-Work blockchain launched January 10, 2014.
- Approximately 15-second block target; official guide documents 1 MB max block size and theoretical SegWit capacity up to about 1,066 TPS under stated assumptions.
- Five mining algorithms: SHA-256d, Scrypt, Skein, Qubit, and Odocrypt; each targets a 20% block share.
- DigiShield/MultiShield retargets difficulty every block for each algorithm.
- Maximum supply 21,000,000,000 DGB; rewards decrease about 1% per month and issuance is expected toward ~2035.
- No ICO; disclosed 0.5% (105 million DGB) premine split between giveaways/community distribution and development.
- Dandelion/Dandelion++ helps obscure transaction-origin IP linkage.
- DigiAssets provides on-chain asset issuance/transfer; Digi-ID provides passwordless signature authentication.
- The architecture guide identifies absence of a general-purpose smart-contract VM as a design tradeoff.
Official links
Categories
Related coins
Compare
Frequently asked questions
What is DGB used for?
DGB is DigiByte's native coin used for payments, transaction fees, mining rewards, and ecosystem layers such as DigiAssets.
How is DigiByte secured?
Proof-of-Work uses five mining algorithms and per-block difficulty adjustment; security depends on miner and validator participation.
How fast are confirmations?
The protocol targets a block about every 15 seconds. The integration guide recommends at least 8 confirmations for deposits/withdrawals and up to 50 for higher-value transfers.
Does DigiByte support smart contracts?
The architecture guide says it has no general-purpose smart-contract VM; it uses UTXO execution and purpose-built layers such as DigiAssets and Digi-ID.
Where can I verify a transaction or run the software?
Use https://digiexplorer.info for lookup and https://github.com/DigiByte-Core/digibyte for node software and releases.
External trackers
Choose a tracking site for DigiByte:



