Bible Pay

Recent Posts

Pages: [1] 2 3 4 5 6 7 8 ... 10
1

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.
2
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.
3
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.

4
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.
5
Hi guys,  the command line params changed today:

https://foundation.biblepay.org/GettingStarted

And the miner download URL;

Please try that!

Thanks!


thanks my friend
6
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.

7
i cant connect to the mining pool too

Hi guys,  the command line params changed today:

https://foundation.biblepay.org/GettingStarted

And the miner download URL;

Please try that!

Thanks!

8

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?
9
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).

10
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
Pages: [1] 2 3 4 5 6 7 8 ... 10