Release candidate v0.15.0.0-rc4 is ready for testnet!
Github release candidate: https://github.com/dashpay/dash/releases/tag/v0.15.0.0-rc4
Release notes are not ready yet and will be prepared in the next few days. Post will be updated.
Gitian sigs can be found here: https://github.com/dashpay/gitian.sigs
Before testing:
Make sure you made a backup of your mainnet datadir somewhere or at least a backup of wallet.dat/dash.conf;
Or use the -datadir and -conf parameters to use completely different directories.
This release contains many maintenance related changes. Largest part is the backporting of Bitcoin 0.15 (excluding features we do not want) and the removal of a lot of legacy code (remains of the legacy masternode list code and all of the legacy InstantSend code). Governance is mostly untouched. PrivateSend got slightly improved. Details will follow in the release notes.
We expect this upgrade to be quite seamless compared to the v13 or v14 release, as there are no on-chain consensus related changes involved. Effort for integration partners should be minimal, as only a few RPC parameters and return codes changed.
The usual testing should be performed to make sure everything works as expected:
- Check if normal transactions are still working, perform some automated load testing if you want. All transactions should get InstantSend locked
- Check if ChainLocks are happening on new blocks
- Check if creating and voting on proposals work. Also check if winning proposals get paid and other don't.
- Test if PrivateSend is working. Make sure to use the recently added ability to mix in many sessions in parallel (note that this feature requires you to also enable multi session support which is off by default).
- Run a masternode or two, make sure it is paid. Instructions can be found here: https://docs.dash.org/en/stable/masternodes/setup.html
What else you can do:
- Report serious issues (crashes/hangs/GUI glitches) : https://github.com/dashpay/dash/issues/new
Testnet tools (explorers, faucets, pools): https://www.dash.org/forum/threads/testnet-tools-resources.1768/
For now, only the faucet at http://test.faucet.masternode.io/ is known to be well funded. It should have enough for everyone.
MNOs:
Wiki: https://docs.dash.org/en/stable/developers/testnet.html#masternodes
Sentinel : https://github.com/dashpay/sentinel/tree/develop
NOTE: Make sure you pulled Sentinel from `develop` branch and changed network to `testnet` in `sentinel.conf`. If you already have a mainnet masternode on the same server, do NOT run testnet masternode in the same datadir as your mainnet masternode (i.e. `.dashcore`). Create new folder specifically for testing (e.g. `.dashcore_test`) and make sure you use `-datadir=<yourtestnetdatadirhere>` cmd-line parameter for dashd and dash-cli. You'll also need a separate crontab line for testnet Sentinel. If you are not 100% sure what you are doing, I'd recommend setting up a new machine/instance for testing purposes only instead of reusing your mainnet server.
Github release candidate: https://github.com/dashpay/dash/releases/tag/v0.15.0.0-rc4
Release notes are not ready yet and will be prepared in the next few days. Post will be updated.
Gitian sigs can be found here: https://github.com/dashpay/gitian.sigs
Before testing:
Make sure you made a backup of your mainnet datadir somewhere or at least a backup of wallet.dat/dash.conf;
Or use the -datadir and -conf parameters to use completely different directories.
This release contains many maintenance related changes. Largest part is the backporting of Bitcoin 0.15 (excluding features we do not want) and the removal of a lot of legacy code (remains of the legacy masternode list code and all of the legacy InstantSend code). Governance is mostly untouched. PrivateSend got slightly improved. Details will follow in the release notes.
We expect this upgrade to be quite seamless compared to the v13 or v14 release, as there are no on-chain consensus related changes involved. Effort for integration partners should be minimal, as only a few RPC parameters and return codes changed.
The usual testing should be performed to make sure everything works as expected:
- Check if normal transactions are still working, perform some automated load testing if you want. All transactions should get InstantSend locked
- Check if ChainLocks are happening on new blocks
- Check if creating and voting on proposals work. Also check if winning proposals get paid and other don't.
- Test if PrivateSend is working. Make sure to use the recently added ability to mix in many sessions in parallel (note that this feature requires you to also enable multi session support which is off by default).
- Run a masternode or two, make sure it is paid. Instructions can be found here: https://docs.dash.org/en/stable/masternodes/setup.html
What else you can do:
- Report serious issues (crashes/hangs/GUI glitches) : https://github.com/dashpay/dash/issues/new
Testnet tools (explorers, faucets, pools): https://www.dash.org/forum/threads/testnet-tools-resources.1768/
For now, only the faucet at http://test.faucet.masternode.io/ is known to be well funded. It should have enough for everyone.
MNOs:
Wiki: https://docs.dash.org/en/stable/developers/testnet.html#masternodes
Sentinel : https://github.com/dashpay/sentinel/tree/develop
NOTE: Make sure you pulled Sentinel from `develop` branch and changed network to `testnet` in `sentinel.conf`. If you already have a mainnet masternode on the same server, do NOT run testnet masternode in the same datadir as your mainnet masternode (i.e. `.dashcore`). Create new folder specifically for testing (e.g. `.dashcore_test`) and make sure you use `-datadir=<yourtestnetdatadirhere>` cmd-line parameter for dashd and dash-cli. You'll also need a separate crontab line for testnet Sentinel. If you are not 100% sure what you are doing, I'd recommend setting up a new machine/instance for testing purposes only instead of reusing your mainnet server.
Last edited:
