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

11.2 - Dash Release

eduffield

Core Developer
This is the first Dash release and it’s huge! The team has been hard at work for over 2 months on improving various parts of the core client. The client should overall be much faster to use, require less bandwidth, will require a level-of-service from masternodes, perform Darksend transactions faster and has a new beautiful look and feel.

All users must update!

This includes protocol changes, so all users must update. Enforcement will be turned off briefly while the network updates, then turned on when we hit 80% in a day or two. Older version masternodes will cease to be paid immediately due to the incompatibility of the protocol!

Special thanks to Crowning and Snogcel for the new look and feel, check it out below:


xfQ9qHqt0M_xHY0djk5PMzVdxtzOtu-kau5Q6KkAQL2tEsbtbaOYV36vsnQUSDrKBd86knoOaDA-K8leqwnPT9sb47W31imrqw9X-yUuSukcNEvGBcv3zGLmvYC6zJ31-28Lwj4



Another special thanks to UdjinM6 for writing a really nice masternode management system. You can check it out here: https://github.com/darkcoin/darkcoin/blob/v0.11.2.x/src/masternodeman.cpp

This module makes it much faster to restart a node, because it won’t have to request the masternode list every time. It also keeps a record of the DS variables, which will make the network much more harder to trick.

Configurations Have Been Moved!

Configurations have been moved from .darkcoin to .dash! You’ll need to do the following when updating your client. First close Darkcoin and backup your data directory.

Windows: %APPDATA%\Darkcoin\
Mac OS: ~/Library/Application Support/Darkcoin/
Unix/Linux: ~/.darkcoin/

After that rename it to Dash for Windows/Mac, or .dash for linux. Next go open the directory and locate the darkcoin.conf file, rename this to dash.conf.

Next, simply update to the newest Dash client and restart.

Other new things in this release:

  • Proof-of-service (PoSe), all masternodes MUST have their port opened correctly, otherwise they will be removed. This also checks to make sure masternodes are responding to work requests such as InstantX. This basically will ensure that all nodes are on the same fork and their network functionality is working properly. This was implemented so that the part of the masternode network checks another part of the network, so it's 100% decentralized.
  • New command “masternode list pose”, shows all of the masternodes PoSe scores, good for debugging if your masternode is getting punished for not providing proper service.
  • New DarkSend caching, which improves the experience of using DarkSend vastly
  • Masternode Blinding is NOT part of this release, while it’s in the code, it’s currently disabled. It’ll take a bit more work to complete and we were running out of time before the March 25th deadline, so it’s being moved to the next release.
  • Thanks to PoSe, InstantX should work nearly all of the time now.
  • New masternode voting system for new Dash initiates, each masternode gets one vote. See the new commands “masternode list votes” and “masternode vote yea|nay”. First vote, what color is this dress : http://imgur.com/QjqfntR ? Blue and Black (yea) or White and Gold (nay)
  • Full release notes: https://github.com/darkcoin/darkcoin/blob/master/doc/release-notes/release-notes-0.11.2.md

v0.11.2.22 - Downloads

https://www.dashpay.io/downloads/

Thanks for helping with this release:

-UdjinM6
-Crowning
-Snogcel
-Propulsion, for maintaining our great forums we tested on
-Flare for setting up Transifex again
-All of those who helped translate the new version

Our awesome testers this release:

AjM,Moli, Tante, Lariondos, xxxsexygirls, Sub-Ether, Moocowmoo, AlexMomo
Bridgewater, elbereth, HowlingMad, JPCrypto, the-baker, Lukas_Jackson
coingun, darkred, MangledBlue, yikadee
 
Looks great!! I know its not really important at this time but are we sticking with Darksend? I thought that was being re-branded as well.
 
Innovation as it happens in real time :cool::cool::cool:
Interesting voting system, so how does one propose a vote then, can any masternode do it, whats the command?
 
Last edited by a moderator:
When I try to launch ./dashd getinfo I keep getting error: you must set rpcpassword <password> in the configuration file, although I have set a proper dash.conf.
Any hint?

edit: nvm solved
 
Last edited by a moderator:
https://dashninja.pl is updated, this version shows the Proof-of-Service score (worst found accross monitoring nodes): 0 is OK, 6 is error, in between (1 to 5) something is wrong.
Last Paid is also shown (started gathering the info 18h ago so it won't show for older blocks).
Wondering, can you list all the variables that effect proof of service rating? TIA
 
My MNs seem to have updated ok but when I do a ./dash masternode list command nothing show up...! And the MN count is also 0. All seems ok but thought I'd mention it in case there is a bug in there somewhere...
 
My MNs seem to have updated ok but when I do a ./dash masternode list command nothing show up...! And the MN count is also 0. All seems ok but thought I'd mention it in case there is a bug in there somewhere...
There's a protocol bump and network messages incompatibility with older version. Guess we need "masternode start" from cold wallet to force it go live.
 
I'm getting log errors:

2015-03-30 16:14:33 ProcessMessages(dsee, 253 bytes): Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2015-03-30 16:14:33 ProcessMessage(dsee, 253 bytes) FAILED

Can this be ignored or do I need to do something on my end?

Thanks
 
I'm getting log errors:

2015-03-30 16:14:33 ProcessMessages(dsee, 253 bytes): Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2015-03-30 16:14:33 ProcessMessage(dsee, 253 bytes) FAILED

Can this be ignored or do I need to do something on my end?

Thanks
Yes to be ignored, I have been getting this error for months and no problems.
 
There's a protocol bump and network messages incompatibility with older version. Guess we need "masternode start" from cold wallet to force it go live.

It's all good now, just took a few mins to get itself together I think. All MNs updated and responding properly. Even got a MN payment just then :smile:

Good work dev team!!

Walter
 
Any more info regarding the "really nice masternode management system"?
 
Back
Top