V12 Release

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
I am with nmarley on this. The donation feature is really useful. I have wasted a lot of time from mistakenly spending coins from a masternode input by forgetting to use coin control. It is so much easier if the coins are automatically transferred to a separate spending wallet. I am sure the MN operators that manage other users coins will also use the donate feature pretty heavily. It was possible to run a paper wallet transaction that is used as masternode collateral, but now that will need to be cashed out again and again as they accumulate coins.
Masternode 1k inputs are now locked so it should be a non issue.
 
Last edited by a moderator:

nmarley

Active Member
Jun 28, 2014
366
424
133
I am with nmarley on this. The donation feature is really useful. I have wasted a lot of time from mistakenly spending coins from a masternode input by forgetting to use coin control. It is so much easier if the coins are automatically transferred to a separate spending wallet. I am sure the MN operators that manage other users coins will also use the donate feature pretty heavily. It was possible to run a paper wallet transaction that is used as masternode collateral, but now that will need to be cashed out again and again as they accumulate coins.
I opened a feature request here: https://github.com/dashpay/dash/issues/528, in case anyone else wants to weigh in on it.

Masternode 1k vins are now locked so it should be a non issue.
I don't understand what this statement means. I mean, I think you can set up multiple masternodes for the same address, just using different TX/indexes, but what if people (masternode operators) want to send funds to another address out-of-wallet like mentioned above?
 

Solarminer

Well-known Member
Apr 4, 2015
762
921
163
Masternode 1k vins are now locked so it should be a non issue.
That is good news. Thanks.
I opened a feature request here: https://github.com/dashpay/dash/issues/528, in case anyone else wants to weigh in on it.

I don't understand what this statement means. I mean, I think you can set up multiple masternodes for the same address, just using different TX/indexes, but what if people (masternode operators) want to send funds to another address out-of-wallet like mentioned above?
Thanks. Already commented on your feature request.

This is good news on the locking of masternode inputs. It means you have to unlock a specific masternode input before you can spend them. All the rewards or non masternode transactions will be spent first. Previously, if you just sent a transaction out from a wallet with a masternode, it would most likely pull some coins from a masternode input and shutdown your masternode. You would then need to transfer a full 1000 coins to another input and reset you transaction id on the local and remote daemon and wait for the confirmations....pain.

Of course, this doesn't help you out with monitoring your rewards... or give the ability to automatically transfer coins to a different account.
 
Last edited by a moderator:

emmo

New Member
May 23, 2014
37
11
8
Hi,
before v12 updates after del peers.dat on both sides the "1000" unlocked,but now won`t work,not good to remain so -any ideas ,thx :)
 

emmo

New Member
May 23, 2014
37
11
8
I mean on local wallet(for me its WIN 32),when choose "Inputs" the 1k DASH is locked,before v12 when delete both files(local and remote) peers.dat this fixing things,now this wont work,the 1k DASH still locked.I see that there are but a little scary that are inaccessible :)
 

drkrooster

Member
Dec 26, 2014
62
29
58
Malaysia
Windows wallet client seems to be stucked on 7hrs behind (synchronizing budget)
getinfo shows block 319551
Linux masternode seems to sync. up nicely to the same block, 319551 too
the 7 hrs behind in my clients is incorrect? 319551 should be up to date?
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
I mean on local wallet(for me its WIN 32),when choose "Inputs" the 1k DASH is locked,before v12 when delete both files(local and remote) peers.dat this fixing things,now this wont work,the 1k DASH still locked.
If you want to unlock the input, from the Coin Control, right click on it, and choose "unlock unspent".
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
I opened a feature request here: https://github.com/dashpay/dash/issues/528, in case anyone else wants to weigh in on it.
I don't understand what this statement means. I mean, I think you can set up multiple masternodes for the same address, just using different TX/indexes, but what if people (masternode operators) want to send funds to another address out-of-wallet like mentioned above?
If you want to send all of your mined coins to another wallet without touching the masternode vins, they're already locked but to make sure, click on the button "Select All", like from this screenshot:

upload_2015-8-15_0-17-34.png


Masternode inputs are locked now, you can even run Darksend on the wallet, just don't restart the masternodes while DS is running.
 

bertlebbert

Active Member
Jul 17, 2014
670
289
133
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.
Instances are slow? - You mean MNs (on sever)? That's a good question Tao... someone (not me) should know the answer.
 

nmarley

Active Member
Jun 28, 2014
366
424
133
If you want to send all of your mined coins to another wallet without touching the masternode vins, they're already locked but to make sure, click on the button "Select All", like from this screenshot:

Masternode inputs are locked now, you can even run Darksend on the wallet, just don't restart the masternodes while DS is running.
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.
 
  • Like
Reactions: Solarminer

bertlebbert

Active Member
Jul 17, 2014
670
289
133
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.
Donations was a popular feature, a good place to chime in on this is here: https://github.com/dashpay/dash/issues/528
 
  • Like
Reactions: Solarminer

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
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.
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.
 

Minotaur

Well-known Member
Foundation Member
Apr 7, 2014
452
1,079
263
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.
 
  • Like
Reactions: moli

minersday

Member
Apr 9, 2014
77
19
48
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.
 
Last edited by a moderator:

LucD88

Member
Aug 15, 2014
75
49
58
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?
 

cwnage

Member
Aug 1, 2015
41
22
48
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.
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).
 
  • Like
Reactions: moli and yidakee

cwnage

Member
Aug 1, 2015
41
22
48
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?

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))" | python2
to get an idea of the % of MNs upgraded.
 
Last edited by a moderator:
  • Like
Reactions: flare

Lariondos

Well-known Member
Foundation Member
Apr 8, 2014
89
61
158
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.
 
Last edited by a moderator:

crowning

Well-known Member
May 29, 2014
1,415
1,997
183
Alpha Centauri Bc
General remark:
After updating from v11 to v12 Masternodes drop off the list after 70 minutes...restarting them from the cold wallet fixes this.

I have one where this doesn't work, I'll investigate later.
 

GilAlexander

Member
Jun 26, 2014
84
23
48
After updating from v11 to v12 Masternodes drop off the list after 70 minutes
Have had mn's drop out twice after about 70-80 minutes
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
Aug 6, 2014
1,032
537
183
General remark:
After updating from v11 to v12 Masternodes drop off the list after 70 minutes...restarting them from the cold wallet fixes this.

I have one where this doesn't work, I'll investigate later.
Same here, one for the life of me will not start.
 
  • Like
Reactions: moli

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
I also hang on synchronizing budgets at 93%. Been that way for over 12 hours.
 

wackyD

Member
Jun 11, 2014
53
40
58
Can anyone please confirm that now the masternode 1000 is locked, we can safely anonymise other coins in the wallet without disturbing the 1000 set aside for the MN?
 
  • Like
Reactions: moli

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
Can anyone please confirm that now the masternode 1000 is locked, we can safely anonymise other coins in the wallet without disturbing the 1000 set aside for the MN?
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.
 
  • Like
Reactions: UdjinM6