V12 Release

elbereth

Active Member
Dash Support Group
Mar 25, 2014
440
466
133
Costa Rica
dashninja.pl
Dash Address
XkfkHqMnhvQovo7kXQjvnNiFnQhRNZYCsz
Dash Ninja is now updated to v12 capable (albeit partial) support.
Monitoring nodes are currently syncing.
dmn11 is the one staying on v11 for monitoring support.
I will try to improve v12 support in the coming days, time permitting.
 

LucD88

Member
Aug 15, 2014
75
49
58
Thanks for the quick reply guys, that worked! :)

But how do I tell if they're online? Right now that command displays:

".........txid1923819238-1" : "106.xxx.xxx.xxx:9999"
 

GilAlexander

Member
Jun 26, 2014
84
23
48
Exactly the same. Just add "addr" after "list"
But there's no "status" in such output (it can be ENABLED or EXPIRED - don't know what does it mean but EXPIRED looks more negative than ENABLED).
I wonder how to combine mastenodelist "addr" with masternodelist "status".
One can use ./masternodelist | grep "txid" instead. Txid is a txid of 1000dash masternode transaction.
And I'm still unable to sync masternode list (50%) on my desktop wallet to check my masternode txid in the list - it shows 2911 masternodes without my one.

upd `./masternodelist full` shows ip as well as status.
 
Last edited by a moderator:

minersday

Member
Apr 9, 2014
77
19
48
2015-08-14 19:56:00 CActiveMasternode::GetMasterNodeVin - Could not locate specified vin from possible list
2015-08-14 19:56:00 CActiveMasternode::ManageStatus() - Could not find suitable coins!

I have masternode cold addr with multiple vin and vouts, is there some limit to what it will check.
and original 1000 dash are in the 0-address.


edit: had to generate new masternode genkey and started working.
 
Last edited by a moderator:

cwnage

Member
Aug 1, 2015
41
22
48
Could not compile on centos 6

got
Code:
helpers/memenv/memenv.cc: In member function ‘leveldb::Status leveldb::<unnamed>::FileState::Read(uint64_t, size_t, leveldb::Slice*, char*) const’:
helpers/memenv/memenv.cc:65: error: ‘SIZE_MAX’ was not declared in this scope
probably because of older gcc?

replaced the folder src/leveldb with leveldb 1.17 and it compiles... but is this OK?
 

AlexMomo

New Member
May 19, 2014
33
7
8
I have updated my MNs with success but just got this message on one of them:


Code:
2015-08-14 20:09:14 mnw - winner out of range - FirstBlock 313534 Height 1095195517 bestHeight 319366
2015-08-14 20:09:14

************************
EXCEPTION: NSt8ios_base7failureE
non-canonical ReadCompactSize()
dash in ProcessMessages()

2015-08-14 20:09:14 ProcessMessage(mnw, 145 bytes) FAILED peer=81
2015-08-14 20:09:14 ProcessMessages(mnw, 145 bytes): Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
Edit: I have restarted the daemon and the message just disappeared...
 
Last edited by a moderator:

pille

Active Member
Feb 18, 2015
268
295
123
I have one MN that I can't grep from itself, but its visible from another MN and on dashninja.pl
 

emmo

New Member
May 23, 2014
37
11
8
After remove peers.dat(on both sides) the 1000DASH stay locked,only to me ?
 

weirdgod

Well-known Member
Foundation Member
Jun 4, 2014
91
51
168
Slovenia, EU
Are v11 masternodes still being paid?
Or only v12?

Also, if my last MN payment was 4 days ago, will updating to v12 retain my slot for payment, or will it put me at the end of the line?
 

wsmithston

New Member
Aug 4, 2015
19
8
3
md5sum checks out:
% md5sum dash-0.12.0.44-linux64.tar.gz
1415c4abd8ac556d5b02ec277885f3e9 dash-0.12.0.44-linux64.tar.gz

but,

% sha256sum dash-0.12.0.44-linux64.tar.gz
d8341d0c8b843092c2aa01b11077f3e853aec978b5fb8aca5278d82bd5958336 dash-0.12.0.44-linux64.tar.gz

is longer than the one mentioned on:
https://www.dashpay.io/binaries/dash-0.12.0.44-linux64.tar.gz.DIGESTS.txt

Is the sha56sum that's reported there correct?
 
  • Like
Reactions: anonymous

MangledBlue

Well-known Member
Jun 28, 2014
1,246
678
183
USA
Are v11 masternodes still being paid?
Or only v12?

Also, if my last MN payment was 4 days ago, will updating to v12 retain my slot for payment, or will it put me at the end of the line?

You have until Sept 5th


I'll wait to upgrade until after I get paid :p
 
B

buster

Guest
Congrats to the Developers, testers and the community. This is a huge milestone we can all share and remember in the upcoming years.
 
  • Like
Reactions: Sub-Ether and moli

fible1

