DigiByte (DGB)
Abbreviation: DGB
Pronunciation: DIJ-ih-byte
Also known as: DigiByte, DGB
Definition
DigiByte is the native digital asset of the DigiByte Network, a public proof-of-work blockchain with a UTXO transaction model. DGB is transferred through network-specific addresses and transactions and is used for miner rewards and transaction fees. The network uses multiple mining algorithms and its own parameters, so payment integrations must apply DigiByte-specific address, fee, node, confirmation, and provider-support rules.
Overview
Meaning and scope
DigiByte is the native digital asset of the DigiByte Network, a public proof-of-work blockchain with a UTXO transaction model. DGB is transferred through network-specific addresses and transactions and is used for miner rewards and transaction fees. The network uses multiple mining algorithms and its own parameters, so payment integrations must apply DigiByte-specific address, fee, node, confirmation, and provider-support rules.
Mechanism and operation
DigiByte (DGB) is the native Coin of the DigiByte Network. Transactions consume existing UTXOs and create new recipient and change outputs. Proof-of-work miners order transactions into blocks and receive protocol rewards and transaction fees. DigiByte uses multiple mining algorithms as part of its security and mining-distribution design. It remains an independent chain with its own genesis, software, addresses, transaction history, network messages, and consensus parameters. A DGB payment should be validated through DigiByte-specific address and transaction libraries. Wallets must select inputs, calculate change, estimate fees, sign the transaction, and broadcast it to synchronized nodes.
Practical payment example
A store creates a DGB invoice and monitors the DigiByte chain for the correct amount and confirmation state instead of matching by ticker alone.
Operational checks
Incorrect chain configuration can produce invalid deposits or monitoring gaps even when the transaction format looks familiar. Early visibility should not be confused with irreversible acceptance. For OxaPay operations, integrations should retrieve current currency and network support and bind DGB to the provider’s DigiByte network identifier.
Distinctions and limits
Bitcoin-compatible concepts do not justify using Bitcoin configuration unchanged. Additional blocks reduce the chance of a reorganization affecting the payment, while the business chooses a confirmation threshold appropriate to its value and delivery risk. Reconciliation should preserve destination, amount, transaction hash, fee, block, and confirmation status.
Related reading
Related definitions: Coin, DigiByte Network.
Example
A store creates a DGB invoice and monitors the DigiByte chain for the correct amount and confirmation state instead of matching by ticker alone.
Comparison
Additional blocks reduce the chance of a reorganization affecting the payment, while the business chooses a confirmation threshold appropriate to its value and delivery risk.
Key Takeaway
DGB is the native UTXO asset of the DigiByte Network, requiring DigiByte-specific transaction, fee, confirmation, and provider-support handling.
Sources
- DigiByte Official Website and Documentation — DigiByte (2026-08-02)
- OxaPay API Reference: Supported Networks — OxaPay (2026-08-02)
- OxaPay API Reference: Supported Currencies — OxaPay (2026-08-02)