The Developer Reference aims to provide technical details and API information to help you start building Dash-based applications, but it is not a specification. To make the best use of this documentation, you may want to install the current version of Dash Core, either from source or from a pre-compiled executable.
Questions about Dash development are best asked in one of the Dash development communities. Errors or suggestions related to documentation can be submitted as via the "Suggest Edits" button on the top, right of each page.
In the following documentation, some strings have been shortened or wrapped:
[...]" indicates extra data was removed, and lines ending in a single backslash "\" are continued below.
This Developer Documentation describes how Dash works to help educate new Dash developers, but it is not a specification---and it never will be.
Dash security depends on consensusconsensus - When several nodes (usually most nodes on the network) all have the same blocks in their locally-validated best block chain.. Should your program diverge from consensus, its security is weakened or destroyed. The cause of the divergence doesn't matter: it could be a bug in your program, it could be an error in this documentation which you implemented as described, or it could be you do everything right but other software on the networknetwork - The Dash P2P network which broadcasts transactions and blocks. behaves unexpectedly as in the case of Bitcoin's v0.8 chain fork. The specific cause will not matter to the users of your software whose wealth is lost.
The only correct specification of consensus behavior is the actual behavior of programs on the network which maintain consensus. As that behavior is subject to arbitrary inputs in a large variety of unique environments, it cannot ever be fully documented here or anywhere else.
In addition, we also warn you that this documentation has not been extensively reviewed by Dash experts and so likely contains numerous errors.
Updated about a year ago