it helped me, probably not only me, you are super guys, that's what I love this community
V12 Release
- Thread starter eduffield
- Start date
TaoOfSatoshi
Well-known member
Guys, does V12 use more memory than V11? My instances are slower than cold molasses. If so, what is the the recommended minimum memory for V12?
Thanks.
Thanks.
bertlebbert
Well-known member
Instances are slow? - You mean MNs (on sever)? That's a good question Tao... someone (not me) should know the answer.
But why remove the donations feature? I don't want to have to manually move funds, there are many other uses for this besides donating, as stated by thesolarminer. What about the instances where MN operators manage other users coins? Those other users might be used to seeing funds mined straight to them -- now they have to trust that the MN operator will send them, and not forget/be on-time, etc. Many uses for this feature.
bertlebbert
Well-known member
Donations was a popular feature, a good place to chime in on this is here: https://github.com/dashpay/dash/issues/528
moli
Well-known member
I do not know why, except that now we're having the budget system implemented, we don't have to depend on donations to pay for our devs, projects, marketing.. etc. and maybe that is why this donation feature is abolished. But I agree it is a nice feature to have, and i'm sure some of us still would like to donate some of our MN rewards to a favorite dev. I'm sure the devs will look into your request on github.
As far as I understand it was a security concern. Making it OK for the payments to go to a different address could open unexpected attack vectors, that is what I gathered but I am sure eduffield can clarify.
minersday
Member
dash-cli masternode debug
Not capable masternode: Could not find suitable coins!
setup is cold-wallet.
again, cannot start masternode, and the 1000 dash is untouchable in the 0-address.
but there are multiple vins and vouts in there also.
update: again, changed the IP and generated a new key, so it started.
Not capable masternode: Could not find suitable coins!
setup is cold-wallet.
again, cannot start masternode, and the 1000 dash is untouchable in the 0-address.
but there are multiple vins and vouts in there also.
update: again, changed the IP and generated a new key, so it started.
Last edited by a moderator:
LucD88
Member
In previous (v11) releases the "masternode.conf" file was always placed in the same folder as the wallet-QT. Now with v12 it seems that there's a "masternode.conf" file in both the wallet-QT folder and the data folder.
The one in the wallet-QT folder is the one I used with v11, it has things like my privkey and Masternode address. The (new) one in the data folder has some default values, or well.. I never edit that file.
So, what to do with any of them? Could that be the cause for my Masternodes dropping offline/not starting properly?
The one in the wallet-QT folder is the one I used with v11, it has things like my privkey and Masternode address. The (new) one in the data folder has some default values, or well.. I never edit that file.
So, what to do with any of them? Could that be the cause for my Masternodes dropping offline/not starting properly?
Don't trust that message, it rarely is correct. It's the "last" message, and because of reindexing, doesnt know coins exist, and does this.
Type "masternode status" (new command) and look for status 4.
Also look for the Pings in debug.log (that means you're broadcasting to the network - happens roughly once a minute).
Looks like some people are running pre-0.12.0.44 masternodes as I see 70102 protocol in the list. Is this just to help bridge the migration?
to get an idea of the % of MNs upgraded.
Code:
echo "updated=$( dash-cli masternodelist protocol | grep 7010[23] | wc -l ); total=float( $( dash-cli masternode count ) ); print(\"%.2f%% (%d/%d)\" % (100 * updated/total, updated, total))" | python2to get an idea of the % of MNs upgraded.
Last edited by a moderator:
It's a bit confusing. If I use the official 0.12.0.44 linux 64 release, I'm running with protocol version 70102. If I use the last 0.12.0.44 from testnet, I get protocol version 70103. So which version is the right one for mainnet now?
Edit: The windows release version is on 70103, the linux 64 bit isn't.
Edit: The windows release version is on 70103, the linux 64 bit isn't.
Last edited by a moderator:
GilAlexander
Member
Same for me. After restarting they appear in ./dash-cli masternodelist full as ENABLED, then as EXPIRED and then dissapear.
./dash-cli masternode status on both hot and cold wallets at all the moments shows smth like
{
"vin" : "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
"service" : "goodmnip:9999",
"status" : 3,
"pubKeyMasternode" : "XkdxDim3T4NsBH5Tij8TRwNNJA47qtujj7", <- dunno what is it
"notCapableReason" : "Could not find suitable coins!"
}
Is it because unable to "sync masternodes list" and will it fix itself after the whole network updated?
oblox
Well-known member
Same here, one for the life of me will not start.
moli
Well-known member
Yes. Masternodes are locked. You can run DS on your mn wallet, but DO NOT restart your Masternodes while DS is running.
If you're not sure preferably i'd suggest you to run DS on a different wallet with no MNs.