Bible Pay

Read 21815 times

  • Rob Andrews
  • Administrator

    • 2824


    • 43
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Ive updated the guide :)
- Switched BBP XMRig to Monero XMRig
- Switched Username and Password fields

Question: Is the appending of the .WORKER_NAME thing still useable? Which field should it go on?

Congrats on the successful upgrade for RandomX Rob!

Thanks Togo, and thanks for updating this guide also.

So as far as worker_name please see this page (I updated the field here):

http://foundation.biblepay.org/GettingStarted



  • Rob Andrews
  • Administrator

    • 2824


    • 43
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
I see we are solving RX blocks in the pool with merge-mining!

Congratulations all orphan miners!



  • togoshigekata
  • Hero Member

    • 519


    • 26
    • September 01, 2017, 10:21:10 AM
    • USA
    more
Wait a sec you went on a fork?  How is that possible- unless wait you upgraded after the mandatory height correct?
Just want to make sure we have zero fork risk with chainlocks.

If you upgrade later than block 199K, it is possible that the blockchain will mark the block as "bad" and then you need to either reindex, or, manually mark the block as good (with for example exec reassesschains).

However if you upgraded before 199K you should not be able to go on a fork.

Hmm, I have a 43mb debug.log, looks like I upgraded to correct version then accidentally downgraded haha, I installed latest wallet again, I deleted banlist.dat, deleted chainstate and blocks folders and did a reindex, it synced up!

Code: [Select]
Line 30504: 2020-05-05 17:48:14 ProdMode: Prod 1.000000Core Wallet Version 1.5.0.7 (BiblePay Core)
Line 31744: 2020-05-10 03:56:59 ProdMode: Prod 1.000000Core Wallet Version 1.5.0.7 (BiblePay Core)
Line 34106: 2020-05-23 02:34:38 ProdMode: Prod 1.000000Core Wallet Version 1.5.0.7 (BiblePay Core)
Line 39438: 2020-05-27 03:03:59 ProdMode: Prod 1.000000Core Wallet Version 1.5.0.7 (BiblePay Core)
Line 41614: 2020-05-27 23:31:38 ProdMode: Prod 1.000000Core Wallet Version 1.5.1.4 (BiblePay Core)
Line 42368: 2020-05-30 16:30:17 ProdMode: Prod 1.000000Core Wallet Version 1.5.0.7 (BiblePay Core)
Line 45093: 2020-06-03 01:41:42 ProdMode: Prod 1.000000Core Wallet Version 1.5.0.7 (BiblePay Core)
Line 47676: 2020-06-03 22:09:36 ProdMode: Prod 1.000000Core Wallet Version 1.5.0.7 (BiblePay Core)
Line 60568: 2020-06-03 22:13:38 ProdMode: Prod 1.000000Core Wallet Version 1.5.0.7 (BiblePay Core)

Hmm I cant add an attachment, Ill email it


  • Rob Andrews
  • Administrator

    • 2824


    • 43
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Hmm, I have a 43mb debug.log, looks like I upgraded to correct version then accidentally downgraded haha, I installed latest wallet again, I deleted banlist.dat, deleted chainstate and blocks folders and did a reindex, it synced up!

Code: [Select]
Line 30504: 2020-05-05 17:48:14 ProdMode: Prod 1.000000Core Wallet Version 1.5.0.7 (BiblePay Core)
Line 31744: 2020-05-10 03:56:59 ProdMode: Prod 1.000000Core Wallet Version 1.5.0.7 (BiblePay Core)
Line 34106: 2020-05-23 02:34:38 ProdMode: Prod 1.000000Core Wallet Version 1.5.0.7 (BiblePay Core)
Line 39438: 2020-05-27 03:03:59 ProdMode: Prod 1.000000Core Wallet Version 1.5.0.7 (BiblePay Core)
Line 41614: 2020-05-27 23:31:38 ProdMode: Prod 1.000000Core Wallet Version 1.5.1.4 (BiblePay Core)
Line 42368: 2020-05-30 16:30:17 ProdMode: Prod 1.000000Core Wallet Version 1.5.0.7 (BiblePay Core)
Line 45093: 2020-06-03 01:41:42 ProdMode: Prod 1.000000Core Wallet Version 1.5.0.7 (BiblePay Core)
Line 47676: 2020-06-03 22:09:36 ProdMode: Prod 1.000000Core Wallet Version 1.5.0.7 (BiblePay Core)
Line 60568: 2020-06-03 22:13:38 ProdMode: Prod 1.000000Core Wallet Version 1.5.0.7 (BiblePay Core)

