New version 9.4.0 and 10.8.0

eduffield

eduffield

Core Developer
** THIS VERSION IS NOT BACKWARDS COMPATIBLE, SO ALL MASTERNODES AND CORE DAEMONS NEED TO UPDATE. IN THE NEXT FEW DAYS THE MASTERNODE COUNT WILL GO FROM ZERO TO IT'S REAL COUNT **

This update features a whole new architecture for the masternodes that will fix many of the issues we've been having on the network.

Masternodes now sign their 1000DRK vin for the first message to the network, then they specific a second pubkey that they will sign all further messages with. This second signing key must be specified for all masternodes in the configuration with the option "masternodeprivkey"

To generate a key, boot up the client and execute the command "masternode genkey" and then take the output and put it in the configuration like this "masternodeprivkey=COMMANDOUTPUT. There is also a new protocol command called "dseep" which is signed with this secondary key. This key will never be used in the wallet and is generated randomly.

This allows the client to encrypt the wallet and still be able to sign new messages to the network.

Here's a short list of the new features:
  • "masternode votes" : shows who your client would have voted to pay.
  • "masternode genkey" : generates a completely random key that is never used in the wallet and has no funds associated with it.
  • dseep : all ping messages from masternodes are now shorter and signed with the generated key
  • "masternode stop" : Will let the network know to take your masternode off of the list, signed with the generated key
  • masternode inputs now require 6 confirmations on the 1000DRK transaction in order to be accepted into the list
  • masternodes now should appear all over the network immediately when they're available
  • masternodes should also leave the network when they're unavailable
  • the collateral transaction has been reduced from 0.1DRK to 0.025DRK due to the recent price increase
Who should update?
  • Masternodes
  • Users who want to test the new features
Source code:
https://github.com/darkcoinproject/darkcoin

Stable version (v0.9.4.2):
http://www.darkcoin.io/downloads/darkcoind
http://www.darkcoin.io/downloads/darkcoin-qt
http://www.darkcoin.io/downloads/darkcoin-qt.exe
RC2 (v0.10.8.2):
http://www.darkcoin.io/downloads/rc/darkcoind
http://www.darkcoin.io/downloads/rc/darkcoin-qt
http://www.darkcoin.io/downloads/rc/darkcoin-qt.exe

Command Sequence for starting a masternode on the new version:
cd .darkcoin
darkcoind stop
mv darkcoind darkcoind-100704
wget http://www.darkcoin.io/downloads/rc/darkcoind
chmod 755 darkcoind
nano darkcoin.conf - change masternode=1 to masternode=0
darkcoind
darkcoind masternode genkey - copy output to clipboard or whatever
darkcoind stop
nano darkcoin.conf - change masternode=0 to masternode=1 and add line masternodeprivkey=xxxxxxxxxxxxxxxx....xxxx
darkcoind
darkcoind masternode start 'mypassword'
Click to expand...
 
Last edited by a moderator:
Nice work!

Question about voting: What proportion of votes are required to mess with payments? I.e. does it go to the majority vote, meaning an attacker would need 51% of masternodes to hijack masternode payments?
 
When updating existing masternode:
1) First set masternode flag in the darkcoind.conf to 0.
2) Start deamon
3) Generate private key
4) Stop deamon,
5) Set masternode flag back to 1
6) Add masternodeprivkey= generated key
7) Start deamon & masternode
 
getting this error... what am I goibd wrong?

yidakee@ubuntu:~$ sudo cp darkcoind /usr/bin/
[sudo] password for yidakee:
yidakee@ubuntu:~$ sudo chmod +x /usr/bin/darkcoind
yidakee@ubuntu:~$ darkcoind
DarkCoin server starting
yidakee@ubuntu:~$ Error: You must specific a masternodeprivkey in the configuration. Please see documentation for help.
^C
yidakee@ubuntu:~$ masternode genkey
masternode: command not found
yidakee@ubuntu:~$ darkcoind masternode genkey
error: couldn't connect to server
Click to expand...

So then I tired

yidakee@ubuntu:~$ darkcoind stop
error: couldn't connect to server
yidakee@ubuntu:~$ darkcoind masternode genkey
error: couldn't connect to server
yidakee@ubuntu:~$ darkcoind
yidakee@ubuntu:~$ DarkCoin server starting
Error: You must specific a masternodeprivkey in the configuration. Please see documentation for help.

