Bible Pay

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - earlzmoade

Pages: [1] 2 3 4 5
1
General Support / How to setup failover pool in Xmrig - tutorial
« on: June 19, 2020, 03:06:56 AM »
Firstly i assume that you already have Xmrig installed on your computer, if not you can get it at https://xmrig.com/ or at their  github to get latest release https://github.com/xmrig/xmrig/releases.

If you are using the  config file you can do like this:

Open up config file with lets say notepad and scroll down to pool configuration section.

Code: [Select]
{
            "algo": null,
            "coin": "null",
            "url": "foundation.biblepay.org:3001",
            "user": "Your_monero_adress.your_preferred_workername",
            "pass": "Your_biblepay_adress",
            "rig-id": null,
            "nicehash": false,
            "keepalive": false,
            "enabled": true,
            "tls": false,
            "tls-fingerprint": null,
            "daemon": false,
            "socks5": null,
            "self-select": null
        }

Just copy and paste your pool configuration and add a comma  in the end.

Should look like this when you have failover pool setup:

Code: [Select]
{
            "algo": null,
            "coin": "null",
            "url": "foundation.biblepay.org:3001",
            "user": "Your_monero_adress.your_preferred_workername",
            "pass": "Your_biblepay_adress",
            "rig-id": null,
            "nicehash": false,
            "keepalive": false,
            "enabled": true,
            "tls": false,
            "tls-fingerprint": null,
            "daemon": false,
            "socks5": null,
            "self-select": null
        },
        {
            "algo": null,
            "coin": null,
            "url": "bbp.miningpool.fun:3001",
            "user": "Your_monero_adress.your_preferred_workername",
            "pass": "Your_biblepay_adress",
            "rig-id": null,
            "nicehash": false,
            "keepalive": false,
            "enabled": true,
            "tls": false,
            "tls-fingerprint": null,
            "daemon": false,
            "socks5": null,
            "self-select": null
             }

First pool configuration from top will be your primary pool and the one below is  your failover pool, you can set more failover pools if they are available.

Added some picture links aswell: https://imgur.com/a/NoyS7Fo

If you are using the command line or made a batch file it would look like this:

Code: [Select]
xmrig.exe --donate-level 1 -o bbp.miningpool.fun:3001 -u Your_monero_adress.your_preferred_workername -p Your_biblepay_adress -k -o foundation.biblepay.org:3001 -u Your_monero_adress.your_preferred_workername -p Your_biblepay_adress -k



2


Quote
and this is correct on the RAM?
"RandomX uses up 256Meg of memory per mining thread"?, Thanks!

No i dont think so, atleast from what i understand..
So no matter what your cores/threads the miner will allocate little more then 2gb per cpu for fast mode which desktop pcs use.
The higher ram needed  is good to discourage botnets and what not.

Doing some quoting here:

Quote
RandomX can operate in two main modes with different memory requirements:

Fast mode - requires 2080 MiB of shared memory.
Light mode - requires only 256 MiB of shared memory, but runs significantly slower

Quote
16 KiB of L1 cache, 256 KiB of L2 cache and 2 MiB of L3 cache per mining thread
(for optimal performance)

Quote
At least 2.5 GiB of free RAM per NUMA node
Multiple memory channels may be required:
DDR3 memory is limited to about 1500-2000 H/s per channel (depending on frequency and timings)
DDR4 memory is limited to about 4000-6000 H/s per channel (depending on frequency and timings)



The ram usually not a problem.  Whats imortant would be how much cache the cpu has for example why new Ryzen cpus are so good at randomX is because of the high amount of cache they have.

So lets say a intel 9900k 8c/16 threads which has L1 cache 512 KiB, L2 cache 2 MiB, L3 cache 16 MiB. Due to the l2/l3 cache limitations that even though you have 16 threads any more then 8 threads will not give any boost in hashrate.

Then look at lets say 3700x 8c/16t which has L1 cache 512 KiB, L2 cache 4MiB, L3 cache 32 MiB. There we have enough cache to utilize  all the 16 threads for optimal performance.






3
I created first draft of a RandomX mining guide
https://wiki.biblepay.org/RandomX_Setup

Any and all feedback welcome!

=


The guide looks fine to me. Nice work Togo! 

