BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

[sunk818]

Code:

  "Total Legal Tithes Amount": 566.35999992,
  "Total Illegal Tithes Amount": 251.27999999,
  "Total Legal Tithe Count": 59,
  "Total Illegal Tithe Count": 26

Better but still a lot of tithe too high reasons.

[bible_pay]

BiblePay
1.1.9.6 - Leisure Upgrade

- Ensure pogpool is up to date before auto-tithing
- Auto tithe 5% less than max allowed, with 5% more age.  This is
configurable by the user by setting pogbuffer=.05 (the default is
already set to .05).  Set to 0 to disable.
- Fix titheinfo ROI negative figure.
- Make tithe change return to "TITHES" address.
- Enhance exec pogaudit to include actual tithe difficulty parameters

[bible_pay]

I'm enjoying the new higher POW difficulty I'm seeing (6200 right now).  This is good for our security.

I'm not sure yet, but it appears POG is slowly attracting more users.

[bible_pay]

Code:

  "Total Legal Tithes Amount": 566.35999992,
  "Total Illegal Tithes Amount": 251.27999999,
  "Total Legal Tithe Count": 59,
  "Total Illegal Tithe Count": 26

Better but still a lot of tithe too high reasons.

The new version should make a big difference.

[bbptoshi]

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!

[sunk818]

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.

Whatever it is, we need to make the terms consistent across all of the UI and documentation. I personally am fine with min coin age and min coin value. It rolls off the tongue easy enough.

if we used existing wallet data, # of confirmations could have worked too. I understand the concept of min coin age, but I have to do math in my head, or look at pog engine room, or use a debug console command. min coin value is obviously there in the coin inputs screen too. Sadly, we are probably too far along to get away from min coin age I think and we have workarounds like pogbuffer to mitigate these tithing issues many of us are facing. # of confirmations an integer and not a moving target like min coin age.

Glad you like PoG Engine, but I find it extremely confusing. The checkboxes across the top and how you get rows is not intuitive at all. The only two features I understand are create bankroll (exec bankroll) and tithe (tithe). The summary on the right is useful too.

POG exec bankroll just skips locked and POG denominated amounts.

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?

[afeno]

What is the actual reward distribution now that we have POG in place?

This is what I found in the official BBP webpage but POG is not listed.

10% Charity
5% IT
2.5% PR (Public Relation campaigns)
2.5% P2P (Orphan Letter Writing, Pay To Preach, Pay to be a Priest, FAQ Writers, Social Media)
38.5% Proof of Distributed Computing (PODC) [Cancer Research]
3% Proof of Work (POW)
38.5% Masternodes (Sanctuaries)

Can someone clarify how are the coins distributed?

Thank you!

Here you go:

https://wiki.biblepay.org/Economics

Thank you Rob! What is the plan/future of PODC?

[bbptoshi]

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?

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.

I also agree about the checkboxes at the top.  I only understand that checking custom lets you see hypothetical scenarios by changing the parameters.

[bible_pay]

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!

Thanks for the suggestions.  On the pog leaderboard UI, we do have the tithe count so we could probably add a column to it.
On the tithe max allowed amount snapping to nearest 10th idea, its a pretty good idea (in that we could probably quote the amounts rounded down, while the hard consensus allows up to the internal amount)- its certainly interesting.

Could you put an enhancement suggestion in github so this does not get lost?
https://github.com/biblepay/biblepay/issues

[sunk818]

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

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.

[bible_pay]

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.

[bible_pay]

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

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.

Plus he is on the ban list.
Slovakia, see the ban list on the bottom of the OP post.

[sunk818]

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?

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.

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

[sunk818]

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.

If I run tithe=2 , I run into orphans sometimes.
I think I am trying to tithe too fast?
Should I run two wallets then?
I think you mentioned there's a limit of 2 tithes per blocks from same address?
What do you think of InstantSend as default? Would that help with PoG difficulty window?

[bible_pay]

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?

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.

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

No, actually what you mean is you entered it 3 weeks ago and we helped you, and you closed it 19 days ago and re-opened it 2 days ago, correct?

So please don't insinuate that we aren't trying to fix production issues.  I'll go out on a limb and say I think we have a cleaner environment in github with production support issues than 75% of the communities issues lists.  Especially when dealing with prod support emergencies.

[bible_pay]

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.

If I run tithe=2 , I run into orphans sometimes.
I think I am trying to tithe too fast?
Should I run two wallets then?
I think you mentioned there's a limit of 2 tithes per blocks from same address?
What do you think of InstantSend as default? Would that help with PoG difficulty window?

