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

[sunk818]

Dear Rob --

With a heavy heart, I must ask how does one go about reducing/removing POOM sponsorship as I have no funds to continue past Jan 2020?

Due to the price of BBP being at 1 sat, it currently costs 314k BBP for $25 Kairos, and 502k BBP for $40 CameroonONE. I paid for 10 Kairos children up to Jan 2020, but could not meet all my obligations for CameroonONE. I will have spent all the BBP I've accumulated since I started with BiblePay to sponsor the orphans. Let's pray that God's will be done and that the children continue to be supported in some way. You already have a heavy load running BiblePay and sponsoring many children with your big heart, so I don't think anyone expects you to sponsor additional children. Hopefully, more diverse set of sponsors can be involved. I'm sad at the situation that I can not serve the current orphans, but do not regret using the BBP to benefit the orphans.

Thanks,
Sun

If you want to be part of this intelligent conversation you have to be honest Sun.

Okay, you're right. We added many kids very quickly and pay out per child crashed. Fair enough. The economics is right. I'll shore up the difference and use up whatever BBP I have in my wallet. I rather go to 0 and support the orphans as long as I can.

64 CameroonONE children @ $40 = $2,560
21 Kairos kids @ $25 = $525

At current prices, $3085 % 0.00012840 BBP/USD requires 24M BBP.

Is CameroonONE not selling their BBP since Oct 26, 2019? They have a balance of almost 30M BBP.

Should they be selling their BBP on the market every month?

https://chainz.cryptoid.info/bbp/address.dws?BHRiFZYUpHj2r3gxw7pHyvByTUk1dGb8vz.htm
https://chainz.cryptoid.info/bbp/address.dws?B4rwnBcrcr8pqHFFz9oXRcmXEy8g1bZjTV.htm

Thanks for meeting me halfway Sun, and I apologize for being rough around the edges sometimes.

The constant sell pressure is bad.  On one hand, we wanted new charitable people from the outside (like Donald Trump etc) to sponsor orphans with their credit card through paypal.  Then we give them Biblepay, and that keeps the sell pressure off.

But of course with reality kicking in, and the ease of using the poom payments feature, in reality we pay every month with BBP (partially to make BBP a useful currency).

So yes its a conundrum and there really is no easy answer, short of mass adoption and appealing to those who already have a budget to pay for the orphan via Fiat...

Let me check into the increasing balance, thanks for raising the concern.

[bible_pay]

have some questions:
auto sendgscc is sent only at this height? "next_podc_gsc_transmission": 166767
so if i have wallet off and stat it later, it is not send?
it looks like this

second: i did some manual sents because of previous
tx id cfb2e2bf3ba18efbb07e9a1bb9e7c1549519b479e12bd445a3bd6f727df03146
but then i leave wallet online and autosenddid c8cf23f5e888ebe9628768fef5130ff51ee525422ff0f561099a793d5dccb175
it sent almost nothing, so when previous tx expired i disappeared from leaderboard
is this ok?

third:
can i set somehow that sendgscc will be send more times per day or send with specific amount at autosend height?

1) If you start the wallet after the exec rac sendgscc height, it will not auto send one.
2) We always calculate your coin-age-requirement based off of 'exec rac', so we will always calculate it correctly, so it should not send a .10 tx for wcg if you need a big reqt.  That I believe is a bug that is being fixed this week (thats the same as the unlink bug).  So, I believe you can scratch this one off when that liesure is released.
3) We have a key called 'dailygscfrequency'.  This is set by default at 205.  If you decrease it to 100 for example, you would send one out every 100 blocks.  That might be what you need and will also handle most late starts.

If set dailygscfrequency=100 , does this have any negative impact on wcg points on the leaderboard at ll? I thought there was some warning about sending wcg too often?

Also, what happens to cameroon-one and kairos with this setting?

Since we add coin-age once per day, sending two per day is not a problem.  I'm not aware of a warning, except for total network inefficiency.

With Cameroon-one nothing important happens, biblepay gets two records in per day, but we pay only once - off of the sum of the record.

[bible_pay]

Dear Rob --

