{"id":13126,"date":"2018-11-11T00:00:00","date_gmt":"2018-11-10T16:00:00","guid":{"rendered":"https:\/\/www2019.dash.org\/2018\/11\/11\/dash-testnet-v13-is-live-please-join-and-update-all-testnet-miners-nodes\/"},"modified":"2021-09-18T11:36:30","modified_gmt":"2021-09-18T11:36:30","slug":"dash-testnet-v13-live","status":"publish","type":"post","link":"https:\/\/wp.dash.org\/news\/dash-testnet-v13-live\/","title":{"rendered":"Dash TestNet v13 is live, please join and update all TestNet Miners + Nodes"},"content":{"rendered":"

Release candidate v0.13.0.0-rc1 is ready for testnet! ?<\/p>\n

Github release candidate: https:\/\/github.com\/dashpay\/dash\/releases\/tag\/v0.13.0.0-rc1<\/a>
\nRelease notes are not ready yet and will be prepared in the next few days. Post will be updated.
\nGitian sigs can be found here: https:\/\/github.com\/dashpay\/gitian.sigs<\/a><\/p>\n

Before testing:
\nMake sure you made a backup of you mainnet datadir somewhere or at least a backup of wallet.dat\/dash.conf\/masternode.conf;
\nOr use the -datadir and -conf parameters to use completely different directories.<\/p>\n

As this release deploys DIP2\/3\/4, we\u2019ll have to ensure all existing and new functionality works as expected in multiple stages of the deployment. The stages of the deployment are as follows:<\/p>\n

    \n
  1. Full nodes, Masternodes and Miners upgrade their nodes to the latest release<\/li>\n
  2. Miners will start voting on the BIP9 deployment for DIP3, but only if they see enough MNs upgraded (this is automated)<\/li>\n
  3. After enough blocks with the proper BIP9 bits have been mined, DIP3 will activate but stay in \u201ccompatibility mode\u201d<\/li>\n
  4. In this \u201ccompatibility mode\u201d, the existing non-deterministic masternodes should continue to work as expected<\/li>\n
  5. Now MNs can start registering their MNs as deterministic masternodes. Detailed instructions on how to do this will follow when the time arises.<\/li>\n
  6. Even the registered MNs will continue operating in the \u201ccompatibility mode\u201d and will appear in \u201cmasternode list\u201d as expected. InstantSend, PrivateSend, Governance, MN payment logic and so on should continue working as usual.<\/li>\n
  7. We will watch the progress of MNs upgrading to DIP3. When we see enough of these, we\u2019ll turn on spork15 (SPORK_15_DETERMINISTIC_MNS_ENABLED)<\/li>\n
  8. This is the point were all of us will be silent for a minute\u2026as we say goodbye to all the non-deterministic masternodes. We\u2019ll see the output of \u201cmasternode list\u201d immediately switch to the deterministic list (dropping all others). We\u2019ll also see the network go kind of silent, as all the bloat of masternode list synchronization disappears from the network\u2026no more MNB, MNP, MNW, \u2026 messages.<\/li>\n<\/ol>\n

    We are at stage 1. and I will update this line every time we move forward to the next stage.<\/p>\n

    We will have to perform full testing of all functionality in stages 1., 3. \u2013 5. and 8. (so, 3 times in total). This includes:<\/p>\n

    What\/how to test:<\/p>\n