Dash Core

Dash Core Developer Documentation

Welcome to the Dash Core developer documentation. You'll find guides and documentation to help you start working with Dash Core as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    Guides

Constants and Defaults

The following constants and defaults are taken from Dash Core's chainparams.cpp source code file.

NetworkDefault PortMagic ValueStart StringMax nBits
Mainnet99990xBD6B0CBF0xBF0C6BBD0x1e0ffff0
Testnet199990xFFCAE2CE0xCEE2CAFF0x1e0ffff0
Regtest198990xDCB7C1FC0xFCC1B7DC0x207fffff
DevnetUser-defined (default 19799)0xCEFFCAE20xE2CAFFCE0x207fffff

Note: the testnet start string and nBits above are for testnet3.

Command line parameters can change what port a nodenode - A computer that connects to the Dash network. listens on (see -help). Start strings are hardcoded constants that appear at the start of all messages sent on the Dash networknetwork - The Dash P2P network which broadcasts transactions and blocks.; they may also appear in data files such as Dash Core's block database. The Magic Value and nBitsnBits - The target is the threshold below which a block header hash must be in order for the block to be valid, and nBits is the encoded form of the target threshold as it appears in the block header. displayed above are in big-endian order; they're sent over the network in little-endian order. The Start StringStart String - Four defined bytes which start every message in the Dash P2P protocol to allow seeking to the next message. is simply the endian reversed Magic Value.

Dash Core's chainparams.cpp also includes other constants useful to programs, such as the hash of the genesis blockgenesis block - The first block in the Dash block chain. blocks for the different networks.

Updated 12 months ago



Constants and Defaults


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.