With a heavy heart, I must ask how does one go about reducing/removing POOM sponsorship as I have no funds to continue past Jan 2020?

Due to the price of BBP being at 1 sat, it currently costs 314k BBP for $25 Kairos, and 502k BBP for $40 CameroonONE. I paid for 10 Kairos children up to Jan 2020, but could not meet all my obligations for CameroonONE. I will have spent all the BBP I've accumulated since I started with BiblePay to sponsor the orphans. Let's pray that God's will be done and that the children continue to be supported in some way. You already have a heavy load running BiblePay and sponsoring many children with your big heart, so I don't think anyone expects you to sponsor additional children. Hopefully, more diverse set of sponsors can be involved. I'm sad at the situation that I can not serve the current orphans, but do not regret using the BBP to benefit the orphans.

Thanks,
Sun

If you want to be part of this intelligent conversation you have to be honest Sun.

Okay, you're right. We added many kids very quickly and pay out per child crashed. Fair enough. The economics is right. I'll shore up the difference and use up whatever BBP I have in my wallet. I rather go to 0 and support the orphans as long as I can.

64 CameroonONE children @ $40 = $2,560
21 Kairos kids @ $25 = $525

At current prices, $3085 % 0.00012840 BBP/USD requires 24M BBP.

Is CameroonONE not selling their BBP since Oct 26, 2019? They have a balance of almost 30M BBP.

Should they be selling their BBP on the market every month?

https://chainz.cryptoid.info/bbp/address.dws?BHRiFZYUpHj2r3gxw7pHyvByTUk1dGb8vz.htm
https://chainz.cryptoid.info/bbp/address.dws?B4rwnBcrcr8pqHFFz9oXRcmXEy8g1bZjTV.htm

Thanks for meeting me halfway Sun, and I apologize for being rough around the edges sometimes.

The constant sell pressure is bad.  On one hand, we wanted new charitable people from the outside (like Donald Trump etc) to sponsor orphans with their credit card through paypal.  Then we give them Biblepay, and that keeps the sell pressure off.

But of course with reality kicking in, and the ease of using the poom payments feature, in reality we pay every month with BBP (partially to make BBP a useful currency).

So yes its a conundrum and there really is no easy answer, short of mass adoption and appealing to those who already have a budget to pay for the orphan via Fiat...

Let me check into the increasing balance, thanks for raising the concern.

1) It's OK -  I don't think anyone is going to have hard feelings over it.
2) Regarding 1 satoshi, I felt the pinch myself and spent 10% of my biblepay this morning just paying for the children, and I bought the biblepay at a considerably higher price.
3) Do realize that paying via BBP for POOM was only for convenience sake.  Realize that the process of sponsoring a child was technically supposed to be more like this:  I can afford to sponsor the child and intend to pay with Fiat (paypal, credit card, etc), and with BBP down turns we normally would have expected you to pay this month in credit card and keep the child.  The poom sponsorships are for people who want to sponsor long term children and 'in parallel recoup' mining rewards in bbp.  Like I said there is no hard feelings and I think they will understand at cameroon-one when we cancel children.
4) I personally do intend to pay via credit card in a couple months if BBP is still down.  
5) Let me look into a POOM cancellation process, if we have one.  If we don't have one, we will make one.

6) Btw, Todd checked into the 30 million bbp balance and explained that the lingering balance you see is the SX trading balance (on the SX side).  Cameroon already sold all the bbp and has a 0 balance.

[slovakia]

is any problem with wcg rewards?

didnt get it

all is ok

wcg tx sent
exec rac ok
wallet open

Looks like you didnt send enough on 166564:

exec sentgsc B5REkwbrhweML86cxfRaT3HTzZS14trsUD

You sent 4.1MM the day before, 27K on 166564, then back to 8.01 MM on 166769 and 32MM today.

So there is 1 missing (todays).

but this is bug on BBP

capulo same problem

now WCG TX is OK with almost 6M

[harrisvan87]

Everyday BBP make new bottom price...

[sunk818]

Now with DIP3 sanctuaries, it seems there's an opportunity for charities to receive BBP directly while the sanctuary owner retains voting control.

