Quote from: znjrols5 on April 05, 2018, 06:40:48 AM

Quote from: bible_pay on April 04, 2018, 10:38:13 PM

Quote from: dave_bbp on April 04, 2018, 10:32:01 PM

Quote from: bible_pay on April 03, 2018, 09:57:11 PM

Wait, I know the problem dude.

Before 1.1.1.7 the wallet was not smart enough to parse negative numbers.

You need 1.1.1.7 on the 2nd and 3rd miners with 'utxooverride=-1' set, then it will actually interpret the negative number as a number, and then heed the warning not to stake PODC update... Yes I think you need Lights update

.

I updated all the heat miners to 1.1.1.8, but unfortunately this didn't change anything. The wallet again sent out the 3 podcupdates for 1/3 of the stakebalance each. For now I stopped them again, I think I will just start BOINCing on a second CPID for this purpose, associate a second wallet with this second CPID and copy this to the heat miners. Positive side-effect: I don't have my main balance staked on permanently unlocked wallets. Wink

Ok, thanks, I will debug the code and find an easy way to turn off UTXO updates...

I actually had the same problem, had many machines heat mining, and there were always 3 podcupdates in groups (don't know why 3 thou). After updating and adding utxooverride=-1, this was fixed. Unfortunately, my controller wallet also doesn't automatically sends podcupdates, don't know why, monitoring for now and sending manual ones...

Hmmm... on your main controller, if you wait about 4 hours then check the log... look for "PODCUpdate"... see if any error message exists.
Your getmininginfo should show a HPS reading > 0.

Ill see if I can come up with something easy to show that we tried to send them. Possibly a global variable we increment every time we try to process one (IE TotalPODCUpdates: 3) in getmininginfo, then at least people will know they are on autopilot.

Ill also add a second key something like 'disablepodc=1' for Dave. Although Dave the utxoooverride=-1 is working for ZNJ...