yidakee@ubuntu:~$ darkcoin masternode genkey
darkcoin: command not found
yidakee@ubuntu:~$ darkcoind masternode genkey
error: couldn't connect to server
yidakee@ubuntu:~$
Click to expand...

please advice

EDIT: ok... so first start masternode=0, the gen key, input in conf and flag masternode =1 ? I'll try
 
Last edited by a moderator:
ok, does this have to be done both local and remote? Either, or ?

Tried local, as it is the one who activates the node, but get this

yidakee@ubuntu:~$ darkcoind masternodeaddr=54.86.33.147:1999
error: couldn't connect to server
Click to expand...
 
Great work Evan, thanks.

Question: When I request masternode list, I get only the 1 entry, the node which is requesting list, any idea why?
 
I'm wondering the same thing as yidakee - how does this work if we're using an offline wallet with remote masternode? Run this in both locations? Only the remote or local?

Thanks.
 
This sequence seemed to work for me (1000DRK on server):
Code: 
cd .darkcoin
darkcoind stop
mv darkcoind darkcoind-100704
wget http://www.darkcoin.io/downloads/rc/darkcoind
chmod 755 darkcoind
nano darkcoin.conf - change masternode=1 to masternode=0
darkcoind
darkcoind masternode genkey - copy output to clipboard or whatever
darkcoind stop
nano darkcoin.conf - change masternode=0 to masternode=1 and add line masternodeprivkey=xxxxxxxxxxxxxxxx....xxxx
darkcoind
darkcoind masternode start 'hahaIamgoingtoberich'
 
OK, it worked for me first time out of the box (thanks for the tip about turning off the masternode in the .conf file, luke).
 
Ok, someone please explain this easier please;

Remote / Local setup

Which has to have the genkey in the .conf file?

Remote? or Local? Or both (i suspect not both since each will generate and individial genkey) ... so I guess is that if its the remote masternode doing the work, then this must the one to genkey into .conf file?

And then start local wallet the usual way?
 
From the bitcointalk.org
If it helps anyone, here's the sequence I used to update my masternode (1000DRK living serverside):

Code:
cd .darkcoin
darkcoind stop
mv darkcoind darkcoind-100704
wget http://www.darkcoin.io/downloads/rc/darkcoind
chmod 755 darkcoind
nano darkcoin.conf - change masternode=1 to masternode=0
darkcoind
darkcoind masternode genkey - copy output to clipboard or whatever
darkcoind stop
nano darkcoin.conf - change masternode=0 to masternode=1 and add line masternodeprivkey=xxxxxxxxxxxxxxxx....xxxx
darkcoind
darkcoind masternode start 'hahaIamgoingtoberich'

Hopefully I didn't miss anything. And thanks to luke997!
 
Yeah, but but what about local remote setup?

I tried setting remote to genkey, and not local... I get

yidakee@ubuntu:~$ darkcoind masternodeaddr=54.86.33.147:1999
error: couldn't connect to server
yidakee@ubuntu:~$
 
thelonecrouton said:
Same here. And with linux qt wallet, 'masternode count' = 0
Click to expand...

Hmm getting the same here :/ very odd

EDIT: and yeah the new wallet is not showing any masternodes being active at the moment, is this a mandatory update for current masternodes?
 
Last edited by a moderator:
thelonecrouton said:
Same here. And with linux qt wallet, 'masternode count' = 0
Click to expand...
Scriptiee said:
Hmm getting the same here :/ very odd

EDIT: and yeah the new wallet is not showing any masternodes being active at the moment, is this a mandatory update for current masternodes?
Click to expand...

This new version makes protocol changes that are not backwards compatible. Currently much of the core daemons are on the old version, so messages aren't getting propagated. This will fix itself over the next few days.

If you're having problems please clear peers.dat and try restarting your daemon (addnode=23.23.186.131). You should see yourself and others in the list.
 
I have found this.
Is this forum linking problem ?

Firsrt two has /rc/ in href.

ycUfgn5.png
 
Last edited by a moderator:
Anyone else having a problem with "masternodeaddr=yourserverip" with this release? I am getting a could not connect to server message when trying to specify my ip.

EDIT: Never mind. I just added it to the config file and it worked. Dont know why i didn't do that before. *banging head on desk"
 
Last edited by a moderator:
You must log in or register to reply here.
Back
Top