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

V12 Release

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
 
Congrats to the Developers, testers and the community. This is a huge milestone we can all share and remember in the upcoming years.
 
Stuck 1 hour behind after -reindex anyone have this issue/tips?
 
On Slack ...

flare[5:34 PM]Enforcement is off, so it does not matter what version you are on - payments are distributed by random

Not according to my scripts:

dash-cli getblocktemplate

...
"payee" : "XrUz5xZR8QExjmZyg3DeTCEE2Ab3SMBK6N",
"payee_amount" : 232142850,
"masternode_payments" : true,
"enforce_masternode_payments" : true
...
 
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?
 
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?
 
I'm concerned that I didn't upgrade correctly. Now I'm getting a status 3 and this message:
Code:
        "notCapableReason" : "Wallet is locked."

walletpassphrase "<your_passphrase>" 60 unlocks your wallet for 60 seconds so you can start it within that time
 
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.
 
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"
 
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
 
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.
 
Back
Top