DigiByte (DGB)
Reference metadata for DigiByte. Full parameter tables and request/response examples are being authored — the verified facts below are accurate today.
| Field | Value |
|---|---|
| coinType | 20 |
| keyPath | m/44'/20'/<accountIdx>'/0/0 |
| amount unit | DigiByte satoshi (1 DGB = 1e8) |
| chainId | bip122:7497ea1b465eb39f1c8f507bc877078f/slip44:20 |
Supported Methods
| Method | Supported |
|---|---|
| getAddress | ✓ |
| signTransaction | ✓ |
| signMessage | ✗ |
| signTypedData | ✗ |
| signAuthEntry | ✗ |
Notes
Fully signable UTXO chain. Supports both legacy P2PKH and native SegWit (bech32 dgb1… via the DGB-SEGWIT variant). Both variants share one chainId, so you must send addressFormat: 'segwit-native' to get a dgb1… address — omit it and the request resolves to the legacy P2PKH account. Shares the Bitcoin-family signTransaction path; provide the previous transactions for the inputs you spend.
This is a fully signable UTXO chain that shares the Bitcoin-family signing path. The signTransaction payload shape (inputs, outputs, previous transactions) matches the Bitcoin reference — only the address version, coinType and amount decimals differ (see above). Per-parameter tables come from the DCENT Web Bridge and the connector presets.
signTransaction
await dcent.sign({
method: 'signTransaction',
chainId: 'bip122:7497ea1b465eb39f1c8f507bc877078f/slip44:20',
payload: {
keyPath: "m/44'/20'/<accountIdx>'/0/0",
transaction: {
/* see Notes */
}
}
}) // → body.parameter.signature