Since the UTXOWeight is set automatically, should I remove the uxtoamount=51000 in the biblepay.conf file?
Yes, try removing it, and just see if your 'exec utxoreport cpid' looks OK in about 8 hours
.
Yes, but beware
I have running two wallets 24/7 (just for sure if 1 of them will fall down
) on linux 1.1.1.3 with setted utxoamount.
Then I've updated my win wallet to 1.1.1.7 and removed utxoamount to make it automatically
But then my win wallet made 1 podc update only with 11k BBP (it is less than 10% of my RAC), but I have seen it and I've made corection with podc update true. What is worst it made this bad podc update again (with 20k BBP) but I've not noticed it and now I have in next superblock only 10% utxo weight even if my others podcupdates from linux machines are correct. It looks, that my bad podcupdate was in worst time when new block rewards was formed
Now I've set my win wallet to utxooverride=-1, so I hope that it was for last time
Rob, maybe it will be really good to have there some rule, that if there was podcupdate in last for example 6 hours don't make the new one. I think that the problem was, that the last podcupdate from linux machine was less than 6 block from prior and my stakebalance was only 20k.
Well the thing is we really just want them to run one controller wallet for the most part. Currently, the main controller wallet does check the depth of the last transmission so it does not over-send these podcupdates unless one is due.
The lions share of the problem is people who run copies of the wallet.dat, the sub-nodes - we dont want those sending podc updates at all, so they just have to set the key 'utxooverride=-1' on those copy-cat nodes.
(I dont want to add a new rule because technically, we would not know which "last" podc to honor"). So its better if we tell people:
If you are going to copy your wallet.dat out to another machine, please set this key to prevent podc updates on that sub-node.
The other part of the issue is Id rather have the default be like it is now, where the controller sends a PODC update by default if it has an associated CPID in the wallet... Thats how it is now for ease of use for the multitudes.
So unfortunately I dont have an easy way to make this automatic for heat miners except: They have to do a little more work if they are heat miners