Well-known Member
Dash Core Team
Masternode Owner/Operator
May 11, 2014
710
722
163
Stuck 1 hour behind after -reindex anyone have this issue/tips?
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
Congrats to the Developers, testers and the community. This is a huge milestone we can all share and remember in the upcoming years.
Thanks, Bill. Looks like you got sunburn from the beach? :)
 
  • Like
Reactions: buster

LucD88

Member
Aug 15, 2014
75
49
58
Thanks for the quick reply guys, that worked! :)

But how do I tell if they're online? Right now that command displays:

".........txid1923819238-1" : "106.xxx.xxx.xxx:9999"
I'm not sure but I think the following command is the one I was looking for:
./dash-cli masternode status | grep -e SERVER_IP -e SERVER_IP -e etc.

EDIT:
Nope, it's not the correct command either. Writing ./dash-cli masternode status in the VPS terminal shows the following:
"vin" : "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, xxxxxx), coinbase )",
"service" : "106.xxx.xxx.xxx:9999",
"status" : 3,
"pubKeyMasternode" : "xxxxxxxxxxxxx",
"notCapableReason" : "Could not find suitable coins!"

Whatever that means, can anyone please explain?
 
  • Like
Reactions: moli

nmarley

Active Member
Jun 28, 2014
366
424
133
I'm concerned that I didn't upgrade correctly. Now I'm getting a status 3 and this message:

Code:
    $ ./current_dash/bin/dash-cli masternode status
    {
        "vin" : "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
        "service" : "XXX.XXX.XX.XX:9999",
        "status" : 3,
        "pubKeyMasternode" : "XXXXXX",
        "notCapableReason" : "Wallet is locked."
    }
I also don't have any "HotCold enabled" message in the debug log — but it is showing up in the "masternodelist full" output.

How can I be sure this is upgraded correctly? And how can I fix it if it's a problem?
 

nmarley

Active Member
Jun 28, 2014
366
424
133
walletpassphrase "<your_passphrase>" 60 unlocks your wallet for 60 seconds so you can start it within that time
I did that, twice. Output from 2nd time:

Code:
masternode start-many
{
    "overall" : "Successfully started 3 masternodes, failed to start 0, total 3",
    "detail" : {
        "status" : {
            "alias" : "mn1",
            "result" : "successful"
        },
        "status" : {
            "alias" : "mn2",
            "result" : "successful"
        },
        "status" : {
            "alias" : "mn3",
            "result" : "successful"
        }
    }
}

Edit: Still not working though, this is still an issue for me. I still get the "wallet is locked" message.
 
  • Like
Reactions: moli

GilAlexander

Member
Jun 26, 2014
84
23
48
I'm not sure but I think the following command is the one I was looking for:
./dash-cli masternode status | grep -e SERVER_IP -e SERVER_IP -e etc.

EDIT:
Nope, it's not the correct command either. Writing ./dash-cli masternode status in the VPS terminal shows the following:
"vin" : "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, xxxxxx), coinbase )",
"service" : "106.xxx.xxx.xxx:9999",
"status" : 3,
"pubKeyMasternode" : "xxxxxxxxxxxxx",
"notCapableReason" : "Could not find suitable coins!"

Whatever that means, can anyone please explain?
What do you want? This one?
./dash-cli masternodelist full | grep "SERVER_IP"
 
  • Like
Reactions: moli

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
I did that, twice. Output from 2nd time:

Code:
masternode start-many
{
    "overall" : "Successfully started 3 masternodes, failed to start 0, total 3",
    "detail" : {
        "status" : {
            "alias" : "mn1",
            "result" : "successful"
        },
        "status" : {
            "alias" : "mn2",
            "result" : "successful"
        },
        "status" : {
            "alias" : "mn3",
            "result" : "successful"
        }
    }
}

Edit: Still not working though, this is still an issue for me. I still get the "wallet is locked" message.
But you got your masternodes started successfully.
Try this: walletpassphrase "<your_passphrase>" 9999999
 

nmarley

Active Member
Jun 28, 2014
366
424
133
But you got your masternodes started successfully.
Try this: walletpassphrase "<your_passphrase>" 9999999
But that's not secure, and I shouldn't have to leave it unlocked for so long.

I've never had to wait more than a few seconds to see the "HotCold enabled" message before... currently I'm getting 2 different statuses, "Wallet is locked." and "Could not find suitable coins". Digging through the code now to see what's the issue. This was never a problem before with v11, and I'm inclined to think there's a bug somewhere... or something's gone wrong.

I'm also getting these random addresses in the "pubKeyMasternode" status field, that i've never seen before. Those aren't my masternode pubkeys. :/.

$ ../current_dash/bin/dash-cli masternode status
{
"vin" : "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
"service" : "XXX.XXX.XXX.XX:9999",
"status" : 3,
"pubKeyMasternode" : "XxLD1pQ8HjhMgrTTMBfdUBDsBbqnNXKqbt",
"notCapableReason" : "Could not find suitable coins!"
}

I'm wondering if the "Wallet locked" message is referring to my local wallet or the wallet associated with that address (above). I repeat: this is not one of my known addresses, I even just searched through every address on my own local "cold" wallet and it's not in there — so I don't care if I post it here.