** BULLETIN FROM GRAVIEX **


Dear Friend!
 
In the light of St. Valentine’s Day we announce another picture competition! Since 16:30 UTC of February 11 till 16:30 UTC of February 15 post your Valentine’s pics with coin project logos in Twitter and Instagram.
Please, notice:
- a coin must be listed on Graviex;
- all your pics must have hashtags: @graviex_net and #GraviexValentinesDay2020;
On February 15th at 16:30 UTC , 4 authors of the most popular pics will be rewarded as follows:
- 1st prize – 0.5 ETH;
- 2nd - 0.25 ETH;
- 3d and 4th - 0.125 ETH (each).
 

** Biblepay TestNet - Opening Now **



RandomX testing is starting today!

We have 3 options available so far:
Windows 64 bit binary
Linux 64 bit biblepayd
Linux 64 bit biblepay-qt

or

Self compile

Please help us test RandomX here:

https://forum.biblepay.org/index.php?topic=490.new#new

It looks like when testnet opens we will get paid for mining on the randomx side.  This will be a pro.

Sent.


And I also added code to the server side to prevent the same issue from reoccurring.

Or, if you want you can just replay the prior superblock to the PODC researchers.

I'll cover the costs on this, let me know how much it is. 

Tomorrow I will add code to the server side to prevent this.  I believe we can detect it when we are in prod mode with less than 50% of the CPIDs, we can keep hold of yesterdays file and keep trying until success occurs.  Hopefully we will get the uptime back to 99% that way. 

I want to give an update on temporarily winding down Compassion and transitioning to POOM.
And to re-iterate we do like compassion, they appear to be a great organization with Christian values.  We are in the POOM era simply because Cameroon-One and Kairos agreed to integrate with us technically, and we don't have an unlimited budget to continue the Compassion side until some time in the future.

So in the wind-down we had approx $1,675 credit that compassion recommended we put toward the orphan insurance fund.  I then recommended we put it toward new children (or to compassion for babies).  Because of the "assumption" that we would sponsor 4 new children and then cancel them, they said no.  So I tried manually starting 4 children with my credit card and asking if we can use the residual balance to pay for the 4 kids for the next year.  After the kids started, They said No (and canceled the children).  (And recommended us to use the balance for the insurance fund).

I said No, I want it to go to the KIDS only.  So I asked for a credit back.  They have issued a credit.

So now what I'm doing is working with Steve, president of SAI.ngo, to see if he can give us a wholesale deal on 20 orphans in Venezuela.  I'm trying to direct the leftover money with the absolute maximum magnitude.

It looks like everyone missed the PODC reward today, because the assessment by the sancs over the last 105 blocks (before the emission) was that there were no cpids to pay.
However the rest of the superblock was emitted (Cameroon one, Kairos, and Whale stakes).

** BIBLEPAY POOL ADMINISTRATORS BULLETIN **


All pools:

Due to the RandomX development initiative, POBH will (most likely) have a shortened lifespan (IE < 6 months left before it retires).
So please be aware of the following plan to transition to the RandomX algorithm:

The current POBH pools have been forked to:
https://github.com/biblepay/node-open-mining-portal-pobh
https://github.com/biblepay/node-stratum-pool-pobh

No code changes have been made to POBH so there is no need to do anything.  Please be aware however, not to git pull the latest until we are live in prod with randomx.
As the current repos will be transitioned over to RandomX.  If you need to start a new pool or repair your pool please change your github URLs to the above urls for pobh.

The next steps:
I will be creating more repos and a testnet endeavor for RandomX. 
My goal is to have testnet ready by the end of this weekend.


All:  NOTE:  We need your help to test the BBP RandomX branch!

Ok, looking at this issue (not linked cpids, truncated CPID info):

The problem has been resolved.  (The technical reason was the WCG info we read was cut off at that particular time - but when rescanned - all data came in).

So as a user, if you want immediate results please restart biblepay and let it re-load the cpids - then exec rac should work - or you can simply wait ~4 hrs, and during the next block cycle (within 102 blocks) it will repopulate the leaderboard.  (The sancs will automatically repopulate at the next mid-cycle).

Ok, yes, let's offer another 1 million reward for the February 2020 (PODC jumpstart giveaway).

Feel free to promote it Sun, Togo and any others who have been spreading the word.

I'm sorry I haven't been on to reply in the last two days, but I've been very busy with the RandomX integration in testnet.  I will post an update on the poll thread very soon.

From what I can tell, the RandomX concept is going to work, and we will most likely have something to test in testnet within 7 days.

*** CONGRATULATIONS BBP Leaderboard PODC Researcher 027057 (BQWhLA82SxL8PW5LGnwKj8qeog3k3JETBZ), you won the 1,000,000 BBP January Prize! ***


Thank you all for participating!

Since this months participation was a success, we should hold a new giveaway in February.

The reward has been sent.  

As far as calculating it, I wrote a tiny vb6 subroutine for this that I will post in the thread and re-use if we have another poll.

