DigiByte (DGB)

Overview

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. Bitcoin-compatible concepts do not justify using Bitcoin configuration unchanged.

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. Incorrect chain configuration can produce invalid deposits or monitoring gaps even when the transaction format looks familiar.

DGB settlement follows Probabilistic Finality. 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. 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. Reconciliation should preserve destination, amount, transaction hash, fee, block, and confirmation status. An old supported-asset list is not a reliable production configuration.

DigiByte-specific testing should include address generation, input selection, transaction serialization, fee estimation, change recovery, node synchronization, and confirmation updates. A generic UTXO integration can appear functional during a simple transfer while still failing on network prefixes, wallet recovery, or provider-specific status mapping.

Production rollout should begin with low-value transfers and independent node or explorer comparison before larger merchant or treasury flows are enabled.