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

On the boolean :
"You can only tithe a maximum of "MaxTitheAmount" from addresses with amount>"MinCoinValue" AND (boolean) age>"MinCoinAge":  Yes, exactly, so you tithed less than the max allowed, you used a coin > than the minimum coin value required and that coin was older than the age required (for this diff level of this block), yes exactly.

As far as losing the address:  When you spend the coin, its actually no longer yours (its with the foundation) so technically you not only lost the age but you lost the whole coin but you received the change from the transaction (as a new transactionid with an age of zero).  But no, your address is re-usable.   The change from the transaction that came back to you (say your tithe was 10, the coin was 1000, your change was 990), that 990 that came back to you now has to re-age.  It is then tithable again after it meets the future difficulty level.

I guess that brings up an interesting point - most of the banknotes created, as they get spent will shrink, but they are still useful if they end up being tithes.

We will just need some automatic process that builds banknotes for people based on the most likely difficulty (IE maybe the average diff over the last 7 days), using a certain % of the wallet, if the feature is on.  (This will alleviate the complaints someone mentioned for Granny).

send money showing bigger number than pog room, and i was trying to tithe manualy and it takes this num. but i dont understand why it was sending only 8.1 when manualy i was able to sent 9 at same moment

For everyone who didn't catch this:  The goal of creating bank notes is to create a set of bills that meet the anticipated difficulty level in the future.

If you anticipate that difficulty will be 12,000 all the time, then knowing that you will need coins of a value > approx 7000 with an age > 9 days, you would then create bank notes of 7000 each.  So 1 coin is not 1 bbp, 1 coin is whatever is on the face of the bill (IE 7000 bbp).  Then this set of bank notes will meet the difficulty level.

I'll create an rpc command to show the 3 dimensions for each difficulty level with a step of 500 or so to give everyone an idea what the requirements are per range.

Ah thank you, that makes it much clearer. I think I understood the concept now. So basically you can only tithe a maximum of "MaxTitheAmount" from addresses with amount>"MinCoinValue" AND (boolean) age>"MinCoinAge". Additionally, am I right to assume that once an address has been used for tithing it looses its coin age, meaning that if I have a single address with 50k BBP I can NOT tithe several times per day from this? Then the bankroll feature is actually quite helpful.

On the ARMs: Yes, I have some Raspberries (RPi 3b and 3b+), some Orange Pis (O-Pi PC 2) and an Odroid C2.
They all run quite stable; the biggest issue with the BBP wallet right now is the I/O of the SD cards (especially when running multiple wallets) and the traffic if you use wifi.
However you need some cooling of course; I use those cheap mini-racks and some passive cooling on the chips with a 120mm FAN on the side of the rack.

Power-wise it's safe to say that none of those uses north of 5 watts.

I don't think the discrepency is in 3 places, I think the problem is:
The pog room and the 'titheinfo' rpc command actually show the right value for max_tithe (8.12 right now).  The Send Money max_tithe amount on the screen is rounded down to the nearest whole number (and that is a bug, but fortunately its rounded down).

Ill look into fixing that for the next leisure but first Ill check into the github issue someone reported.

info in send tab showing max tithe 9.00000. in pog room tam it is 9.12 and autotithe sending 8.1
what is wrong?

Update is available now in the usual PPA. Thanks!

Can you re-read https://discontinuo.us/biblepay-unofficial-wiki/proof-of-giving/exec-bankroll-example ?

I added a screenshot and more explanation. Let me know if anything is unclear. Anyone (that means you) can revise the wiki like I just did.


I'm also glad you got them installed on the ARMs. Can you tell me what kind of hardware setup you have? Someone mentioned running Rasp Pi. Wouldn't that be cool? Be eco friendly (being good stewards of the Earth as God called us to be) and being able to help secure the BiblePay PoW network and also submit donations for PoG rewards. All using maybe 2-5 watts!

Could anyone please explain again (from scratch) what the heck the "bankroll" feature is all about?
Why should I create a certain amount of fixed BBP "changes" when my wallet can just use random amounts of coins I have?
I read "https://discontinuo.us/biblepay-unofficial-wiki/proof-of-giving/exec-bankroll-example" but still have no idea what the purpose of all of this is. Why is it benefitial to have a large amount of equal-coin bankrolls??

