{"id":14039,"date":"2018-06-03T00:00:00","date_gmt":"2018-06-02T16:00:00","guid":{"rendered":"https:\/\/www2019.dash.org\/2018\/06\/03\/dash-core-v12-3-testing-is-now-open-please-join-and-help-test-the-upcoming-release\/"},"modified":"2021-09-18T11:37:15","modified_gmt":"2021-09-18T11:37:15","slug":"testing","status":"publish","type":"post","link":"https:\/\/wp.dash.org\/news\/testing\/","title":{"rendered":"Dash Core v12.3 Testing is now open , please join and help test the upcoming release !"},"content":{"rendered":"
Hello everyone,<\/p>\n
UPDATE<\/strong>: 0.12.3.0-rc4 has been uploaded to Github: Please upgrade to the new version and issue mn-start on your masternodes.<\/p>\n RC4 includes a few PrivateSend fixes and a protobump (mn-start required). It also includes a change in the sendrawtransaction RPC to reduce the risks behind the 0-conf+0-fee double spend that was recently shown by Vin Armani. The double spend shown by him is actually known since a long time and not a Dash only problem but affects many other coins. And even though it\u2019s not even a real bug\/vulnerability (merchants should never trust in simple 0-conf+0-fee transactions\u2026that\u2019s why we have InstantSend), we decided to reduce the risk by disallowing 0-fee transactions in sendrawtransaction by default (can be allowed through a parameter).<\/p>\n InstantSend should now also work better on testnet when large parts of the network have not yet upgraded. Please test this.<\/p>\n Detailed changes:\u00a0https:\/\/github.com\/dashpay\/dash\/compare\/v0.12.3.0-rc3\u2026v0.12.3.0-rc4<\/a><\/p>\n After a lot of unfortunate things happening one after another and getting into our way of releasing 12.3, we are finally at a point were we can go to public testing on testnet. For this, we created a 12.3 release candidate (v0.12.3.0-rc2) which can now be downloaded from the Github release page.<\/p>\n Github release candidate:\u00a0https:\/\/github.com\/dashpay\/dash\/releases\/tag\/v0.12.3.0-rc4<\/a> One of the efforts we did in the last days was to fix and re-establish Gitian building and signing. This is not fully done yet, as there seems to be some non-determinism when the final windows setup.exe is built. We will investigate\/fix this in the future. The actual binaries however (which are inside the setup.exe) match between Gitian builds and are signed as well. Gitian sigs can be found here:\u00a0https:\/\/github.com\/dashpay\/gitian.sigs<\/a><\/p>\n Before testing: What\/how to test:<\/p>\n What else you can do:<\/p>\n Testnet tools (explorers, faucets, pools):\u00a0https:\/\/www.dash.org\/forum\/threads\/testnet-tools-resources.1768\/<\/a> MNOs: NOTE: Make sure you pulled Sentinel from We\u2019re very sorry for the delay, and we\u2019ll try to change a few things so this doesn\u2019t happen again. For example, we\u2019ll now distribute knowledge\/experience about the release process a little bit more. This is one of the reasons you see me instead of\u00a0@UdjinM6<\/a>\u00a0doing this post now (another reason is that his internet connection is horribly limited since a few days\/weeks). Another thing we did now is to remove the dependency on Bamboo for doing releases. It has gone down a few weeks ago and left us in a state were we could not do a proper Gitian release anymore\u2026add this together with missing time of multiple team members, missing experience in the release process, bad internet connections, ASICs on testnet (which shouldn\u2019t be a problem anymore after a few fixes we did) and you get the perfect mix of circumstances to get to the delay we got. We learned a few things about our weak spots here, let\u2019s try to fix them.<\/p>\n","protected":false},"excerpt":{"rendered":" Hello everyone,<\/p>\r\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[216],"tags":[],"class_list":["post-14039","post","type-post","status-publish","format-standard","hentry","category-news"],"acf":[],"yoast_head":"\n
\nhttps:\/\/github.com\/dashpay\/dash\/releases\/tag\/v0.12.3.0-rc4<\/a>
\nI\u2019ve also updated the links in this post.<\/p>\n
\n
\nRelease notes can be found here:\u00a0https:\/\/github.com\/dashpay\/dash\/blob\/v0.12.3.0-rc4\/doc\/release-notes.md<\/a><\/p>\n
\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\n
\n
\nNOTE: Most faucets were dry recently, but a few devs now started to automatically fund these faucets. At the moment, at least\u00a0http:\/\/test.faucet.masternode.io\/<\/a>\u00a0should have enough tDASH for everyone.<\/p>\n
\nWiki:\u00a0https:\/\/dashpay.atlassian.net\/wiki\/spaces\/DOC\/pages\/118162190\/Masternodes+under+testnet<\/a>
\nSentinel :\u00a0https:\/\/github.com\/dashpay\/sentinel\/tree\/develop<\/a><\/p>\ndevelop<\/code> branch and changed network to
testnet<\/code> in
sentinel.conf<\/code>. 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<\/code>). Create new folder specifically for testing (e.g.
.dashcore_test<\/code>) and make sure you use
-datadir=<\/code> cmd-line parameter for dashd and dash-cli. You\u2019ll also need a separate crontab line for testnet Sentinel. If you are not 100% sure what you are doing, I\u2019d recommend setting up a new machine\/instance for testing purposes only instead of reusing your mainnet server.<\/p>\n