Hmm I cant add an attachment, Ill email it

Thats OK, as long as you know if you ran 1.5.0.7 after 199K then upgraded, that would do it (cause 1507 will mark a block as bad if the height > 199000) and hose the current chain, requiring either exec reassesschains or a resync (or a reindex).



  • Costa82
  • Newbie

    • 24


    • 5
    • April 23, 2020, 09:10:05 PM
    more

Ok, foundation.biblepay.org is now live with merge-mining.

Please upgrade your miner to XMRIG now, otherwise your shares will be rejected.

Our satellite pool has been notified.

Good evening Rob. The old bbprig miner seems to work ok *only checked that it works* when you interchange the pass username in the command.
Is that the case, or regarding to the rejected shares ,  we do still have to upgrade to the xmrig 6.0.0?


  • Rob Andrews
  • Administrator

    • 2824


    • 43
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Good evening Rob. The old bbprig miner seems to work ok *only checked that it works* when you interchange the pass username in the command.
Is that the case, or regarding to the rejected shares ,  we do still have to upgrade to the xmrig 6.0.0?

Good evening Costa!

Yes if you could please switch to any version of the actual Xmrig (by monero) miner, because, we are technically not fully compatible with bbp-xmrig anymore.
And yes you are right the command line params were switched today:

https://foundation.biblepay.org/GettingStarted


Please post if anyone has any trouble!

EDIT:  Switching to XMRig should take care of the invalids also.
I am on xmrig and I have a few but I think they will decrease as we get more hashpower.

« Last Edit: June 03, 2020, 07:28:13 PM by Rob Andrews »


  • Costa82
  • Newbie

    • 24


    • 5
    • April 23, 2020, 09:10:05 PM
    more
i am sorry insisting on this one, but  having tried on XMRIG  5.11.1 and 6.0.0 also, i seem to have my hashrate halved, like the times when i used to mine monero only .
Likewise There is no accepted BBP messages on the miner nor for Monero.

Since i am not that techsavy i always run the command line from the console
( xmrig.exe -o foundation.biblepay.org:3001 -u  -p  --threads nproc_count) and i never mess with the batch file.
It would be highly appreciated if someone could share an example config file of the miner  that the rest of us could work on.
Thank you.


  • Rob Andrews
  • Administrator

    • 2824


    • 43
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
i am sorry insisting on this one, but  having tried on XMRIG  5.11.1 and 6.0.0 also, i seem to have my hashrate halved, like the times when i used to mine monero only .
Likewise There is no accepted BBP messages on the miner nor for Monero.

Since i am not that techsavy i always run the command line from the console
( xmrig.exe -o foundation.biblepay.org:3001 -u  -p  --threads nproc_count) and i never mess with the batch file.
It would be highly appreciated if someone could share an example config file of the miner  that the rest of us could work on.
Thank you.


1) On the hashrate halved, thats normal, (I probably should have mentioned that, sorry).  Yeah, you will now see the half hashrate, but, each hash is still going toward both XMR and BBP now - so in effect its just like it was before (but with half the rate counting 2* for each hash).

2)  On the command line please ensure your BBP address is here:
https://foundation.biblepay.org/GettingStarted

3)  You should definitely see "XMR accepted (N)" for each accepted XMR share (but there are no longer any BBP accepted share messages).
However, each XMR that is accepted should increase your leaderboard for a BBP share now.
If you are increasing BBP in the leaderboard with < 10% stales you are working fine.



  • sunk818
  • Sr. Member

    • 457


    • 27
    • April 24, 2018, 02:02:20 PM
    more