LOL, it looks like I won (vout #52 in block 173245).

But since I'm a nice guy I am going to award this to the CPID in position 51 (I'm going to 51 simply because the math of the answer has a floor of 51, and rounding sent it to 52).

I will announce the winner next.

Looks like we have 59 participants in the leaderboard!

I look forward to calculating the results on block 173,307.

Good luck!

Wow!  What a terrible line of business these hosting services have been embroiled in.
Btw, hostbrz owed me a $1,000 credit and the owner e-mailed me and said don't worry we'll get back to you within 10 days with a refund plan, then they pulled the whole domain etc and dissapeared.

I called my credit card company and asked if I would be allowed a chargeback but they didn't go for it due to the date of the charge being like 6 months ago.

Anyway, its good we didn't go tooo far with Apollon, although I wish them the best (that is, too far in goatroping our users into something that will fail).

I believe the only partner we have left is SatoshiSolutions.  We will need to get an update on that project from MIP.

And just to reiterate my opinion, I'm all for our partners accepting BBP, and always have been.  I am also of the belief its up to the individual if they want to pay POOM or sponsorship dollars in BBP.

(We removed the poom autopay option so as to guard our price from dropping sharply every month.  And also to make it more likely for a poom user to potentially pay in fiat.  But not to completely block them.  If they really want to pay in BBP they still can by doing a manual liq.)

On a side note I paid my cameroon yesterday in paypal to keep the sell pressure off BBP.

(And, I stopped charging BBP payroll until new exchange fund is paid off).

Maybe - with due diligience and vetting; but - after speaking with Steven, president of SAI.NGO, who btw seems to be a very good future candidate and partner for us, explained to me how important the vetting process is for larger investors.  The globalgiving seal of approval is "a good start", but more importantly, he explained the GuideStar platinum rating was one of the most coveted ratings.  And if we want to yoke ourselves with leaders we should tout all spent dollars go through fully vetted orgs.

I do have a lot to talk about on this but I cant make a wiki page about the concept right now.  But some of this is related to being a charity agent.  Part of the idea is for BBP sanctuaries to gather and rank charities that are fully vetted and apply ranking scores, and help maintain our web pages of vetted charities.  And reach out to them and look for deals.  Enter this info in the database and have a central (and I think this would be a brand new ngo web site for biblepay), that would allow the user to rank these by magnitude descending.  Part of the magnitude would also be the discount given (either through matches, or discounts by the org).

This would allow donation fiat or crypto to be passed through our system - something we dont do yet (donate buttons, donate processes etc) - and we would be a trusted arbiter of the 'best deals' - or the most bang for the buck when spent on charity.  The small % fee we would charge would be rewarded back to the giver in BBP.

One other discovery I made in this was 'wholesale deals'.  Steven explained how he can find 20 Venezuelan orphans for half price (IE something like $20 per month), but only if this entire ecosystem was established (we cant go these routes unless we have solid commitments and the programming done and see that our community is helping do this work also).  But if we get there, we will be able to offer wholesale sponsorships with these deep discounts for desperate needs.  He can also potentially give us bios.

So anyway, I as a part time charity investor really believe in this vetting process; it can be done more so by others because we will be seeking larger orgs like sai.ngo who naturally have to be certified to receive cross border payments etc.

The problem with non-vetted orgs is there is no way to know the funds actually reach the end-user and we need 100% trust here for our pass through dollars -- otherwise we might fail.

It would be nice to eventually prove that all pass through dollars can be traced to orphan ids.  So far we do have that ability.

I don't fully agree with the terminology of "missed" or "minimal send".

Instead, I maintain that there is a 24 hour delay between the point the researcher surpasses 255 rac, and a full automatic send by the wallet.
The wallet does automatically send the correct coin age after the maturity period- and day to day thereafter.

Please read this additional info and also please vote everyone:
https://forum.biblepay.org/index.php?topic=489.msg6899#msg6899

So basically, the way the aggregator in PODC 2.0 works is once every 105 blocks (twice a day), each sanctuary (and full node) will re-calculate all of the rac.  So for most intents and purposes this means all the cpids (participating or not) and their corresponding RAC are known to the sancs with a 12 hour delay.

So what this means for the user is if one had crossed over to 255 RAC this morning, by the next morning they should see themselves in the leaderboard - lets just call it a 24 hour delay.
They don't have to manually send the sendgscc as it will automatically send at the height in 'exec rac'.

However if they are in team BBP with < 256 rac, we don't need the daily escrow record (we automatically insert it for the unbanked).

If someone is really ancy, if they see their 'exec rac' has surpassed 255, they can manually send the sendgscc and then appear in the leaderboard a few blocks later.  (The leaderboard is what the sancs use to assess the contract).

** POW POLL **

Dear all users - please provide feedback on the next-gen hashing algorithm for POW, to ensure the community guides and likes the potential direction:

https://forum.biblepay.org/index.php?topic=489.msg6894#msg6894