Bible Pay

Read 303735 times

  • sunk818
  • Global Moderator

    • 521


    • 36
    • April 24, 2018, 02:02:20 PM
    more

Nice job on the new build. Would you consider giving us lower difficulty sooner? My i5 can't seem to handle 50k difficulty and takes 5-10 minutes before going down to 10k which seems more manageable. I don't know how difficulty works exactly with RandomX but that's been my experience on my lowly computer.

** BBP-Xmrig 5.10.1 - Mandatory Upgrade for Miners **


- Remove automatic tithing from the miner

* Note:  The old version of the miner tithes 10%.  Please start using the new version, as the pool now holds back the 10% orphan-tithe automatically.

Binaries:
https://wiki.biblepay.org/Upgrade_to_RandomX

** Mac is still building, MIP will notify
BH6oxjLkyz3z8FYpvU3ZR7PTZ31Xt9DkXZ


  • Rob Andrews
  • Administrator

    • 4097


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Nice job on the new build. Would you consider giving us lower difficulty sooner? My i5 can't seem to handle 50k difficulty and takes 5-10 minutes before going down to 10k which seems more manageable. I don't know how difficulty works exactly with RandomX but that's been my experience on my lowly computer.

Looking at the diff level in the pool (this is called difficulty=1 for both XMR and BBP, regardless of what the display shows for XMR), running my ryzen on 1 thread, it takes 2 minutes to solve 2 shares.  I dont see a problem with the diff level, especially since we have a few thousand shares being solved in each block.

Besides, you have 7 blocks to solve a share before it gets discarded.

Everything looks fine. I suggest mining for 24 hours and looking at the grand total shares solved by the machine for bbp and xmr.



  • Rob Andrews
  • Administrator

    • 4097


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Are we racing towards the mark of the beast?

Cryptocurrency patent #060606 using body activity data in place of POW (apparently with the assumption that someone is already chipped):
https://patentscope.wipo.int/search/en/detail.jsf?docId=WO2020060606&tab=PCTDESCRIPTION
I find it highly disturbing how many times the word "blood" is used also.

I almost didnt believe this was # 060606, so I incremented the number by one and sure enough its valid:
https://patentscope.wipo.int/search/en/detail.jsf?docId=WO2020060607



  • MIP
  • Sr. Member

    • 365


    • 47
    • February 13, 2018, 11:55:52 AM
    more
Are we racing towards the mark of the beast?

Cryptocurrency patent #060606 using body activity data in place of POW (apparently with the assumption that someone is already chipped):
https://patentscope.wipo.int/search/en/detail.jsf?docId=WO2020060606&tab=PCTDESCRIPTION
I find it highly disturbing how many times the word "blood" is used also.

I almost didnt believe this was # 060606, so I incremented the number by one and sure enough its valid:
https://patentscope.wipo.int/search/en/detail.jsf?docId=WO2020060607

I believe they will try to put us the chip with the excuse of a remedy for CV.
If you don’t follow then you will be considered an outcast.


  • Rob Andrews
  • Administrator

    • 4097


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
I believe they will try to put us the chip with the excuse of a remedy for CV.
If you don’t follow then you will be considered an outcast.

Yeah either that or maybe the antichrist has dreams of a society that is constantly tracked and paid in cryptocurrency for 'activity' but the activity must be GPS located and conforming with the plans of the antichrist (go here, buy a vial of tainted baby blood, worship the beast, come back to location 1, etc).