[bible_pay]

Everyday BBP make new bottom price...

I think we need to remove the sell pressure from our charity model.

[bible_pay]

** Sell pressure mitigation **

On one hand its easy to realize how our currency goes down in price more than it goes up.  We've given $214,000 to orphan charity directly from the blockchain since inception.

Over the last 6 months especially with POOM, we've adopted a model where each charity accepts biblepay directly from each POOM sponsorship payment.

I think we need to immediately reverse this and ask our charities (Cameroon & Kairos) to not accept biblepay for orphan payments.  (Even though it sounded like a good idea, lets make a use case for our cryptocurrency, it actually added more sell pressure).

So if we do that, this will require sponsors to use a credit card or paypal to sponsor the child to remain in poom.  The fiat would be considered a tax deductible contribution.  

[bible_pay]

** Leisure upgrade coming in the next 72 hours **



The next leisure upgrade contains these features:

1)  Removing the glitch where 'exec rac' becomes unlinked. 
2)  Fixing the calculation where a user receives reduced RAC (due to insufficient escrow) to be more refined (this allows RAC levels to drop all the way to 1 rac).  Note this requires a mandatory for the sancs, so what we will do is make it so this does not go into effect until the next sanctuary upgrade is announced (Jan 20th~).
3)  Removed the ability for POOM sponsors to pay with BBP.  (Removed paysponsorship command).  This theoretically reduces sell pressure since all of our charity expenses are through poom.  This means poom miners will need to set up payments with a credit card for children (or use paypal or checks).
4)  Added 'cancelsponsorship' command.  This allows a poom sponsor to cancel a child.
5)  Fixing two of the clerical errors found during the go live.
6)  Allow voting up to 93% into the epoch of the voting period.

Please let us know if we missed anything or if anything else is sorely needed for this release.

[WhyMe]

Thanks for that. I'm concerned by points 1 & 2. Will see result tomorrow !

[bible_pay]

** 1 Million BiblePay PODC Giveaway **


Terms and conditions:

- You must be an existing PODC researcher, in the biblepay leaderboard as of January 31st, 2020
- You must be contributing to research in World Community Grid
- You must have more than 100 RAC (recent average credit)

Mechanics of picking the winner:
- At block height 173307 we will take the first 4 hex-characters of the blockhash,  equaling 1-65535 (A).  Let B = 65535 / (count of superblock researchers in the prior superblock).  Let C = A / B.  C equals the (ordinal of) the winner (by counting from left to right through the last GSC contract prior to 173307).

[bible_pay]

** 1 Million BiblePay PODC Giveaway **


Terms and conditions:

- You must be an existing PODC researcher, in the biblepay leaderboard as of January 31st, 2020
- You must be contributing to research in World Community Grid
- You must have more than 100 RAC (recent average credit)

Mechanics of picking the winner:
- At block height 173307 we will take the first 4 hex-characters of the blockhash,  equaling 1-65535 (A).  Let B = 65535 / (count of superblock researchers in the prior superblock).  Let C = A / B.  C equals the (ordinal of) the winner (by counting from left to right through the last GSC contract prior to 173307).

I'm doing this to drum up interest in joining PODC this month.  If anyone wants to copy this into BOINC forums or in other threads feel free to help spread the word.

I'll also be creating an opt-in e-mail list campaign on google for this in a couple days to see if I can gather an e-mail address first - then I give them the campaign info, this way we can have an opt-in e-mail list to build on.

[Budinga]

Happy New Year All.

I have just come back from the holidays and trying to associate my work community grid account.

Ok i managed to get a bit further now.

It says im not part of biblepay team. will wait a little while and try again.

[togoshigekata]

Updated ANN:
https://bitcointalk.org/index.php?topic=2388064.msg53463543#msg53463543

Updated Documentation:
https://bitcointalk.org/index.php?topic=2388064.msg53457231#msg53457231

Any and all feedback welcome!

and Rob if the ANN is thumbs up for you, please update it when you get a chance

[jaapgvk]

I've upgraded my sanctuaries to the latest wallet version (1.4.8.4.) and cleaned them as per Togo's guide. Everything seems to be working fine, but I can't seem to vote.