What version are you running first?  Its only been out for 12 hours.

No, No, No, No.

[bible_pay]

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?

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.

I also agree about the checkboxes at the top.  I only understand that checking custom lets you see hypothetical scenarios by changing the parameters.

When you sent coins to yourself via coin-control to enable yourself to spend the coins in a PODC update, please tell us the exact amounts to had to free.
If they were change for pog bankroll denoms, then they would not have worked in a PODC update anyway (as PODC updates skip those).

If you can reproduce the scenario again, please enter a github with a screen shot of the coin control before you reallocate, an actual PODC update error message, and the output of exec getdimensionalcoins 0 0 so we can see the actual coins involved in the failed podc update.

[bible_pay]

What is the actual reward distribution now that we have POG in place?

This is what I found in the official BBP webpage but POG is not listed.

10% Charity
5% IT
2.5% PR (Public Relation campaigns)
2.5% P2P (Orphan Letter Writing, Pay To Preach, Pay to be a Priest, FAQ Writers, Social Media)
38.5% Proof of Distributed Computing (PODC) [Cancer Research]
3% Proof of Work (POW)
38.5% Masternodes (Sanctuaries)

Can someone clarify how are the coins distributed?

Thank you!

Here you go:

https://wiki.biblepay.org/Economics

Thank you Rob! What is the plan/future of PODC?

I'm going to enter a topic for it later today - and we can discuss its future.

[sunk818]

So please don't insinuate that we aren't trying to fix production issues.  I'll go out on a limb and say I think we have a cleaner environment in github with production support issues than 75% of the communities issues lists.  Especially when dealing with prod support emergencies.

Please don't take it the wrong way. We appreciate all that you do. We all want a better BiblePay product, right? I closed the issue because I figured out a workaround (make a separate PoG wallet). But I still have problems with exec bankroll (different circumstance). I'm just trying to help bbptoshi by explaining what I did. I doubt anyone thinks you aren't fixing production issues. Look at all the fixes and new features we've in the last few weeks!

What version are you running first?  Its only been out for 12 hours.

I'll let 1.1.9.6 run a bit then. never mind.

[bible_pay]

So please don't insinuate that we aren't trying to fix production issues.  I'll go out on a limb and say I think we have a cleaner environment in github with production support issues than 75% of the communities issues lists.  Especially when dealing with prod support emergencies.

Please don't take it the wrong way. We appreciate all that you do. We all want a better BiblePay product, right? I closed the issue because I figured out a workaround (make a separate PoG wallet). But I still have problems with exec bankroll (different circumstance). I'm just trying to help bbptoshi by explaining what I did. I doubt anyone thinks you aren't fixing production issues. Look at all the fixes and new features we've in the last few weeks!

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.

If I run tithe=2 , I run into orphans sometimes.
I think I am trying to tithe too fast?
Should I run two wallets then?
I think you mentioned there's a limit of 2 tithes per blocks from same address?
What do you think of InstantSend as default? Would that help with PoG difficulty window?

What version are you running first?  Its only been out for 12 hours.

Was on 1.1.9.5 and now I'm tithing on 1.1.9.6. Still ran into some tithes too high

this one is interesting... tithe amount is 9.79 and max tithe is 9.79, but considered Illegal tithe - tithe too high?

Looks like block PoG diff was 9.78999999 so that makes sense now.

"xxx": "Legal: -3 [TITHE_TOO_HIGH], Amount: 9.79, Height: 104236, Spent_Coin_Value: 1046.00, 9212fd788f03968e2dfc81372bf9e4b779f510e980bf0303525284d45b257715-76, Age: 1.55, NickName: xxx
[Max Tithe Amt: 9.79, Min Age: 1.51, Min Coin Value: 530.04]",

http://explorer.biblepay.org/api/getblock?hash=efa857e0928fdc37c970cbd13337d80ecb96158342502524744ac35ee0650c6a

Code:

  "block_tithes": 617.8805,
  "24_hour_tithes": 7509.68399948,
  "pog_difficulty": 1386.882573590632,
  "min_coin_age": 1.51,
  "min_coin_amt": 530.04,
  "max_tithe_amount": 9.78999999,

OK, just try to proofread your post and think what others feel when you click the red button.  OK, thats cool.

Anyway, on that tithe you posted (-3) that was not from 1196.  I can tell because 1196 sends out .05% less than the TDP params for the block.  So I suggest going through your list - and auditing blocks up to your cutover point.  Thats why I said wait 24 hours- then your list will be clean with 1196.  EDIT: Yes - its possible on 1195 that a tithe that is rounded down is over the limit by .000001 satoshi.