Dash

Overview

Zafeguard Dash components for the full transaction lifecycle — address derivation, UTXO selection, signing, and broadcasting.

Overview

Zafeguard ships 7 Dash components covering the full lifecycle of Dash transactions: address derivation → UTXO selection → fee estimation → signing → broadcasting.

Dash uses P2PKH addresses exclusively (no SegWit or Taproot). Network access (UTXO fetch, fee estimation, broadcast) is handled by Zafeguard — no RPC endpoint configuration required.


Categories

GroupComponentsPage
TransactionsBUILD, SIGN, BROADCAST, COMPUTE_SIGNATURE_HASHTransactions →
Wallets & AddressesCOMPUTE_ADDRESS, GET_BALANCE, GET_DERIVATION_PATHWallets & Addresses →

Chain facts

PropertyValue
BIP-44 coin type5 (m/44'/5'/...)
Smallest unitduff (1 DASH = 100,000,000 duffs)
Payment typesP2PKH only
Signed-message prefix\x19DarkCoin Signed Message:\n
Networksmainnet, testnet

Typical Dash workflow

GET_DASH_DERIVATION_PATH


COMPUTE_PUBLIC_KEY  ──▶  COMPUTE_DASH_ADDRESS


GET_DASH_ACCOUNT_BALANCE (guard check)


BUILD_DASH_TRANSACTION
        │ messageHashes[]      │ unsignedTransaction
        ▼                      │
SIGN_WITH_KEY_SHARE (×N)       │
        │ signatures[]         │
        └──────────┬───────────┘

        SIGN_DASH_TRANSACTION
                   │ signedTransaction

        BROADCAST_DASH_TRANSACTION
                   │ txid

              [Confirmed]

On this page