• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Version 12.2 release

Status
Not open for further replies.

UdjinM6

Official Dash Dev
Dash Core Group
Hello Everyone,

Today we are happy to announce the release of 0.12.2.0 of the Dash Core software!

This is a major release of the Dash Core 0.12.2.x series. This release contains new features, improvements and bugfixes.

The most notable changes are:
- DIP0001 implementation (which is a 2MB block upgrade);
- Transaction fee reduction 10x (activates via DIP0001 activation);
- InstantSend vulnerability fix (activates via DIP0001 lock in);
- PrivateSend improvement which should allow user to have mixed funds available much faster;
- Various RPC changes;
- Lots of backports from Bitcoin Core and refactoring of our own legacy code which should improve performance and make code more reliable and easier to review;
- Experimental HD wallet with BIP39/BIP44 support.

There are also tons of smaller fixes and improvements, you can see extended description of the items above as well as the full list of changes in release notes available on github: https://github.com/dashpay/dash/blob/v0.12.2.0/doc/release-notes.md

As you might know, the upgrade procedure for this release and the release itself was extensively (stress-)tested to make sure everything works smoothly and nodes can handle the load of full 2MB blocks once they are allowed on the network. We confirmed on testnet that there are no known issues left and we consider this release to be a stable one.

Who is required to update?

It's a major update, so everyone - end users, miners, pool operators, exchanges, and masternode owners have to update.

How to update?

Regular users simply need to download and install an updated version of their wallet software. Instructions can be found here: https://dashpay.atlassian.net/wiki/spaces/DOC/pages/124026991/Updating+to+12.2+-+Users
Masternode upgrade instructions can be found here: https://dashpay.atlassian.net/wiki/spaces/DOC/pages/123961419/Updating+to+12.2+-+Masternodes
P2pool node operators need to update both Dash Core binaries and pool software. The version of p2pool software capable of handling 2MB blocks is available on github: https://github.com/dashpay/p2pool-dash

Downloads:

Binaries are available from official website: https://www.dash.org/downloads/#wallets

Bugs / Issues:

Please report bugs using the issue tracker at github: https://github.com/dashpay/dash/issues

UPDATE:
The latest release is 0.12.2.1 (fixes high CPU usage issue)
https://github.com/dashpay/dash/releases/tag/v0.12.2.1

UPDATE2:
The latest release is 0.12.2.2. This release includes fixes and improvements as follows:
  • Per-UTXO fix (fixes Corebleed vulnerability)
  • Additional indexes fix
  • InstantSend fix
  • PrivateSend fix
  • Removal of support for local masternodes
  • Dropping old (pre-12.2) peers
We encourage all masternode and other full node operators (exchanges, pools, explorers) to update.

https://github.com/dashpay/dash/releases/tag/v0.12.2.2

UPDATE3:
The latest release is 0.12.2.3. This release includes fixes and improvements as follows:
  • InstantSend fixes
  • Fix -liquidityprovider option
  • Fixes a few crashes and compatibility issues
We encourage all masternode and other full node operators (exchanges, pools, explorers) to update.

https://github.com/dashpay/dash/releases/tag/v0.12.2.3
 
Last edited:
How long do masternodes have to upgrade please?
I'd recommend to update as soon as it's paid. Why wait longer? :)

Congratulations and amazing work!

When does 2mb blocks activate?
It's all described in details in DIP0001 ;) tl;dr: https://github.com/dashpay/dips/blob/master/dip-0001.md#expected-activation-conditions which translates in ~2 weeks after we have majority of MNs and miners upgraded to lock it in and another ~2 weeks to activate.
 
i belive DMT tool needs an update for 12.2
so no stress MN holders - the dev is contacted and will get onto it in 2h +
 
i belive DMT tool needs an update for 12.2
so no stress MN holders - the dev is contacted and will get onto it in 2h +

I dunno, I haven't upgraded DMT, I just used the current version to start a masternode and it seemed to work.. or is it really necessary to upgrade DMT and re-start again?
 
I dunno, I haven't upgraded DMT, I just used the current version to start a masternode and it seemed to work.. or is it really necessary to upgrade DMT and re-start again?

MN owners:
upgrade after your MN is paid as there is a protocol bump. Because of this a new start is required after upgrading.
 
I'd recommend to update as soon as it's paid. Why wait longer? :)

Does this mean that if we upgrade we will fall off the network? Thus we need to wait until we are paid? Or are you suggesting this because we may have issues, and if we are slow to get back online, that we might fall off the network? Thanks for clarification :)
 
I dunno, I haven't upgraded DMT, I just used the current version to start a masternode and it seemed to work.. or is it really necessary to upgrade DMT and re-start again?
MN owners:
upgrade after your MN is paid as there is a protocol bump. Because of this a new start is required after upgrading.

isn't the upgrading referring to the MN itself?...the DMT is just being used to issue a masternode start command so I didn't think it needs to be updated, just the MN needs to be updated to 12.2...
 
isn't the upgrading referring to the MN itself?...the DMT is just being used to issue a masternode start command so I didn't think it needs to be updated, just the MN needs to be updated to 12.2...

i was referring to “DMT needs update from developer “ (not u !)
 
i was referring to “DMT needs update from developer “ (not u !)

Yes, but I'm saying that the DMT might not require an update just because a new Dash Core version has been released. I used it to restart my MN (which I updated to 12.2) and it seems to have been successful.
 
Sorry,, I didn't see tungfa's post "MN owners:upgrade after your MN is paid as there is a protocol bump. Because of this a new start is required after upgrading." So that answers my question above, thanks :)
 
Yes, but I'm saying that the DMT might not require an update just because a new Dash Core version has been released. I used it to restart my MN (which I updated to 12.2) and it seems to have been successful.

he is in the progress of updating his nodes
might be needed for governance and such
good it worked for u
 
Yes, but I'm saying that the DMT might not require an update just because a new Dash Core version has been released. I used it to restart my MN (which I updated to 12.2) and it seems to have been successful.

talked to bertrand (dev)
u are right - everything working and on track :rolleyes:
(never mind me)
 
Dash Core packages for Fedora, CentOS and RHEL updated to 12.2 (and 1.1 for Sentinel)
If you don't know what I am talking about, this message likely doesn't apply to you.

WARNING (Masternode people): Ideally only update after your masternode has recently distributed a payment because you have to send a "start" from your wallet due to a protocol bump.

The github for these maintained packages of Dash Core is here: https://github.com/taw00/dashcore-rpm
If you are a current user of these packages, be aware that the 12.1 and 12.2 packages are actually housed in two different repositories so that you do not idly update your box accidentally.

When ready, read the "howto" in the documentation directory (folder) at that github link. I am probably too detailed in my description of the process, but the native packaging makes the whole process roughly a 3 minute exercise with maybe an hour of monitoring.

Enjoy. Stay dashy! :)
 
upload_2017-11-8_11-43-48.png

I have this overlap when syncing (Win10 64bit machine)
 
What would offer the best performance ?
a) Just install 12.2 over 12.1, and keep running as is
b) Or do a complete clean install the current masternode(s) including to new private/pub keys and masternode privkey ?
c) Or anything inbetween
 
What would offer the best performance ?
a) Just install 12.2 over 12.1, and keep running as is
b) Or do a complete clean install the current masternode(s) including to new private/pub keys and masternode privkey ?
c) Or anything inbetween
Update remote to 12.2 && update sentinel
Update local wallet to 12.2 and start the masternode
This is the best :)
 
Status
Not open for further replies.
Back
Top