Code:

Voting failed! Failed to vote 0 time(s). (Check that sanctuaries are DIP3? Also you must wait 3 minutes in-between re-votes due to network rules.)

They are in the DIP3 list and I've been getting rewards consistently. Both controller wallet and sanctuary wallets are on the same chain, and they are not on a fork as far as I can tell...

Can you please post the voting command including the id you are using, as I voted manually for Togos proposal and it worked but I did it from the rpc.

I tried to vote using the GUI. I can't remember the command to pull all the Proposal ID's, and I don't know if I can copy them from the GUI proposal tab   So I can't try it from the rpc for now. How can I find a list of all the current Proposal ID's that I can copy/paste so I can try it from the rpc? There used to be an overview of all the proposals on pool.biblepay.org right?

Ok yes cause I would like to try to reproduce with one that actually throws the gov exception error, so one way, is to type:
gobject list all proposals

Could you try voting on the woocommerce one?  98e09d657fb771f1559ab046af76d295ebde16f563d35ff9bc95ff738ae725f7

gobject vote-many objid funding yes

And let me know if successful and also, then try voting on the one you tried earlier and paste the vote string so I can reproduce?

Note that we have not passed the mandatory height yet, but thats another topic (partially related though).

Yes, it's working fine manually from the rpc

Code:

17:46:33

gobject vote-many 98e09d657fb771f1559ab046af76d295ebde16f563d35ff9bc95ff738ae725f7 funding yes


17:46:33