I have been hearing many negative things about the potential 'vaccine' for coronavirus.  The prophet Tracy Cooke claims he saw God take him to the Wuhan lab, and watch it being created as a weapon.  He said the vaccine will be designed to kill people.  Then when I woke up, I believe the Holy Spirit made me know that the Gates vaccination tests that resulted in thousands of dead Indians, those were intentional deaths - because the vaccine is going to be a killer vaccine.    A friend sent me a video last night with Dr. Buttar (here it is    https://youtube.com/watch?v=WGbYHJcMbz8   )  that anyone who has had an official flu shot in the last few years probably tests positive for coronavirus naturally.



  • sunk818
  • Global Moderator

    • 521


    • 36
    • April 24, 2018, 02:02:20 PM
    more
Everything looks fine. I suggest mining for 24 hours and looking at the grand total shares solved by the machine for bbp and xmr.


Yeah, I think the issue is on my end. I think I may need to restart my computer then only run the miner. When I tried yesterday with just 1 thread, the SSD was paging to the disk constantly and that's not the right setup I think. I appreciate you checking.
BH6oxjLkyz3z8FYpvU3ZR7PTZ31Xt9DkXZ


  • Rob Andrews
  • Administrator

    • 4097


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more

Yeah, I think the issue is on my end. I think I may need to restart my computer then only run the miner. When I tried yesterday with just 1 thread, the SSD was paging to the disk constantly and that's not the right setup I think. I appreciate you checking.

Thats great.  I haven't heard any other complaints so I hope this new pool environment is stable now.

I plan on posting some good news about the summary of the RX environment today.  Its very encouraging.



  • Rob Andrews
  • Administrator

    • 4097


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
** XMR+BBP parternship appears to be a success **


I'm very pleased to announce a small update regarding our RandomX initiative. 

First, tallying our April revenue from RandomX (sourced from foundation.biblepay.org and miningpool.fun), we have raised  1.13 XMR between April 1st and April 21st.  Even more exciting, with the higher recent trend (collecting the full 10% tithe over the last two days), it is projected at our current mining level (of 2.0 MH/S in the foundation pool), that we would actually be raising 3.0 XMR by the end of April!  This means that with our very tiny initial launch, we are already on track for raising about $180 in orphan charity in one single month!  Although this is relatively meager, it's a pretty big dent in our current orphan sponsorship level (75 orphans at $2,645.00 per month paid via POOM).  Or another way to look at it, we are on track to raising 6.8% of our child sponsorship expenses in our very first month of operation. 

The other equally important facet of this initiative is we have successfully found a way to eliminate 100% of the drawdown on the BBP currency ticker (remember, in the past, with our huge orphan charity expenses, each time we liquidated for compassion, we sent our price spiraling down by 70% as we raised money for orphan charity); those days appear to be over!  If we move entirely to the new model (XMR charity liquidations) there will be no drawdown on the BBP price!  (Except for the effect of normal mining liquidations).  But even that aspect has a very positive change.  With our XMR-BBP partnership, it can be viewed that the lions share of the miner's electricity bills are already paid (via the personal mining XMR reimbursement).  Meaning that this ecosystem allows us an unlimited growth potential without drawing down our price for mining rewards.

SAI.ngo news:  I received a message from Stephan at SAI.  We have been working on a deal to sponsor 30 more Venezuelan orphans for $20 per month.  The deal has been delayed for two reasons:  they are operating in emergency mode due to coronavirus.  Secondly they are having some type of governmental issue at the branch.  Steven will follow up with me within 30 days, once he confirms that the local branch is creating the bios.  In the mean time, we can mine against our extra cameroon-one children.  (I am setting up 10 outside of poom for this purpose, but keeping the bios and accounts active).

Future:

I believe we need to scale up what is successful, and what works for us.  We have quite a bit of room with POOM to improve our RandomX ecosystem.  Note that I am not the type of person that wishes to start a relationship and break it, so I feel we must do this slowly (over the next 8 months).  The idea is to slowly phase out POOM and phase more RandomX rewards in.  We can do this without hurting our relationship with Cameroon-One, by keeping the children sponsored but paid for with RX.  I'm monitoring GlobalGiving for matching opportunities.  If we can find a match, I will jump in and create a BiblePay match account, move the child from Poom to GG, and then we can allocate XMR revenue towards those children, etc.

What this means from a mining perspective is we can raise the heat mined reward as we scale back POOM rewards.  For example, if we lower the POOM reward 20% in our June release, we can raise our heat mined reward the effective amount up.  It might rise from 2482 per block to 3482 per block, for example.

Exciting times!






« Last Edit: April 21, 2020, 03:54:52 PM by Rob Andrews »


  • earlzmoade
  • Super Developer

    • 311


    • 48
    • August 02, 2018, 03:22:01 AM
    more
Nice update Rob! Looks like thers alot of possibility to grow aswell.

Getting more  RX miners and what not, the new fractional masternodes nice idea aswell i think.
Joshua 1:9
Have i not commanded you?
Be strong and courageous. Do not be afraid;
do not be discouraged, for the Lord your God
will be with you wherever you go.


  • MIP
  • Sr. Member

    • 365


    • 47
    • February 13, 2018, 11:55:52 AM
    more
** XMR+BBP parternship appears to be a success **


I'm very pleased to announce a small update regarding our RandomX initiative. 
...
The other equally important facet of this initiative is we have successfully found a way to eliminate 100% of the drawdown on the BBP currency ticker (remember, in the past, with our huge orphan charity expenses, each time we liquidated for compassion, we sent our price spiraling down by 70% as we raised money for orphan charity); those days appear to be over!

This is great news for both orphans and price action. It was a bit unfair to see this penalty on the price, and even more knowing the project has improved to become a rock-solid chain.

Let’s hope in the coming months we see the spiral but up for sponsorships and price.


  • Rob Andrews
  • Administrator

    • 4097


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Good news:  Song from miningpool.fun is going to start a satellite pool soon. 
I checked in more detailed instructions recently in the biblepay/foundation github branch (Starting a biblepay pool.pdf).

This should help us add resilience so we don't experience outages and also help decentralize the charity aspect.

I'll make a new spreadsheet to try to determine all places in Biblepay that we can decentralize.  I would like it so that if I die (or get raptured) that the coin can continue without a hiccup.

After all we might be a very useful coin in the great tribulation.



  • Rob Andrews
  • Administrator

    • 4097


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
***  Plan to Decentralize BiblePay into a fully decentralized autonomous charity  (DAC)  ***

https://wiki.biblepay.org/Continuity_Plan

Please read and if you have any concerns or proposed changes or if you feel this does not cover one of our processes please let us know.



  • earlzmoade
  • Super Developer

    • 311


    • 48
    • August 02, 2018, 03:22:01 AM
    more
Yesterday i saw i was getting this message on one miner, today i see it happens quiet abit on several machines,  any ideas Rob?

Code: [Select]
[2020-04-26 16:06:40.827]  cpu  accepted (106/1) diff 2 [6] BBP (291 ms)
[2020-04-26 16:06:41.037] speed 10s/60s/15m 16443.0 16439.1 16414.8 H/s max 16470.0 H/s
[2020-04-26 16:06:41.500] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:06:43.241]  net  new job from foundation.biblepay.org diff 469344 algo rx/0 height 2085213
[2020-04-26 16:06:44.642]  cpu  accepted (107/1) diff 479402 [1120757] XMR (1562 ms)
[2020-04-26 16:07:03.793]  cpu  accepted (108/1) diff 2 [96] BBP (248 ms)
[2020-04-26 16:07:23.039] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:07:23.701] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:07:39.040]  cpu  accepted (109/1) diff 2 [2] BBP (247 ms)
[2020-04-26 16:07:39.706] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:07:41.797] speed 10s/60s/15m 15787.5 16044.2 16387.8 H/s max 16470.0 H/s
[2020-04-26 16:07:42.663]  net  new job from foundation.biblepay.org diff 450442 algo rx/0 height 2085214
[2020-04-26 16:07:50.078]  cpu  accepted (110/1) diff 2 [2] BBP (281 ms)
[2020-04-26 16:08:11.063]  cpu  accepted (111/1) diff 2 [3] BBP (253 ms)
[2020-04-26 16:08:11.732] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:08:20.127]  cpu  accepted (112/1) diff 2 [4] BBP (314 ms)
[2020-04-26 16:08:20.848] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:08:21.204]  cpu  accepted (113/1) diff 2 [2] BBP (391 ms)
[2020-04-26 16:08:21.365] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:08:30.574]  cpu  accepted (114/1) diff 2 [16] BBP (757 ms)
[2020-04-26 16:08:30.736] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:08:41.827] speed 10s/60s/15m 16078.5 16024.7 16358.9 H/s max 16470.0 H/s
[2020-04-26 16:08:58.457]  net  new job from foundation.biblepay.org diff 424781 algo rx/0 height 2085215
[2020-04-26 16:09:04.452]  cpu  accepted (115/1) diff 424781 [874667] XMR (281 ms)
[2020-04-26 16:09:23.290]  cpu  accepted (116/1) diff 424781 [1873313] XMR (894 ms)
[2020-04-26 16:09:26.083]  cpu  accepted (117/1) diff 2 [2] BBP (241 ms)
[2020-04-26 16:09:26.745] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:09:33.086]  cpu  accepted (118/1) diff 2 [21] BBP (239 ms)
[2020-04-26 16:09:33.741] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:09:41.850] speed 10s/60s/15m 15881.0 15920.1 16323.7 H/s max 16470.0 H/s
[2020-04-26 16:09:50.091]  cpu  accepted (119/1) diff 2 [5] BBP (239 ms)
[2020-04-26 16:09:50.754] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:09:55.110]  cpu  accepted (120/1) diff 2 [2] BBP (255 ms)
[2020-04-26 16:09:55.780] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:09:56.244]  cpu  accepted (121/1) diff 424781 [911131] XMR (286 ms)
[2020-04-26 16:10:05.620]  net  new job from foundation.biblepay.org diff 455892 algo rx/0 height 2085216
[2020-04-26 16:10:07.152]  cpu  accepted (122/1) diff 2 [3] BBP (293 ms)
Joshua 1:9
Have i not commanded you?
Be strong and courageous. Do not be afraid;
do not be discouraged, for the Lord your God
will be with you wherever you go.


  • Rob Andrews
  • Administrator

    • 4097


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Yesterday i saw i was getting this message on one miner, today i see it happens quiet abit on several machines,  any ideas Rob?