Also, I want to confirm what the mined block amounts should be and what the sanctuary reward should be now after the mandatory. If I'm reading the values right, mined reward went up ~500 BBP and sanctuary reward dropped ~500 BBP? I thought mining reward would move up closer to sanctuary reward and sanctuary reward would stay the same.
BH6oxjLkyz3z8FYpvU3ZR7PTZ31Xt9DkXZ


  • Costa82
  • Newbie

    • 24


    • 5
    • April 23, 2020, 09:10:05 PM
    more

1) On the hashrate halved, thats normal, (I probably should have mentioned that, sorry).  Yeah, you will now see the half hashrate, but, each hash is still going toward both XMR and BBP now - so in effect its just like it was before (but with half the rate counting 2* for each hash).

2)  On the command line please ensure your BBP address is here:
https://foundation.biblepay.org/GettingStarted

3)  You should definitely see "XMR accepted (N)" for each accepted XMR share (but there are no longer any BBP accepted share messages).
However, each XMR that is accepted should increase your leaderboard for a BBP share now.
If you are increasing BBP in the leaderboard with < 10% stales you are working fine.

Excelent, we are good to go then.
Thank you kindly for the reply Rob, i know you are really busy with the project and i really appreciate that you also find time to help the newbies.
God bless you.


  • Radar_Dude7
  • Newbie

    • 36


    • 7
    • April 16, 2020, 08:52:42 AM
    more
Good morning, Rob et al.

Been receiving a 'connection reset by peer' error since yesterday at around 4 pm EDT. I understand that we are now using the straight XMRig. I installed 5.11.2 and ensured that I re-arranged my CLI command to match the new format, listed above in the 'Get Started' page. Still receiving the reset error.

Can you offer any guidance? Thanks for all you do!


  • Rob Andrews
  • Administrator

    • 2824


    • 43
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Good morning, Rob et al.

Been receiving a 'connection reset by peer' error since yesterday at around 4 pm EDT. I understand that we are now using the straight XMRig. I installed 5.11.2 and ensured that I re-arranged my CLI command to match the new format, listed above in the 'Get Started' page. Still receiving the reset error.

Can you offer any guidance? Thanks for all you do!

Hmm, can you please provide your BBP address and I will need to add some type of trace and confirm if you are mining against foundation.biblepay.org also?

PS:  We do disconnect if the BBP address is not 34 chars long (its in the password field), but I doubt thats it since you had it working for hours.


  • Rob Andrews
  • Administrator

    • 2824


    • 43
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
** Increased Dynamic Whale Stake Rewards after block 199,000 ! **

Type in 'exec dws' into the console and retrieve the latest whale stake quote:
43.3% return on your stake!

Post here if anyone needs help burning BiblePay for an annual whale stake reward.

EXAMPLE BURN:

exec dws 212000 180 I_AGREE

The above command burns 212K for 180 days for a 32% reward.

(Shorter durations have a lower reward than longer).

I think this caught someones interest, because I see 5 mil in burns over the last 24 hours and 4 mil missing in SX sell book.

I'm happy about that because we really need a free floating environment again (on SX).  Those 40 mil coins (for sale) have been sitting there since we retired the first version of PODC.



  • Radar_Dude7
  • Newbie

    • 36


    • 7
    • April 16, 2020, 08:52:42 AM
    more
Hmm, can you please provide your BBP address and I will need to add some type of trace and confirm if you are mining against foundation.biblepay.org also?

PS:  We do disconnect if the BBP address is not 34 chars long (its in the password field), but I doubt thats it since you had it working for hours.
Hi Rob - thanks for the quick reply. Here is my address: BG4qhDsU8oDWp9ZN42Q395KJvUFvupZGM8
I have been using this address for quite some time now and have been mining actively since yesterday afternoon. BTW - I want to ensure that you understand that I have just today downloaded XMRig plain and have not had success using it yet.
Lastly, the instructions on the Getting Started page say to place your User Name as the BBP address and then the command is in the password position. Was this on purpose? Thanks again.


  • Radar_Dude7
  • Newbie

    • 36


    • 7
    • April 16, 2020, 08:52:42 AM
    more
Sorry - I messed up. I meant to say that I have been mining regularly UNTIL yesterday afternoon.