** 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. |
|
|
|
|
** 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).
|
|
|
|
|
** 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.
|
|
|
|
|
** 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.
|
|
|
|
Everyday BBP make new bottom price...  I think we need to remove the sell pressure from our charity model. |
|
|
|
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 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. |
|
|
|
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. |
|
|
|
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). |
|
|
|
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. |
|
|
|
Rob, any update on accountability? accountability.biblepay.org has been missing details after Sep 2019 for revenue & expense.
How do we track how much BBP was donated to charities and the the price of USD (roughly) at the time BBP was given to these charities?
Let me take a look at this problem. All the data is present in the chain, but not consolidated correctly. |
|
|
|
Dear ROB / BBP team, I joined the PODC 2.0 over 2 Days and the RAC and coinage is no any problem. I checked over 2days no reward. Please help to check. thanks.  CHRISTIAN-PUBLIC-KEY:B6vnmv8QQ87Teuzvaa7M36Nvybe9cxewLE Adding to what Capulo said, It looks like you set up your CPID and linked it correctly to your CPK, your rac is 18,100 and you are on team biblepay, and daily reqs are 344K of coin age and you have plenty of BBP in your wallet (and coin age) and you did send your first GSC transmission successfully. You can find this out by typing: exec sentgsc B6vnmv8QQ87Teuzvaa7M36Nvybe9cxewLE See you send 1 out with 328K coin age, so you are good there. I see you are not in the leadeboard today. It takes 48 hours to get the payment for the one you sent at height 166359, meaning that days work will be in todays superblock (your are #4 in todays superblock payment list). So all you really have to do now is figure out why your machine is not sending gsc's regulary. You can type 'sendgscc wcg' now and force one manually. Maybe you need to leave your node running. They send out automatically at the height shown in 'exec rac'. Once per day. Good luck. |
|
|
|
The original guide explains coin*age https://wiki.biblepay.org/PODCThe guide I've been working on doesn't, just added it in, please review https://wiki.biblepay.org/PODC_Setup#PART_H:_Calculate_StakingI dont think it really changes the calculation since PODC is a daily thing and you need that many coins aged 1 day, But it does affect starting out, because you have to wait a whole day for newly acquired/boughten coins to age to get the full reward I believe the reasoning behind coin*age is to combat staking abuse (Using the same coins for multiple stakes, for example, in the past, 2 or 3 of us could get together and pass 1 million BBP around in a circle every day and each of us could use those same coins for our staking requirement, not saying I did this, just showing as an example) Yes, exactly, the original PODC just required the daily coin amount and was eventually shared and manipulated, but now we require coin*age. |
|
|
|
1) Strictly on the part about the 'exec rac' switching from the 37Mil requirement over to 'not being linked', that is a bug in this first version, but note, its not the kind of bug affecting PODC or payments (its a client glitch on the display purposes only). You can get around it by rebooting the client or waiting four hours (then exec rac will work again). Im trying to get that fixed as a leisure asap. 2) So Im looking at your coinage reqs. Since you arent on team bbp, thats why the req is so high (37 mil). Yes, we are supposed to put you in the leaderboard with a commensurate low reward, but I see we have a minimum threshhold (I honestly dont remember doing that, but for now we have it because its the consensus for the sancs). So here is how the two step phase works: On Non-Team BBP, we check your req, and 54000 rac reqs 37Mil in coin-age. Then we reduce your minimum RAC req (after we see you didnt make it), to 4368 RAC. Then we see if you have a coin age of 667,501 BBP (but you didnt meet that), so that explains why you are not in the leaderboard. Note, that if you send out a GSC, you will show up in the leaderboard in about 5-7 blocks, as long as you satisfy the req. So if possible, if you join team BBP, what would happen is the req would drop to 53.9K for 4368 (after missing the first) and you would be in the leaderboard. This also explains why you have not received podc rewards (you must be in the leaderboard to get podc rewards). OK, so since I won't switch teams (as I am a team captain) then my only option is to set up an Exchange account and purchase more Biblepay to meet the minimum requirements which isn't going to happen either. I don't trust the current exchanges. So, I guess what I need to know now is how to turn off PoDC so that I'm not wasting my BBP with GSC transmissions that won't ever pan out a return. I also see this as an issue that will most likely occur with many BOINC contributors that may be tempted to create wallets. It should also be explained better in the wiki as this seems to be a "dead zone" of sorts. Also, since there is no Android (or mobile) work to crunch at WCG right now (for a few months now actually) and no ETA on when it will return (scientists have not said when SCC will have work again and WCG has no official plans for Android work on the other sub projects) then isn't it a moot point right now to have a low RAC stipulation for unbanked? Maybe a note needs added to the wiki for this as well. 1) 10-4 on WCG lacking the mobile app. Thank you. 10-4 on the wiki guide. And the dead area on unjoining a project. 2) As far as a moot point for unbanked, I think its a two part deal. MIP is working on making the 'sendgscc wcg' work on the mobile. But yes once he finishes, we will have a challenge to deal with. We'll have to make a post on the WCG threads and ask them if *any* sub projects will ever return for android? If they say no we might as well stop working on that MIP, until we have a better idea. I think its certainly a good feature to have; we should have a coin that is friendly to third world countries who have no bank accounts. Back when our price was higher we calculated that mobile research was enough to live on in a third world country (food only). 3) To unjoin please type: 'exec unjoin wcg'. That should stop the daily gsc transmission. 4) As far as trust, I don't have any reason to not trust SX personally. One way you can minimize the risk is not keeping any latent digital asset on an exchange overnight - just make small trades (IE 100K bbp) and take it out immediately, then repeat etc. |
|
|
|
Finally my WCG account is linked with my wallet.
RAC 657 ... So I need 4500bbp to get my reward ...
To be under 250 we need to run WCG on a pentium III ?
Sort of ... To be unbanked, you can throttle boinc so it hardly does work - and let the rac drop. But on a more serious note we have some mobile unbanked users and they tend to gravitate under 300 rac. The idea back then was to allow them to earn enough to buy a loaf of bread through cancer mining etc (on a mobile). |
|
|
|
Yesterday running exec rac got me:  { "Command": "rac", "cpid": "1bb993deb5284d5f357c6ef05d8eddb2", "CPK": "BSzYoSHeQGwAGseo12gq67KdL56AhVSoEV", "next_podc_gsc_transmission": 166357, "team_name": "Unknown", "external_purse_total_coin_age": 1789.596875000001, "coin_age_percent_required": 0.99, "NOTE!": "Coins must have a maturity of at least 5 confirms for your coin*age to count. (See current depth in coin control).", "WARNING!": "BiblePay requires staking collateral to be stored in your Christian-Public-Key (External Purse) to be available for GSC transmissions. You currently do not have enough coin age in your external purse. This means your PODC reward will be reduced to a commensurate amount of RAC. Please read our PODC 2.0 guide about sending bankroll notes to yourself. ", "coin_age_required": 37331261.2988052, "wcg_id": 338542, "rac": 54018.86 } 21:53:52  However today when I run it I get: exec rac 21:53:52  { "Command": "rac", "cpid": "1bb993deb5284d5f357c6ef05d8eddb2", "temporary_cpid": "1bb993deb5284d5f357c6ef05d8eddb2", "Error": "Your CPID is linked to your CPK, but we are unable to find your research records in WCG; most likely because you are not in team BiblePay yet.", "Step 1": "Log into your WCG account at 'worldcommunitygrid.org' with your WCG E-mail address and WCG password.", "Step 2": "Click Settings | My Profile. Record your 'Username' and 'Verification Code' and your 'CPID' (Cross-Project-ID).", "Step 3": "Click Settings | Data Sharing. Ensure the 'Display my Data' radio button is selected. Click Save. ", "Step 4": "Click My Contribution | My Team. If you are not part of Team 'BiblePay' click Join Team | Search | BiblePay | Select BiblePay | Click Join Team | Save.", "Step 5": "NOTE: After choosing your team, and starting your research, please give WCG 24 hours for the CPID to propagate into BBP. In the mean time you can start Boinc research - and ensure the computer is performing WCG tasks. ", "Step 6": "From our RPC console, type, exec associate your_username your_verification_code", "Step 7": "Wait for 5 blocks to pass. Then type 'exec rac' again, and see if you are linked! ", "Step 8": "Once you are linked you will receive daily rewards. Please read about our minimum stake requirements per RAC here: wiki.biblepay.org/PODC" } I am not on team BiblePay. According to the documentation I do not have to be. Is this accurate or is it limited to team BiblePay and Gridcoin? https://wiki.biblepay.org/PODC_SetupI can see that I have now sent out 3 GSC transmissions in the wallet but have not received any payouts for contributions to WCG. Before asking, I have contributed to WCG non-stop for 12 years. My RAC is fully established by now. I am aware that coin age may be a factor, but wasn't sure if that is the case since the reply mentioned not being part of the team. I will also add that I do allow stats exporting. 1) Strictly on the part about the 'exec rac' switching from the 37Mil requirement over to 'not being linked', that is a bug in this first version, but note, its not the kind of bug affecting PODC or payments (its a client glitch on the display purposes only). You can get around it by rebooting the client or waiting four hours (then exec rac will work again). Im trying to get that fixed as a leisure asap. 2) So Im looking at your coinage reqs. Since you arent on team bbp, thats why the req is so high (37 mil). Yes, we are supposed to put you in the leaderboard with a commensurate low reward, but I see we have a minimum threshhold (I honestly dont remember doing that, but for now we have it because its the consensus for the sancs). So here is how the two step phase works: On Non-Team BBP, we check your req, and 54000 rac reqs 37Mil in coin-age. Then we reduce your minimum RAC req (after we see you didnt make it), to 4368 RAC. Then we see if you have a coin age of 667,501 BBP (but you didnt meet that), so that explains why you are not in the leaderboard. Note, that if you send out a GSC, you will show up in the leaderboard in about 5-7 blocks, as long as you satisfy the req. So if possible, if you join team BBP, what would happen is the req would drop to 53.9K for 4368 (after missing the first) and you would be in the leaderboard. This also explains why you have not received podc rewards (you must be in the leaderboard to get podc rewards). |
|
|
|
Coin age is not the same as BiblePay total. So 1 BBP in your wallet untouched for 3 days is 3 days worth of coin age. At least that is how I understand it. And yes this is an issue for DC'ers and requiring such an up front amount to get started. I am not a large DC'er and I don't have the amount needed as I only have a little over 100k BBP total to work with.
Hi there! I believe you need to pass the minimum stake to go into the leaderboard, regardless of the team. It was something like 5% ? Assuming it is 5%, you would need 1.8M BBP or so in the CPK address. Well, we do actually reverse engineer the researchers RAC down to a commensurate level of RAC if they dont have enough BBP. So if they have 100,000 bbp on hand, and lets say that amount allows a level of '9000 rac' on team biblepay, but he has 150,000 rac, the leaderboard will reverse his RAC down to 9000 and he will still get a reward. There is an issue where if payments are lower than something like .10 bbp they will not enter the leaderboard due to rounding issues etc. Note all: Its a lot cheaper to participate if you are in Team BBP rather that not in team bbp. |
|
|
|
I'm sorry to see that you might have mined on a fork and lost some bbp mined off the main chain, but we must move forward. Ill post my hypothesis.
First, note that in our 2 year history this is the first mandatory where the network required our users to upgrade before the mandatory cutover height. We had an increase in our governance protocol version to 70750 from 70737, and when 60% of our sancs moved to 70750, the older biblepay clients stopped recognizing those sanctuaries as official, meaning they then need to upgrade early (or go on a fork) - this explains why 75% of our network upgraded 3 days early (we were shooting for Dec 26th and all this happened around Dec 23rd).
So apparently what happened is you mined on the prior version, 1 mil bbp on the low diff chain. When you upgraded, all the blocks mined on the side chain got erased. Notice how your outbound transaction to your mobile is orphaned also. Thats because it was sent on a sidechain, and the txid is not on the main chain.
The reason your last mined transaction is in immature is because its not 120 deep yet but its probably officially mined.
Just run the client with -zapwallettxes=1 and restart and it will fleece the orphans out of the wallet - note it will remove all the mined and the outbound tx and leave all official txes.
Good luck going forward.
Is it possible in future display a message about necessary upgrades (or just about next available versions) right inside the wallet? May be as a Prayer Request, I don't know... Also, I would like BiblePay to support a distributed computing project Rosetta@homep.s. https://wiki.biblepay.org/PODC_Setup#PART_I:_Calculate_Rewards - so actually we can't calculate a reward for PoDC mining, right? I like charity and BOINC, please don't get me wrong, but for now I need to return my investments in hardware... Later (pls check my signature if you didn't do this yet) it will not have such a meaning for me like it has now... Addressing the PODC reward question, we have a daily GSC superblock with 872K emitted to participants daily; about 40% goes to POOM/Healing and 60% to PODC. So out of the daily emission of 550,000 bbp, that is split evenly by the RAC in WCG project. Right now 1 point of RAC is very close to 1 BBP daily reward; if you go into the Leaderboard from qt, and look at all the rows starting with "WCG", notice that the "points" on those rows actually equal the researchers RAC. So if someone has 1000 points, they have 1000 RAC. Today 1000 RAC is paying about 1000 bbp per day. Of course this changes as more competitors come in. Ill have to look at the situation with Rosetta; we like them but they ran out of work a lot, and caused us to really break our necks trying to add WCG as a backup. Now we have WCG primarily because they have about 10 different possible parallel projects to crunch - so Im hesitant to add complexity to PODC (by supporting multiple projects) - once you go that route then you have to have a dynamic ratio per RAC per project (as each RAC per project is not equal in cobblestones). At least now, everyone is fairly stuck in WCG which is nice for competition and fairness. |
|
|
|
Android mobile wallet version 1.4.8.5
- added new tithe feature screen
iOS version will come in a few days
Oh wow, this is awesome, we always wanted to be able to tithe to churches from the mobile (even though we have no official partners yet, who are churches). So what we did to launch this is we entered a few 'partner' records in DSQL (from web.biblepay.org click on partners). These are just our existing charities we already have a relationship with. If someone clicks "Tithe" from the mobile wallet, they can give some extra BBP to one of those partners. The idea is in the future, when we make a relationship with a church, we can add a DSQL record for the church, then the congregation can tithe with BBP. Great work MIP, thanks! |
|
|
|
If they use the built in miner, they do still need the basic rpc commands (actually all the old solo mining config options in biblepay.conf still work, like gen=1, genproclimit=20 etc, minersleep=0, those things would cause the solo miner to automatically run when biblepay boots). As far as the rpc though, if the user wants to manually start mining, they have to type : setgenerate true num_cores setgenerate false (to stop mining) getmininginfo is a little slimmed down now (the pool fields have been removed. As you know ABN is off, so that has been removed also). So its basically simplified now. |
|
|
|
|
Show Posts