{
  "overall": "Voted successfully X time(s) and failed 0 time(s).",

From the GUI I tried voting for all the proposals that are currently in the 'Proposals' list, and they all got the same error I mentioned before.

I think we are OK then, the reason you cant vote now is we are past the 'end epoch period' for the monthly gov proposal block (166050).  (I confirm it is actually too late to vote to change the outcome of this monthly trigger).  Also there are a couple changes coming - at height 166075, we switch over to pure dip3 DM mode. 

So lets do this, please wait til next months proposals start kicking in then lets vote for one as early as possible and the error should go away.  (We tested that in testnet).

I do confirm I receive the same error as you in my GUI so yes we are on the same page.

I tried voting again from the GUI on some new proposals and initially got the same error as last time:

Code:

Voting failed! Failed to vote 0 time(s). (Check that sanctuaries are DIP3? Also you must wait 3 minutes in-between re-votes due to network rules.)

Then, I tried voting from the command line and I understand the 'error' now. I believe that in the past, when voting via the GUI, you got a popup asking you to type your password to unlock your wallet before voting. Now, it seems' that pop-up no longer appears. So I've been trying to vote with a locked wallet :p When I unlock the wallet from the debug console first, and then vote from the GUI, I don't  have problems voting. But I guess that I was so used to doing everything from the GUI that I didn't notice that the popup didn't show, and the 'error' didn't say anything about perhaps having to unlock your wallet before voting, so I didn't think about that.

Was the popup removed for a reason?

[bible_pay]

I've upgraded my sanctuaries to the latest wallet version (1.4.8.4.) and cleaned them as per Togo's guide. Everything seems to be working fine, but I can't seem to vote.

Code:

Voting failed! Failed to vote 0 time(s). (Check that sanctuaries are DIP3? Also you must wait 3 minutes in-between re-votes due to network rules.)

They are in the DIP3 list and I've been getting rewards consistently. Both controller wallet and sanctuary wallets are on the same chain, and they are not on a fork as far as I can tell...

Can you please post the voting command including the id you are using, as I voted manually for Togos proposal and it worked but I did it from the rpc.

I tried to vote using the GUI. I can't remember the command to pull all the Proposal ID's, and I don't know if I can copy them from the GUI proposal tab   So I can't try it from the rpc for now. How can I find a list of all the current Proposal ID's that I can copy/paste so I can try it from the rpc? There used to be an overview of all the proposals on pool.biblepay.org right?

Ok yes cause I would like to try to reproduce with one that actually throws the gov exception error, so one way, is to type:
gobject list all proposals

Could you try voting on the woocommerce one?  98e09d657fb771f1559ab046af76d295ebde16f563d35ff9bc95ff738ae725f7

gobject vote-many objid funding yes

And let me know if successful and also, then try voting on the one you tried earlier and paste the vote string so I can reproduce?

Note that we have not passed the mandatory height yet, but thats another topic (partially related though).

Yes, it's working fine manually from the rpc

Code:

17:46:33

gobject vote-many 98e09d657fb771f1559ab046af76d295ebde16f563d35ff9bc95ff738ae725f7 funding yes


17:46:33

{
  "overall": "Voted successfully X time(s) and failed 0 time(s).",

From the GUI I tried voting for all the proposals that are currently in the 'Proposals' list, and they all got the same error I mentioned before.

I think we are OK then, the reason you cant vote now is we are past the 'end epoch period' for the monthly gov proposal block (166050).  (I confirm it is actually too late to vote to change the outcome of this monthly trigger).  Also there are a couple changes coming - at height 166075, we switch over to pure dip3 DM mode. 

So lets do this, please wait til next months proposals start kicking in then lets vote for one as early as possible and the error should go away.  (We tested that in testnet).

I do confirm I receive the same error as you in my GUI so yes we are on the same page.

I tried voting again from the GUI on some new proposals and initially got the same error as last time:

Code:

Voting failed! Failed to vote 0 time(s). (Check that sanctuaries are DIP3? Also you must wait 3 minutes in-between re-votes due to network rules.)

Then, I tried voting from the command line and I understand the 'error' now. I believe that in the past, when voting via the GUI, you got a popup asking you to type your password to unlock your wallet before voting. Now, it seems' that pop-up no longer appears. So I've been trying to vote with a locked wallet :p When I unlock the wallet from the debug console first, and then vote from the GUI, I don't  have problems voting. But I guess that I was so used to doing everything from the GUI that I didn't notice that the popup didn't show, and the 'error' didn't say anything about perhaps having to unlock your wallet before voting, so I didn't think about that.

Was the popup removed for a reason?

I don't know about the popup; realize that we have gone through so many hundreds of K of changes running the hybrid mode and now dip3 mode, its hard to say; note that there is even a different case that your wallet is going to go through when we enable chainlocks in a few days (two more DIPS actually get set in mainnet soon), so what Im saying is we will be running the pure voting DM mode in a few days, and now the error can be streamlined.

In any case, I just modified the error message to ask the user to unlock the wallet if its locked.

[bible_pay]

Happy New Year All.

I have just come back from the holidays and trying to associate my work community grid account.

Ok i managed to get a bit further now.

It says im not part of biblepay team. will wait a little while and try again.

Happy New Years!

Yeah, if you have any trouble with 'exec rac' after waiting 12 hours (since the researchers are loaded twice per day) let me know the cpid and Ill search.

But it does take a while to sync changes to the team, or to the data sharing settings, etc.

[bible_pay]

Updated ANN:
https://bitcointalk.org/index.php?topic=2388064.msg53463543#msg53463543

Updated Documentation:
https://bitcointalk.org/index.php?topic=2388064.msg53457231#msg53457231

Any and all feedback welcome!

and Rob if the ANN is thumbs up for you, please update it when you get a chance

Thanks a lot Togo, this is extremely helpful!  Updated.

[MIP]

New iOS mobile wallet version

Ready in app store

- added new tithe feature screen
- updated protocol number
- fix message header processing for qsendrecsigs

[bible_pay]

Just as a non-related test I rebooted the wallet and measured the governance sync time - and it was only about 30 seconds total (to reach mnsync status 999),  and it consumed about 75k of bandwidth!

This is great, and I feel we must give credit where credit is due - the deterministic sancs are behaving much better than the old hybrid branch.

Ill go as far as saying, I think we got very unlucky when we picked the hybrid version.  We didn't have a horrible time with PODC 1.0 when we used the September 2017 branch of Dash.  But we had a horrendous time throughout most of 2019 with the hybrid branch. 

Lets look towards a bright future with DM, concerning reliability (and with chainlocks, and we are looking forward to a bright fork-free future also!).