Additionally when Rob says does that mean that from now on it only makes sense to create bankrolls of 10 (or less)? Just for the fun of it I created 100x10BBP denominations. What will the effect of this be in relation to my current tithing? (My wallet randomly spits out denoms of 7 or 8 bbp).

Finally, I find it really confusing to use the term "coin" for a certain amount of BBP used as tithe. For me (and I think most crypto guys) 1 coin == 1 BBP!

P. S.: Thank you MIP for the POG Engine Room in the wallet. This is really interesting, although I don't think it will make things easier to understand for new users.

P.P.S.: Also thanks for the quick compiling of 1191 on the PPA. Just updated my ARMs.

Please check this one

https://launchpad.net/~biblepay-official/+archive/ubuntu/mainnet

Sure?


There is a new PPA repository?

Unfortunate,  but I do understand the reasoning...   (still is cheaper than the .5? they were asking before..)

Hopefully things are stabilizing,  looking forward to the next phase of bbp.

Whoever created 250 POG accounts in the pool, as you can see, each of these payments will not sum to more than if you had 250 distinct tithing coins available on a single wallet, so as you can see there is no advantage to doing this (You can set tithe=5 on your controller, if you have 250 coins, and it will try to tithe every 5 minutes which should be often enough to simulate this same environment).  However remember, once we have more than 1000 users in the pool, there will be no advantage to tithing that frequently - at that point the idea is to save up coin-age so that we are not a chatty network.

But I'm happy someone did go through this exercise to stress test POG early.

The primary change that will occur this weekend is all the tithes over 10 bbp will dissapear and the POG payment per user should increase, and also, all the coins will have to meet the difficulty level, meaning a lot of these small tithes will also dissapear (as I dont think they met the age requirement) -- and that should finally make the POG environment sane and fair for everyone.

EDIT:  I didn't want to give the impression to anyone - that tithing frequently earns you more BBP.  You'll see it does not.  Every coin that is spent has to re-age before having the ability to be re-spent again after Saturday.  So all these extra frequent tithe entries are going to dissapear on the weekend.

** Reminder to upgrade to 1.1.8.9+ before block 103175 **

Only 20% of our network has upgraded.  This is a reminder that everyone must upgrade before 103175 or your node will fork onto the invalid chain.

GIN, SX, and CX have upgraded already.  CryptoBridge is choosing to put us in maintenance.
I entered a ticket with CCEX.

We have other tools that sum, like engine room, titheinfo, and when you click "Tithe" from the send money GUI.

This list is one row per coin.  Its useful because in POG, each tithe must be One Coin, and each of those coins have a chance to be a valid tithe especially at low difficulty levels.

On the weekend when all this starts, the difficulty should be pretty low (because of everyones low tithes).  So I look forward to POG working very well.

Age is calculated by:  How old is the individual coin you own (IE from Today - the Date you received the coin).

BiblePay - v1.1.9.1
Leisure Upgrade

- Release POG Engine Room (MIP)

Mac and PPA's have been released also.

Why so many different coin/ages ?? Why they don't summ? How Age are calculated?

Thank you very much, Togo!

I agree - the negative energy just hurts everyone and slows us all down.  In a perfect world devs would work 24 hours a day and be immune to negative statements but we are all human here and we are hurt by some of the views expressed (in both ways - from me towards the community and from the community to me). 

However remember we are all living in the age of grace, and we should forgive one another and start over.   Since Jesus forgave us of our sins we should be quick to forgive others.

To a new - Brighter Future, we are Free Indeed!

I feel we should also allow auto (IE 1) to work properly, and depending on user count (starting low) yes auto should tithe more frequently, so Ill be glad to send a spork to make the default more like 7 minutes when we start out later this weekend.  (Its already set up as a spork).

Thanks a lot Togo for taking the time to deal with CryptoBridge.  It's a shame, on one hand I can understand the problem (when coins take advantage of the situation) but I also think there should be exceptions (IE emergencies beyond our control), and additionally, a $100 fee instead of $1000 for an upgrade.  Maybe they should pay the IT technician a 50% commission on upgrades and cap it for marketcaps < 1,000,000. 

Oh well, could you please tell them to put us in maintenance until our next mandatory upgrade?