Update to 0.9.4.4 or 0.10.8.4 to prepare for the hardfork on May 25!

Still getting different results between the stable and the RC for the masternode votes.

Code: 
$ ./darkcoind getinfo
{
    "version" : 100804,
    "protocolversion" : 70015,
    "walletversion" : 60000,
    "balance" : 1000.00000000,
    "blocks" : 71587,
    "timeoffset" : 0,
    "connections" : 15,
    "proxy" : "",
    "difficulty" : 2104.36196442,
    "testnet" : false,
    "keypoololdest" : 1399068045,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "unlocked_until" : 0,
    "errors" : ""
}
$ ./darkcoind masternode votes
{
    "71583" : "OP_DUP OP_HASH160 8e59899f3d3d0291d0b9581e5bf716458d337126 OP_EQUALVERIFY OP_CHECKSIG",
    "71584" : "OP_DUP OP_HASH160 a195af90c3ccf61ffbb377e6f08d49829f42ffad OP_EQUALVERIFY OP_CHECKSIG",
    "71585" : "OP_DUP OP_HASH160 8e59899f3d3d0291d0b9581e5bf716458d337126 OP_EQUALVERIFY OP_CHECKSIG",
    "71586" : "OP_DUP OP_HASH160 ab7912f0fd72f99db47ad5ca13024aab2bc3d932 OP_EQUALVERIFY OP_CHECKSIG",
    "71587" : "OP_DUP OP_HASH160 6fa380600134982350cc440d7f2be0e0095272fb OP_EQUALVERIFY OP_CHECKSIG",
    "71588" : "OP_DUP OP_HASH160 7597ff1c8f54c58c966726d5bb35f37228492f1b OP_EQUALVERIFY OP_CHECKSIG"

Code: 
$ ./darkcoind getinfo
{
    "version" : 90404,
    "protocolversion" : 70015,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 71587,
    "timeoffset" : 0,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 2104.36196442,
    "testnet" : false,
    "keypoololdest" : 1399071343,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "unlocked_until" : 0,
    "errors" : ""
}
$ ./darkcoind masternode votes
{
    "71582" : "OP_DUP OP_HASH160 a195af90c3ccf61ffbb377e6f08d49829f42ffad OP_EQUALVERIFY OP_CHECKSIG",
    "71583" : "OP_DUP OP_HASH160 3b7cb7a63e631b067161fc20d5214045741cab58 OP_EQUALVERIFY OP_CHECKSIG",
    "71584" : "OP_DUP OP_HASH160 a195af90c3ccf61ffbb377e6f08d49829f42ffad OP_EQUALVERIFY OP_CHECKSIG",
    "71585" : "OP_DUP OP_HASH160 3b7cb7a63e631b067161fc20d5214045741cab58 OP_EQUALVERIFY OP_CHECKSIG",
    "71586" : "OP_DUP OP_HASH160 a195af90c3ccf61ffbb377e6f08d49829f42ffad OP_EQUALVERIFY OP_CHECKSIG",
    "71587" : "OP_DUP OP_HASH160 3b7cb7a63e631b067161fc20d5214045741cab58 OP_EQUALVERIFY OP_CHECKSIG",
    "71588" : "OP_DUP OP_HASH160 3b7cb7a63e631b067161fc20d5214045741cab58 OP_EQUALVERIFY OP_CHECKSIG"
}

Is that meant to happen or did I do something wrong?
 
Question guys... when on testenet 10.8.2, I did genkey on the server, added to conf file, flag=1 -.... but local wouldnt start masternode
I added the SAME genkey to local conf file, and it worked fine.

But I've read around people generating one genkey for server masternode, and another for the local wallet.
So what is the right procedure? I'm ready to go live but want to do it right from the get to!
 
Unfortunately, I don't think anyone can tell if their MN's are really working. Is there a command to see who won the last round? It no longer shows up in the debug log.
 
from what I can see the main net is kinda divided in 3 if it comes to wallet versions, take I a masternode or stable wallet.
It is hard to tell what is really going on until everyone updates their wallets to the correct versions (or at least majority of people)
 
I'd like to understand how it all is supposed to work. When I type in masternode votes, what am I seeing? Am I seeing the last 10 winners of the voting? Are those the masternode genkey keys? Why do I get an IP number instead when I do masternode current instead of it's key? If the results were the same data, I might have a chance to understand what I'm looking at?? If the masternode votes are the last 10 winners, then there must be very few actually working masternodes because there are repeats of 2 to 3 identical keys. Which would mean they're constantly cycling through the same few masternodes.

I wish Evan would come in here and explain a few things???
 
TanteStefana said:
Unfortunately, I don't think anyone can tell if their MN's are really working. Is there a command to see who won the last round? It no longer shows up in the debug log.
Click to expand...
I don't think so. I think we will have to wait for Evan to call for the rebooting of masternodes to have more clues about which ones are actually working. I updated my two ones a few hours ago and the results are:
-Masternode A: it sees 35 masternodes, including my own two (now in 0 state, an hour ago I think they were 1)
-Masternode B: it sees 18 masternodes and it doesn't see itself. The list is not a subset of list in A although most MNs in B are in A. Most are 1s but also a few 0s.
-Local wallet: it sees 15, all in state 1. My MNs not here :(

Masternode votes don't check either. They are different in both MNs and in local wallet, although a few of the votes in the local wallet do check with masternode B.

If I hadn't read a post by Evan in bitcointalk about messages not propagating and the need to wait for the reboot I would be going crazy!
 
I read it and was still going crazy, LOL, but I finally gave up. Too wired now to sleep though, LOL
 
AlexMomo said:
What are the <0> and <1> means at the right of the masternodes list ?

"54.187.221.4:9999" : 0,
"54.255.148.0:9999" : 1,
"54.187.223.100:9999" : 0,
"54.186.167.254:9999" : 1,
"54.72.58.75:9999" : 1,
"141.255.184.191:9999" : 1,
"108.171.248.164:9999" : 0,
"81.71.76.162:9999" : 1,
"54.186.116.211:9999" : 0,
"172.245.215.22:9999" : 1,
"54.72.209.87:9999" : 1,
"80.38.144.39:9999" : 1,
"142.161.23.40:9999" : 1,
"107.170.146.58:9999" : 0,
"54.72.196.78:9999" : 0,
"54.207.101.228:9999" : 0,
"184.73.179.148:9999" : 1,
"37.59.168.129:9999" : 1,
"188.226.133.22:9999" : 1,
"188.226.248.36:9999" : 1,
"54.215.181.251:9999" : 0
Click to expand...

1 means the node is active (it's pinged in the last hour), 0 means it's expired.
 
thelonecrouton said:
Updated. Both my MNs can see themselves and each other, qt wallet can only see the last few on the list, seems to be working itself very slowly back up the list from the bottom.

edit: actually no, qt wallet is only seeing nodes launched after it was as the new ones come online. Not seeing any nodes from before it was launched.
Click to expand...

So this update is incompatible with the old messaging system for the masternodes. This basically means that messages weren't able to propagate correctly across the network, so we had different lists for awhile. From the looks of it about 50% of the users have updated, so messages should start propagating correctly soon.
 
Version 9.4.5 and 10.8.5

I've added some code to help the network sync while we update. Now the client will request the masternode list from each client it connects it and combine them.

If you're having syncing problems with the masternode list or you are a masternode please update.

Source code:
https://github.com/darkcoinproject/darkcoin

Stable version (v0.9.4.5):
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.5):
http://www.darkcoin.io/downloads/rc/darkcoind
http://www.darkcoin.io/downloads/rc/darkcoin-qt
http://www.darkcoin.io/downloads/rc/darkcoin-qt.exe
 
eduffield said:
So this update is incompatible with the old messaging system for the masternodes. This basically means that messages weren't able to propagate correctly across the network, so we had different lists for awhile. From the looks of it about 50% of the users have updated, so messages should start propagating correctly soon.
Click to expand...

Yes, seems like the critical mass of updated nodes is reached, the network is starting to regain cohesion.
My masternodes have currently 37 active MNs in their lists and counting :)

Thanks for the great work!

EDIT: 43 nodes

EDIT: http://drk.poolhash.org/masternode.html back again :)
 
Last edited by a moderator:
Updated, much more reassuring - both my MNs see each other, latest qt wallet also sees both them, flagged '1', and did so within about 30 secs of firing up. I am a happy masternodeer!
Masternode count varies by 3 or 4 between them but this will probably sort itself out.
 
Awesome! I updated my two masternodes and they now show the same 45 list of active masternodes that my local wallet has. Votes are also the same everywhere. Great job!
 
pinwc4 said:
I just downloaded it and the Linux darkcoind rc binary is still pointing to the 0.10.8.4 version.
Click to expand...
You are right. I was so happy that everything seemed to be working that I didn't check the version I was running, but it is 0.10.8.4
 
Whats the difference in the config file between
Code: 
externalip= xxx.xxx.xxx

masternodeaddr= xxxx.xxx.xxx
 
Hmm, bugger, getinfo shows "version" : 100804, but it all works and I am afraid to change it! :confused:
edit: updated to 100805
 
Last edited by a moderator:
You must log in or register to reply here.
Back
Top