Code: [Select]
[2020-04-26 16:06:40.827]  cpu  accepted (106/1) diff 2 [6] BBP (291 ms)
[2020-04-26 16:06:41.037] speed 10s/60s/15m 16443.0 16439.1 16414.8 H/s max 16470.0 H/s
[2020-04-26 16:06:41.500] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:06:43.241]  net  new job from foundation.biblepay.org diff 469344 algo rx/0 height 2085213
[2020-04-26 16:06:44.642]  cpu  accepted (107/1) diff 479402 [1120757] XMR (1562 ms)
[2020-04-26 16:07:03.793]  cpu  accepted (108/1) diff 2 [96] BBP (248 ms)
[2020-04-26 16:07:23.039] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:07:23.701] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:07:39.040]  cpu  accepted (109/1) diff 2 [2] BBP (247 ms)
[2020-04-26 16:07:39.706] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:07:41.797] speed 10s/60s/15m 15787.5 16044.2 16387.8 H/s max 16470.0 H/s
[2020-04-26 16:07:42.663]  net  new job from foundation.biblepay.org diff 450442 algo rx/0 height 2085214
[2020-04-26 16:07:50.078]  cpu  accepted (110/1) diff 2 [2] BBP (281 ms)
[2020-04-26 16:08:11.063]  cpu  accepted (111/1) diff 2 [3] BBP (253 ms)
[2020-04-26 16:08:11.732] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:08:20.127]  cpu  accepted (112/1) diff 2 [4] BBP (314 ms)
[2020-04-26 16:08:20.848] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:08:21.204]  cpu  accepted (113/1) diff 2 [2] BBP (391 ms)
[2020-04-26 16:08:21.365] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:08:30.574]  cpu  accepted (114/1) diff 2 [16] BBP (757 ms)
[2020-04-26 16:08:30.736] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:08:41.827] speed 10s/60s/15m 16078.5 16024.7 16358.9 H/s max 16470.0 H/s
[2020-04-26 16:08:58.457]  net  new job from foundation.biblepay.org diff 424781 algo rx/0 height 2085215
[2020-04-26 16:09:04.452]  cpu  accepted (115/1) diff 424781 [874667] XMR (281 ms)
[2020-04-26 16:09:23.290]  cpu  accepted (116/1) diff 424781 [1873313] XMR (894 ms)
[2020-04-26 16:09:26.083]  cpu  accepted (117/1) diff 2 [2] BBP (241 ms)
[2020-04-26 16:09:26.745] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:09:33.086]  cpu  accepted (118/1) diff 2 [21] BBP (239 ms)
[2020-04-26 16:09:33.741] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:09:41.850] speed 10s/60s/15m 15881.0 15920.1 16323.7 H/s max 16470.0 H/s
[2020-04-26 16:09:50.091]  cpu  accepted (119/1) diff 2 [5] BBP (239 ms)
[2020-04-26 16:09:50.754] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:09:55.110]  cpu  accepted (120/1) diff 2 [2] BBP (255 ms)
[2020-04-26 16:09:55.780] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 16:09:56.244]  cpu  accepted (121/1) diff 424781 [911131] XMR (286 ms)
[2020-04-26 16:10:05.620]  net  new job from foundation.biblepay.org diff 455892 algo rx/0 height 2085216
[2020-04-26 16:10:07.152]  cpu  accepted (122/1) diff 2 [3] BBP (293 ms)

I'm going to  let my miner run and see if I can reproduce it now.

The only thought I have is if it happens at a particular height, like the superblock height.  Maybe blocks with more than N transactions get passed down to the solominers.  I do see a few solomined blocks occur per day and that could be the explanation for those.  Those get solved when the pool cant solve the block for more than 30 minutes.

I do see the last superblock was at 191080 (and we are at 191100) now.  Can you tell if it only happened during 191080?

Or is it still going on now?




  • earlzmoade
  • Super Developer

    • 311


    • 48
    • August 02, 2018, 03:22:01 AM
    more
It looks normal now , last it happened was 15 minutes ago , it happened on and off for around 10 minutes.

I heard a dude on discord yesterday also said it happened  for him just one message.

He also had ryzen cpu maybe something with amd cpus.

Looking at the backlog for xmrig i dont see any of these messages during the superblock.
Joshua 1:9
Have i not commanded you?
Be strong and courageous. Do not be afraid;
do not be discouraged, for the Lord your God
will be with you wherever you go.