Suppose you could add the more technical stuff for RandomX   cpu threads, like how much cache is needed per mining thread for optimal performance, then people could do some basic calculations themselfs for their cpu.

https://github.com/tevador/RandomX 

There some more  information.

Also could add in  monerobenchmark  website with alot of diffrent configurations and cpus. https://monerobenchmarks.info/

Anyways just some ideas that i had.


4
Sanctuary Discussions / Re: Raspberry pi 4 2gb/4gb
« on: June 06, 2020, 11:11:32 AM »
Project is  getting along well, have bought all the necessery hardware.

Now i will just get some more bbp and then see if i can get a home sanctuary up n running  :)

https://imgur.com/VrE6upI


5
Hey!

when do you think the mining issue is fixed? I am still not be able to get shares, and i also see the username / password has been switched so i changed that in my config also. However, the mining part still not work.

You can come to discord and we can try to help you with the configuration.

6
Have finally upgraded all my miners to latest xmrig...  Looks like it works really good.   Thanks for your time and effort Rob!

Hence we use official xmrig miner now, is it possible to have a backup pool ?  Like this for example in the config.json:

Code: [Select]
"pools": [
        {
            "url": "foundation.biblepay.org:3001",
            "user": "your_monero_adress",
            "pass": "your_biblepay_adress",
            "keepalive": true,
            "nicehash": false
        },
        {
            "url": "bbp.miningpool.fun:3001",
            "user": "your_monero_adress",
            "pass": "your_biblepay_adress",
            "keepalive": true,
            "nicehash": false

7
Sweet!

Quote
Removing "BiblePay-Evolution" from the windows wallet and fixing the default program directory name (it is still Evolution).  This should go back to BiblePay.  Check to see if the windows installer wizard is correct.


Biblepay installs correct folder for w10, no more evolution.

Quote
- 'exec price' : XMR price has been added

I tested now in console and looks just fine.

Code: [Select]
14:35:50

exec price


14:35:55

{
  "Command": "price",
  "BBP/BTC": "0.000000019000",
  "DASH/BTC": "0.008088008000",
  "XMR/BTC": 0.0069188835,
  "BTC/USD": 9315.602001499999,
  "DASH/USD": 75.34466351294802,
  "XMR/USD": 64.45356498074533,
  "BBP/USD": 0.0001769964380285
}

8
It looks fine for me now, seems it was just during 22 may i was getting that miner ip block thing....
Nor do i have botnet with computers or such, i got 8 rigs running..

I guess just mineXMR doing something..

Quote
And, of course we are also working on standard merge-mining for our June release so that we dont have a specific risk (IE if minexmr goes down we go down), so that is happening too.

Sounds awesome!  Keep up the nice work!  ;D

9
I have been real busy with work, im working at cemetery.

Anyhow i cant help out with the masternodes  but tomorrow i will test out some of the other stuff that you posted Rob and will give some feedback.
Hope all is fine in these times// earlz

PS : It looks like the Testnet download link for windows downloads the older 1.5.0.5 version

10
I have been real busy with work, im working at cemetery.

Anyhow i cant help out with the masternodes  but tomorrow i will test out some of the other stuff that you posted Rob and will give some feedback.
Hope all is fine in these times// earlz

11
Hey Rob.

Was checking log for dual miner and i get these messages:

Code: [Select]
[2020-05-22 17:23:57.015] speed 10s/60s/15m 16463.3 16449.0 16445.0 H/s max 19799.5 H/s
[2020-05-22 17:24:07.563]  cpu  rejected (3045/101) diff 354926 [676403] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (303 ms)
[2020-05-22 17:24:07.934]  cpu  rejected (3045/102) diff 354926 [507614] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (285 ms)
[2020-05-22 17:24:33.225]  net  new job from foundation.biblepay.org diff 345365 algo rx/0 height 2103950
[2020-05-22 17:24:48.879]  cpu  accepted (3046/102) diff 7 [7] BBP (357 ms)
[2020-05-22 17:24:57.038] speed 10s/60s/15m 16451.8 16438.6 16444.4 H/s max 19799.5 H/s
[2020-05-22 17:24:57.384]  cpu  rejected (3046/103) diff 345365 [639672] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (1452 ms)
[2020-05-22 17:25:45.563]  cpu  rejected (3046/104) diff 345365 [804752] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (293 ms)
[2020-05-22 17:25:57.068] speed 10s/60s/15m 16464.1 16455.0 16444.4 H/s max 19799.5 H/s
[2020-05-22 17:26:07.069]  cpu  rejected (3046/105) diff 345365 [465059] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (1670 ms)
[2020-05-22 17:26:46.113]  cpu  rejected (3046/106) diff 345365 [583328] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (287 ms)
[2020-05-22 17:26:57.092] speed 10s/60s/15m 16460.7 16454.4 16444.6 H/s max 19799.5 H/s
[2020-05-22 17:27:14.116]  net  new job from foundation.biblepay.org diff 330509 algo rx/0 height 2103950
[2020-05-22 17:27:31.473]  cpu  rejected (3046/107) diff 330509 [2146629] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (295 ms)
[2020-05-22 17:27:57.120] speed 10s/60s/15m 16463.3 16454.3 16444.6 H/s max 19799.5 H/s
[2020-05-22 17:28:14.907]  cpu  rejected (3046/108) diff 6 [27] BBP "Stale" (292 ms)
[2020-05-22 17:28:16.925]  cpu  rejected (3046/109) diff 6 [22] BBP "Stale" (311 ms)
[2020-05-22 17:28:19.913]  cpu  rejected (3046/110) diff 6 [186] BBP "Stale" (299 ms)
[2020-05-22 17:28:25.893]  cpu  rejected (3046/111) diff 330509 [364286] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (295 ms)
[2020-05-22 17:28:33.918]  cpu  rejected (3046/112) diff 6 [8] BBP "Stale" (297 ms)
[2020-05-22 17:28:46.931]  cpu  rejected (3046/113) diff 6 [15] BBP "Stale" (304 ms)
[2020-05-22 17:28:48.915]  cpu  rejected (3046/114) diff 6 [8] BBP "Stale" (288 ms)
[2020-05-22 17:28:50.035]  cpu  rejected (3046/115) diff 330509 [359717] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (586 ms)
[2020-05-22 17:28:52.079]  net  new job from foundation.biblepay.org diff 322178 algo rx/0 height 2103951
[2020-05-22 17:28:55.187]  cpu  rejected (3046/116) diff 322178 [1307535] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (275 ms)
[2020-05-22 17:28:57.140] speed 10s/60s/15m 16446.7 16424.6 16445.7 H/s max 19799.5 H/s
[2020-05-22 17:29:03.916]  cpu  rejected (3046/117) diff 1 [1] BBP "Stale" (284 ms)
[2020-05-22 17:29:14.007]  cpu  rejected (3046/118) diff 322178 [330347] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (1457 ms)
[2020-05-22 17:29:16.881]  cpu  rejected (3046/119) diff 322178 [2403792] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (1176 ms)
[2020-05-22 17:29:20.941]  cpu  accepted (3047/119) diff 1 [1] BBP (299 ms)
[2020-05-22 17:29:23.918]  cpu  accepted (3048/119) diff 1 [1] BBP (277 ms)
[2020-05-22 17:29:25.061]  cpu  accepted (3049/119) diff 1 [1] BBP (420 ms)
[2020-05-22 17:29:32.245]  net  new job from foundation.biblepay.org diff 316878 algo rx/0 height 2103952
[2020-05-22 17:29:34.912]  cpu  accepted (3050/119) diff 2 [4] BBP (266 ms)
[2020-05-22 17:29:37.935]  cpu  accepted (3051/119) diff 2 [4] BBP (287 ms)
[2020-05-22 17:29:50.829]  net  new job from foundation.biblepay.org diff 316878 algo rx/0 height 2103953
[2020-05-22 17:29:57.163] speed 10s/60s/15m 16448.4 16441.2 16445.8 H/s max 19799.5 H/s
[2020-05-22 17:29:58.939]  cpu  accepted (3052/119) diff 4 [5] BBP (284 ms)
[2020-05-22 17:30:04.954]  cpu  accepted (3053/119) diff 4 [136] BBP (294 ms)
[2020-05-22 17:30:06.068]  cpu  accepted (3054/119) diff 4 [136] BBP (409 ms)
[2020-05-22 17:30:18.792]  net  new job from foundation.biblepay.org diff 314281 algo rx/0 height 2103953
[2020-05-22 17:30:24.790]  cpu  rejected (3054/120) diff 314281 [335514] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (293 ms)
[2020-05-22 17:30:47.360]  cpu  rejected (3054/121) diff 314281 [397291] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (288 ms)
[2020-05-22 17:30:48.739]  net  new job from foundation.biblepay.org diff 311726 algo rx/0 height 2103954
[2020-05-22 17:30:57.187] speed 10s/60s/15m 16453.1 16445.0 16445.5 H/s max 19799.5 H/s

And i noticed the  xmr charity adress  also  looks like the hashrate over there  is way to low. 
Hmm any ideas?

12
Hey Rob.

For wishlist i would like to add in  backup xmr pools, like hashvault.pro , supportXMR.com, nanopool.com, xmrpool.eu etc etc...   
Some pools that have good reputation with payouts and what not.

Its a feature that i think alot of people would appreciate, perhaps more towards "bigger" miners.


13
Unfortunately I cant find this issue in the log and my miner hasnt encountered it yet;
I made a change on the server to transmit its json reply slightly differently;
Lets see if it happens again; if it does could you please give me your bbp address and Ill try to add a more specific piece of logging for that so we can trap it.

Yeah ofcourse. It dosent look to me like anything happens with the mining per say except for the message so to say.

Code: [Select]
[2020-04-26 19:47:45.430] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 19:47:53.581] speed 10s/60s/15m 16322.7 16395.8 16387.7 H/s max 17063.5 H/s
[2020-04-26 19:48:01.327]  net  new job from foundation.biblepay.org diff 483558 algo rx/0 height 2085325
[2020-04-26 19:48:10.758]  cpu  accepted (641/6) diff 18 [30] BBP (242 ms)
[2020-04-26 19:48:11.426] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 19:48:53.614] speed 10s/60s/15m 16386.8 16410.5 16387.6 H/s max 17063.5 H/s
[2020-04-26 19:48:55.792]  cpu  accepted (642/6) diff 18 [25] BBP (259 ms)
[2020-04-26 19:48:56.460] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 19:49:53.642] speed 10s/60s/15m 16396.1 16390.4 16386.4 H/s max 17063.5 H/s
[2020-04-26 19:50:52.119]  cpu  accepted (643/6) diff 483558 [505691] XMR (307 ms)
[2020-04-26 19:50:53.675] speed 10s/60s/15m 16411.9 16362.3 16382.9 H/s max 17063.5 H/s
[2020-04-26 19:51:16.948]  cpu  accepted (644/6) diff 483558 [720376] XMR (292 ms)
[2020-04-26 19:51:28.955]  net  new job from foundation.biblepay.org diff 471352 algo rx/0 height 2085326
[2020-04-26 19:51:40.878]  cpu  accepted (645/6) diff 471352 [536149] XMR (304 ms)
[2020-04-26 19:51:53.706] speed 10s/60s/15m 16383.1 16402.8 16382.5 H/s max 17063.5 H/s
[2020-04-26 19:51:55.925]  cpu  accepted (646/6) diff 18 [19] BBP (325 ms)
[2020-04-26 19:51:56.593] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."
[2020-04-26 19:52:15.860]  cpu  accepted (647/6) diff 18 [22] BBP (251 ms)
[2020-04-26 19:52:16.523] [foundation.biblepay.org:3001] JSON decode failed: "Missing a comma or ']' after an array element."

So i belive 4-5 hours between the 2 episodes.

My adress is:  BBFfgmZhTdNXPYzk7hZnYA9j27mCSZVYB1

14
BiblePay discussion / Re: RandomX Giveaway for New RandomX Miners
« on: April 26, 2020, 01:48:28 PM »
I really liked this project ... I will look for more miners to help in this noble cause ... thank you for the opportunity to help and be helped.

Thank u

15
Ok thanks, that helps a lot, as it sounds like it has nothing to do with the size of the block, it sounds more like a malformed message but, thats kind of strange because the messages are all the same length.

I think I will be able to add a log that shows this later today then we can figure it out.

Right now Im getting some database data for Song to start another mining pool.  So ill post again as soon as I get some type of logging in there.

No problem.

Just figured i could do some feedback.


Pages: [1] 2 3 4 5