All content has been migrated to docs.dash.org. You will be automatically redirected momentarily.
Dash Core performs full masternode synchronization as required. There are four conditions that initiate a start/restart the sync process:
- Initial startup of Dash Core
- More than 60 minutes have passed since the last activation
- A failure occurred during the last sync attempt (after a 1 minute cooldown before sync restarts)
- Issuing a
mnsync resetRPC command
Initial Masternode Sync
The deterministic masternode lists introduced by DIP3 eliminated several steps of the sync process related to the masternode list and masternode payments. Since that information is now available on-chain, P2P messages related to those steps were deprecated.
This diagram shows the order in which P2P messages are sent to perform masternode synchronization initially after startup.
The following table details the data flow of P2P messages exchanged during initial masternode synchronization after the activation of DIP3 and Spork 15.
|Syncing Node Message||Direction||Masternode Response||Description|
|→||Syncing node requests sporks|
|→||Syncing node requests mempool entries|
|3. Governance||See Governance sync|
Masternode Sync Status
There are several status values used to track masternode synchronization. They are used in both
ssc messages and the
|-1||Removed in Dash Core 0.16.0|
|0||Deprecated (merged with |
Synchronization just started, was reset recently, or is still in IBD
|1||Renamed in Dash Core 0.16.0|
Synchronization pending - waiting after initial to check for more headers/blocks.
|4||Synchronizing governance objects|
Ongoing Masternode Sync
Once a masternode completes an initial full sync, continuing synchronization is maintained by the exchange of P2P messages with other nodes. This diagram shows an overview of the messages exchanged to keep governance objects synchronized between masternodes.
After the initial governance synchronization, governance information is kept current by the
govobj messages and
govobjvote messages relayed on the network. Unsynchronized peers may send
govsync messages to request governance sync.
Masternode Sync Schedule
The following tables detail the timing of various functions used to keep the masternodes in sync with each other. This information is derived from the scheduler section of
|6||MN Sync||Synchronizes sporks and governance objects (masternode-sync.cpp)|
The following actions only run when the masternode sync is past
|60||Process MN Connections||Disconnects some masternodes (|
|60||InstantSend Check/Remove||Remove expired/orphaned/invalid InstantSend candidates and votes (|
|300||Maintenance||Check/remove/reprocess governance objects (|
Updated 23 days ago