Quote from: sunk818 on February 14, 2019, 08:45:23 PM

Quote from: cryptocadxyz on February 14, 2019, 07:56:39 PM

No, what was happening, was that I had bankrolled a whole bunch of coins but left just enough for PODC. However, PODC kept saying insufficient balance. I looked at the Coin Input and saw that my bankrolled coins were nicely separated from the amount I wanted to save for PODC, so I couldn't figure out what was wrong. I ended up selecting all the coins in my NON-Tithe addresses and sending them to a single address, then I noticed that shortly after, a single automatic PODC update would go out. But after that, it would stop completely. Each day, I would have to manually consolidate all my NON-TITHE addresses into one wallet for PODC to update. Eventually, I thought there might be a problem with the bankrolled coins, so I selected those as well and consolidated everything into one single wallet address. PODC automatic updates now work fine, however, now it always takes the whole balance regardless of what I specify in UTXOOverride. POG no longer works because my entire coin age is always reset.

Perhaps why my PODC updates were failing is because somehow my wallet was not reading the utxooverride value correctly in some cases and was trying to send out a larger amount than what I had specified.

I just tried bankrolling a bunch of coins again and will see in a little while if I continue to have problems.

Sounds like the issue I posted here:
https://github.com/biblepay/biblepay/issues/70

I suggest you separate PoG from PoDC.

The issue will resolve itself over time. There's a vote to potentially remove PoDC from BiblePay. If the proposal passes, there's no point in using dev hours to make PoDC and PoG interoperate in the same wallet.

Anyway, if you want to split PoDC and PoG, you can send PoDC stake a second wallet. This worked for me in Windows 10:
https://discontinuo.us/biblepay-unofficial-wiki/how-to-run-multiple-biblepay-wallets

If anything is unclear, feel free to edit the wiki. Anyone can edit it anonymous and even upload images.

And also just to clarify, the PODC update code might have been accidentally picking some of the bankroll outputs; so let's see if this problem is resolved in the next version.
I can say for sure the next version will not spend bankroll transaction outputs for 'exec bankroll' or podcupdates (as I did some testing last night with the new version).