Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 207. (Read 243417 times)

I posted this as a github issue 3 weeks ago. I think more will run into this as they transition away from PoDC to PoG. My workaround is to run two wallets - one for PoDC and one for PoG. I keep enough for 100% stake in PoDC and send the rest to PoG.

PODCUpdate: Unable to locate coins not marked as POG bankroll denominations.
https://github.com/biblepay/biblepay/issues/70

After running 1.1.9.6 for 24+ hours, just restart the wallet with -zapwallettxes=1 once and it will remove the orphaned transactions -- then going forward we should not see new ones appear.

This happened to me as well, except instead of a second bankroll I was unable to send a podcupdate until sending the coins to myself using coin control.

This is a self-moderated topic. You can start your own thread if you want.

Why are you still here? Your last racist and homophobic message to me will not be tolerated. I've reported you to BTC Talk mods and will ask them to kick you off this forum. That kind of hate speech is not tolerated.

ROBERT

if you will be deleting posts....ill be writing to Theymos that you makin joke from this forum and ppl   its FIRST warning to you you are very little person on this BTT,so Calm Down

Great work on the POG everyone.  Its a great complement to PODC and they balance each other well for different users.  The POG Engine is a powerful interface, and in using it I came up with some additional thoughts.

 - Would it be possible to number the list in the POG Engine so users can count the tithes? This would be useful for the custom view especially.

 - Another suggestion would be to consider rounding the max tithe (and enforcement of such) to the tenth or whole number to make it a bit more user friendly.  Not rounding individual tithes, just the limits.  Also could include rounding of the minimum age and minimum coin (maybe should be called note) amount.

For example (and I changed the verbiage and order a bit as a suggestion):

Max. Tithe: 9.5
Min. Coin Age (Days): 3.4
Min. Note Size: 1290

The order then is consistent with the 'tithe 9.5 3.4 1290' command.

Thanks for considering my suggestions, all!

using 1.1.9.6 (2019-02-27 15:39:43 -0600)

I did an exec bankroll of a single 500k BBP just now. It wouldn't let me run another exec bankroll on the change address. I had to send it to a different receiving address first. Then I was able to do an exec bankroll. you're saying it should work, but it doesn't work for me.

can anyone else reproduce my situation?

Here you go:

https://wiki.biblepay.org/Economics

Max. Tithe: 9.5
Min. Coin Age (Days): 3.4
Min. Note Size: 1290

The order then is consistent with the 'tithe 9.5 3.4 1290' command.

POG exec bankroll just skips locked and POG denominated amounts.

Better but still a lot of tithe too high reasons.

Sorry, my mistake. I finally found a case where my hypothesis was not correct:

http://explorer.biblepay.org/tx/1756b896769f70b0f0c98b8b72357a82bed6bbb13965230d79b6b8f9aa16bbe7

BBP tithe > 9.5 BBP but change is <1 BBP.

It is quirky the range goes somewhere between 0 to 2, but its not a bug. I would think change would be 0 to 1, but maybe that's just an incorrect assumption.

What is it that I'm not understanding - you seem to be saying the change is inconsistent, and I seem to be saying the change is based on the leftover amount after a denominated change amount (posted above) - but for some reason you quoted Capulo and said the same complaint over.  Its usually best in this situation to enter a github issue with the exact transaction ID so we can explain why you received that amount.

Regarding PODC, its PODC updates that skips pog denominated funds in PODC updates.  Not POGs exec bankroll that skips PODC update funds.    POG exec bankroll just skips locked and POG denominated amounts.

You seem to understand what I was saying. Maybe Rob didn't understand. It is not a big deal, but I think if you get change it should be consistent right? Less than 1 BBP? I don't know, I was thinking maybe one time you need min coin value 1899 and because you got too much change, your tithe was 1898, so you can not tithe. I know, silly worry...


Understandable. Still ran into some issues trying to bankroll. Even though I had enough non-tithe and non-PoDC to create my denominations, the PoDC balance gave the unable to bankroll error. You should be able to bankroll even if PoDC balance exists without touching PoDC funds. Even if PoDC goes away, those that migrate from PoDC to PoG, potentially have the same issue. They'd need to send their PoDC balance to a non-tithe and non-PoDC address and do the exec bankroll from there.

i have also txs with >1bpp back to tithes
lowest pile is 0.49990180 and highest 1.47982520. looks like  everything is +0.5bbp

On the idea about 'exec consolidate' to consolidate change, I was thinking we might not need it because 'exec bankroll' virtually does the same thing.  If a user runs exec bankroll the same process will sweep the change into a larger bank note.

Skipping this idea.

No thats not it - thats the first thing I designed into POG (as a requirement).
The difficulty level is actually set 4 blocks prior, and is good for 4 blocks.  So lets say we are working on block 100,000:
Diff is 2000; max tithe amount is 9.50.

In blocks 100,000 through 100,001 we honor tithes up to 9.50.

So thats not the reason for inducting an illegal tithe.

I thought it was simply .01 rounding when looking at 50 the other night (hence the reason we made the miner go down by .01 bbp in 1193).  But I do see today, in my personal tithing history over the last 205 blocks, I tithed by about .03 bbp too much (I have 30% bad tithes, 70% good tithes).  Note that fortunately since the pog pool pays out 90K~ or so per day everyone is still profitable in this playground.

But yes, we will get to the bottom of this to see why we have 30-50% illegal going into the report.

Looking at my report, it appears 90% of my errors are Legal=-3 (tithe_too_high) - this is the lions share of the problem.  The other 2 small issues we can deal with later.

Let me take a look at the blocks and see what could be causing this client to send out a tx that is .03 bbp too much.  One thing we should add to this report is the actual tithe parameters for the block next to the error- ill do that now.

EDIT 2:  On Capulos issue, bbp creating tiny < 1 bbp new pog denoms, that is actually not really a bug, I think its just a labeling issue.  When you receive change for a 9.50 tithe that came from a 10,000 bbp coin, we are sending the .6905 bbp back to "TITHES" and the 9900.0010 back to "change".  We really should send the TITHES change back to TITHES - but in the mean time this means you are getting the correct pog denoms back and they are working.  Another words we are just left with a nuisance of a lot of change that we need to consolidate manually once every couple of weeks.  This is another thing we could automate later ( we could say, exec consolidate, and it makes everything less than 1 bbp into one banknote for you automatically).