Sent. I changed the WCG_ to WorldCommunityGridUserName (and WorldCommunityGridVerificationCode) in the code for the next release. I believe that is Togos Wiki, Togo if you want you can put to not use underscore in parentheses in the wiki? |
|
|
|
|
Android Mobile version version 1.5.0.7 available in Google Play store
- Support RandomX blocks
- Update CMC price API
And btw all, this is a mandatory upgrade for the mobile devices, because the randomx block size has changed (it has two additional fields), so after 184675, the mobile will not sync unless you upgrade.
MIP, is the iPhone version also released?
|
|
|
|
Ok so I have more information regarding my inability to report BBP shares to the pool.
Unfortunately I am still not showing up on the list of workers, but I did make some progress in other areas. Firstly, I was able to solve the issue of the miner randomly crashing. I set the miner to run in Windows 7 compatibility mode and let it run overnight. Instead of crashing out after just a couple of accepted shares, it now ran successfully without crashing for several hours and has submitted 337 shares (and still going). So that's a great improvement.
Now as for the bigger issue with the pool not seeing my shares, unfortunately that has not changed at all. Even with 337+ shares submitted, I'm still not showing on the BBP worker list. I am no longer able to check the XMR tab to see how many XMR shares I've submitted since that tab doesn't seem to be working. It's just showing blank.
I don't see any reason why it wouldn't be working, everything checked out. Here's what I've tried so far:
Running the miner as administrator.
Launching the miner from an elevated command prompt.
Unblocking the .exe and the winring.sys files.
Adding the mining folder to the exception list of Windows Defender.
Added the individual files in the folder to the exception list of Windows Defender.
Completely disabling Windows Defender.
Added exceptions in Windows Firewall for the mining .exe file.
Completely turned off Windows Firewall.
Tested two versions of the mining .exe - 5.6.2 and 5.6.3.
Successfully telnet to rx.biblepay.org at both ports 3001 and 3020.
Ran the miner at both ports 3001 and 3020.
Generated a new receiving address in the BBP wallet.
Tested mining on a different computer.
Tested mining using a different internet connection.
Tested static IP with Google DNS.
Tested disabling IPv6.
Tested using the --keepalive switch.
That's pretty much everything. Not sure what to try next.
Well, on win7 compatibility mode, the only thing I can say about that is it probably forces your jit compiler to generate slightly different machine code. As I want to point out, the "crash" or silent exit you experience, we do know where that happens and why. Its happening inside the generated machine language, in a stack trace generated by RX's virtual machine (another words, its not in biblepay code). And we know that a segfault cannot be contained safely. Thats why I recommended the goto loop as that is the only safe way to handle that. Just so people dont get the impression that you found a solution to a 'biblepay crash', he found a solution to the jit machine's machine language crash for his particular os and processor. As far as not being able to submit bbp solutions, the only other suggestion I have is to run wireshark on your machine and monitor for the submit share packing (mining.submit). Once you see this going out in wireshark, capture the traffic and see if your machine blocks the submission, or, if it goes out and does not receive a response. The other suggestion is trying a different router and plugging directly into the WAN. It could be software setting in the router resetting the packet outbound. The other suggestion would be uninstalling any software on the machine other than mining software. You might have a proxy of some sort, or a firewall block you are not aware of. Or you can install a virtual machine and try mining in that pristine environment just to prove you can mine. Your house is the only one not mining, so it must be a networking issue in your house. Can you give us a screenshot of the XMR tab not populating? Thats also not happening on any of my machines, and not reported anywhere. Is it that you just have to paste the address in and click lookup? |
|
|
|
The other thing that I can see happening is, I have very little flexibility with nomp to tie orphan URLs, reports, and sponsored miner orphans together (because of the limitations of redis, and Im not willing to bring in nomp-mysql into all this). Do you want to take a poll with miners and see if there's any interest in sponsoring orphans? I can see your conundrum wanting miner and orphan data to be tied together. I've not worked with key-value store databases before (noSQL), but I imagine its not fun joining data together. Whatever you think is best. I like that NOMP allowed us to set up our own independent pools, but I also realize you have bigger plans than NOMP can allow. You have a good heart Rob. May God bless you way. Well thanks, on the poll, either way whether they want to sponsor orphans or not, I'm gleaning some other useful ideas out of this exercise anyway - such as the ability to pull in orphan-bios associated for the entire pool. For example, lets say a satellite pool is generating $60 per month; it would still be valuable to see the 3 orphan bios from SAI that particular pool is supporting. The other thing is, I fear that nomp, if its not very scalable, no database administrator is going to get anyone out of 'a mess' if they cant do any queries in redis. Im at the point where Im a little frustrated with Redis. Im looking into writing a second pool. |
|
|
|
1) In your exec associate command you should not prefix your username with "wcg_". It should just be your wcg username. 2) Your WCG web account username should not have an e-mail suffix. It should just be ksuny for example not ksuny@gmail.com. 3) After you make a change in WCG, you must wait about 12 hours to see the changes propagate. Then try to exec associate again. 4) Id like to see the results of exec associate pasted. None of the screen shots take that output to show. 5) I think we do have a faucet error on web.biblepay.org, but first lets confirm you are associated and in the chain, and then paste your cpid here *after* all that is working. |
|
|
|
Same here, must be a glitch with the BBP daemon. Will come back up soon. Solo miners, enjoy this brief session of luck  I was worrying already that I might be on a fork since I got 8 blocks within the last 6 hours. Thats awesome, just for reference what kind of HPS are you running solo mining? |
|
|
|
Hallo,
Is the pool dead? Only getting XMR charity jobs at the moment...
Same here, must be a glitch with the BBP daemon. Will come back up soon. Solo miners, enjoy this brief session of luck Hmmm, I see an error in the log, something about work queue depth exceeded. Ill restart it and look into the root cause today. |
|
|
|
Hello. How to choose a miner in HiveOS for mining BBP on the RandomX algorithm
I believe first we would need Hive to add us to the custom OS binary links: https://hiveos.farm/getting_started-start_custom_minerIf anyone out there would like to take this on and make the request, ask Hive to add our linux binary (I assume hiveos generally runs on ubuntu) and optionally follow through to see if it works etc. |
|
|
|
Haven't received podc rewards since updating the wallet. Are they simply delayed? Thanks!
They were delayed approx 20 hours due to the slow chain, but, paid 11 blocks ago. block 184725 |
|
|
|
I don't have a comparison ratio handy for XMR vs PODC yet. I think we can do that, once we get a little more XMR info. Maybe we should wait a week then make one. Maybe Sun would like to pick that up as it sounds like it would be very useful if he had some type of updating page, like a payout calculator for one vs the other etc.
I am updating a reward.csv daily and making charts from it. I'm not familiar with XMR so much. My Q2 is extremely full, so I may observe and thinking about it before I actually attempt an ROI calculator. But perhaps a break-even line chart (between sanctuary, podc, heat miner) may work too. Like I previously asked about PoDC RAC to BBP ratio, it is not easy to pull because all the gsc payments are combined for each user. Perhaps if each campaign is paid separately and having unique decimals (like 1527 is for DWS angel number) then I imagine it'd be easier to pull. Anyway, not a big deal, I'm sure I can pull out PoDC RAC to BBP ratio by taking the median value somehow. https://docs.google.com/spreadsheets/d/1ep5G9rG-M460OZYLOd4NHv5sWFDwe_Ow_wop-Fi_SQU/edit#gid=35272442These are all nice reports. Well, maybe I can help over the next week or so. The 'exec price' command displays Dash and BBP so far. Ill make an item on my list to add XMR to this command. Once we have that, we can make another command that gives PODC RAC ratio (RAC->Reward), and then we need yet another call to find out how much each HPS pays from each side of the pool (BBP PPH and XMR PPH). Then I guess we can consolidate it into something useful.
Thank you Rob for your detailed answers. I'm excited to see what the next couple of days hold in store for us. Right now the pool seems to find blocks quite nicely.  Yeah, this RX is kind of funny in that we have double the pool miners already and our diff has gone from 5000 to .26. Its amazing how low the diff is for 2.3 mh/s. Learning from the past, apparently harder is better. |
|
|
|
Hello all, I discovered yesterday that the mandatory upgrade was taking place and upgraded my wallet and also my masternode. Everything went smoothly. Just a couple of quick questions: 1. What is gonna happen to PODC now? Is it (going to be) deprecated, or continuing as before? Is there some kind of prognosis about the profitability PODC vs. BBB/XMR RandomX? 2. My wallet now shows the following versionreport: {
"Version": "Popularity,Percent %",
"1487": "188; 91.70%",
"1507": "17; 8.29%"
}What does that mean for the masternode payments, if currently not even 10% of masternodes are on the right chain? 3. I tried the NOMP pool for RandomX and it works just fine for me (except that my Win10 machine has its RAM too crowded to provide huge pages *lol*). The pool pays matured blocks right away, that means it doesn't collect any balances up to a payout level, right? Is the payout method the same for BBP and XMR? (not that I'm expecting much of a payout anyway with my 2 CPUs  ) Thanks in advance and keep up the good work! God bless you all in these troublesome times. Hi Dave, 1. What is gonna happen to PODC now? Is it (going to be) deprecated, or continuing as before? Is there some kind of prognosis about the profitability PODC vs. BBB/XMR RandomX? -> We don't have plans to retire PODC at all, impho I really like it too. It makes half of our mining "green" and the other half "heat" roughly. We have a breakdown of 30% for GSC, 20% governance, 25% sanc and 25% heat. If RX is a success I could see us lowering POOM (which is 40% of the GSC budget) and moving that to RX, and having RX pay for the POOM expenses. Then later, if its ever more of a success we regroup and consider moving some of the percentages from PODC to RX - but only if we see our price rising due to the success of RX, etc. We have to go with what makes us successful. But for now, we have plenty of room for improvements in other areas. 2. My wallet now shows the following versionreport: {
"Version": "Popularity,Percent %",
"1487": "188; 91.70%",
"1507": "17; 8.29%"
}What does that mean for the masternode payments, if currently not even 10% of masternodes are on the right chain? -> The versionreport actually reports the last 205 blocks, and since we have had a slow chain for 24 hours, its not up to date yet. Please run it in 12 more hours. But I can say this, we must have had a successful upgrade because after the cutover height everyone before 1507 is kicked off. 3. I tried the NOMP pool for RandomX and it works just fine for me (except that my Win10 machine has its RAM too crowded to provide huge pages *lol*). The pool pays matured blocks right away, that means it doesn't collect any balances up to a payout level, right? Is the payout method the same for BBP and XMR? (not that I'm expecting much of a payout anyway with my 2 CPUs ) -> The payment you got was probably from the legacy pool; rx.biblepay.org still pays out after the block has matured, so we have another 105 blocks to go then you should see a payment from that pool. I did change the address to a new wallet so it should show a distinct trail (as we started from scratch with RX). God bless you too. Let me know if I forgot to answer something. |
|
|
|
rx.biblepay.org first bbp block solved i belive! Height 184688 Looking good.  Yes, I'm looking at the pool and everything looks normal now. In hindsight, I wish we would have hardcoded a "50" starting diff for the cutover height, but, that idea wasnt really entertained. NOTE TO US: Remember that next time. So the solo miners solved the first 5, then we had a pool block, then the solo miners solved another one, now we have two more pool blocks. NOTE that I believe the pool has overtaken the solo miners; we will see over the next 100 blocks very clearly as we go; I believe as more RX hashpower comes in from Monero, there will be no way to solo mine a block (when our core diff rises above 20 or so again). |
|
|
|
Question - what IP address / URL does the miner attempt to connect to when it reports a share? I can try pinging it to see if it's blocked.
You can telnet to it, which is slightly better because Ping can be blocked. telnet rx.biblepay.org 3001 You should get a blank screen. I got a blank screen initially, then I got this after a few seconds: {"id":null,"method":"mining.notify","params":["14c",null,"1000005003dbc560105aec1b1ec3f7572205fbd72c17510fdada48fd853ce238cc14830ee3ed544 7a24bdc3e16ee160180480c7e1302bbece9d4916ccdbfa46c6a1bd076e5da7b5ee4a6011c000000 00","0e8314cc38e23c85fd48dada0f51172cd7fb052257f7c31e1bec5a1060c5db03",null,"00000000","1c01a6e4","5e7bdae5",false,"5e7bd65c"]} Yeah, you can connect. If you can try the other two things that might help. Ill try to think of other things we can do. How about right clicking on the bbp-xmrig.exe miner, and ensuring it is "unblocked" and Run as Administrator is checked? Could possibly be network stack blocked at app level. Then restart the mining batch file. And I only have one other suggestion before we do things like wireshark. Try adding "--keepalive" to the end of the params. Unfortunately I tried --verbose logging, and it will not actually give us enough info to help diagnose a packet submission. (I also tried verbose logging to file). --keepalive doesn't work either. Is it possible to solo mine with the miner? Not from xmrig, no, you can only solo mine from the core client. Well I'm out of ideas. Tried downgrading to 5.6.2 and no luck. Even tried using my phone as a mobile hotspot to see if an entirely different internet connection would work, but it didn't. The strange thing is, I actually DID see my BBP address on the pool page for about half an hour this afternoon after I got back from running some errands, but it vanished since then and hasn't come back. What happened with the right clicking of the exe and setting run as administrator checkbox and unblock? |
|
|
|
Question - what IP address / URL does the miner attempt to connect to when it reports a share? I can try pinging it to see if it's blocked.
You can telnet to it, which is slightly better because Ping can be blocked. telnet rx.biblepay.org 3001 You should get a blank screen. I got a blank screen initially, then I got this after a few seconds: {"id":null,"method":"mining.notify","params":["14c",null,"1000005003dbc560105aec1b1ec3f7572205fbd72c17510fdada48fd853ce238cc14830ee3ed544 7a24bdc3e16ee160180480c7e1302bbece9d4916ccdbfa46c6a1bd076e5da7b5ee4a6011c000000 00","0e8314cc38e23c85fd48dada0f51172cd7fb052257f7c31e1bec5a1060c5db03",null,"00000000","1c01a6e4","5e7bdae5",false,"5e7bd65c"]} Yeah, you can connect. If you can try the other two things that might help. Ill try to think of other things we can do. How about right clicking on the bbp-xmrig.exe miner, and ensuring it is "unblocked" and Run as Administrator is checked? Could possibly be network stack blocked at app level. Then restart the mining batch file. And I only have one other suggestion before we do things like wireshark. Try adding "--keepalive" to the end of the params. Unfortunately I tried --verbose logging, and it will not actually give us enough info to help diagnose a packet submission. (I also tried verbose logging to file). --keepalive doesn't work either. Is it possible to solo mine with the miner? Not from xmrig, no, you can only solo mine from the core client. |
|
|
|
Question - what IP address / URL does the miner attempt to connect to when it reports a share? I can try pinging it to see if it's blocked.
You can telnet to it, which is slightly better because Ping can be blocked. telnet rx.biblepay.org 3001 You should get a blank screen. I got a blank screen initially, then I got this after a few seconds: {"id":null,"method":"mining.notify","params":["14c",null,"1000005003dbc560105aec1b1ec3f7572205fbd72c17510fdada48fd853ce238cc14830ee3ed544 7a24bdc3e16ee160180480c7e1302bbece9d4916ccdbfa46c6a1bd076e5da7b5ee4a6011c000000 00","0e8314cc38e23c85fd48dada0f51172cd7fb052257f7c31e1bec5a1060c5db03",null,"00000000","1c01a6e4","5e7bdae5",false,"5e7bd65c"]} Yeah, you can connect. If you can try the other two things that might help. Ill try to think of other things we can do.
Question - what IP address / URL does the miner attempt to connect to when it reports a share? I can try pinging it to see if it's blocked.
You can telnet to it, which is slightly better because Ping can be blocked. telnet rx.biblepay.org 3001 You should get a blank screen. I got a blank screen initially, then I got this after a few seconds: {"id":null,"method":"mining.notify","params":["14c",null,"1000005003dbc560105aec1b1ec3f7572205fbd72c17510fdada48fd853ce238cc14830ee3ed544 7a24bdc3e16ee160180480c7e1302bbece9d4916ccdbfa46c6a1bd076e5da7b5ee4a6011c000000 00","0e8314cc38e23c85fd48dada0f51172cd7fb052257f7c31e1bec5a1060c5db03",null,"00000000","1c01a6e4","5e7bdae5",false,"5e7bd65c"]} Yeah, you can connect. If you can try the other two things that might help. Ill try to think of other things we can do. How about right clicking on the bbp-xmrig.exe miner, and ensuring it is "unblocked" and Run as Administrator is checked? Could possibly be network stack blocked at app level. Then restart the mining batch file. |
|
|
|
Question - what IP address / URL does the miner attempt to connect to when it reports a share? I can try pinging it to see if it's blocked.
You can telnet to it, which is slightly better because Ping can be blocked. telnet rx.biblepay.org 3001 You should get a blank screen.
Question - what IP address / URL does the miner attempt to connect to when it reports a share? I can try pinging it to see if it's blocked.
You can telnet to it, which is slightly better because Ping can be blocked. telnet rx.biblepay.org 3001 You should get a blank screen. And Im not sure if you can try this, but if you can, it would be really helpful to try to run a cat5 cable from a hub to the miner and just try mining that way (in contrast to wifi) just to see if it alleviates the network problem. Ill keep thinking... One other thing; if you try a static IP setting on your miner and set google as the DNS : 8.8.8.8, with a static IP, and try disabling ipv6. It could be that we dont support ipv6 yet. If you keep ipv4 on there checked, that will force all packets through ipv4.
Note about the old pool : nomp.biblepay.org I will bring it up again and keep it on until it pays out the old balances. |
|
|
|
Can the bbp xmrig be compiled with CUDA (nvidia)? This miner is intentionally only CPU right?
This miner already comes with the CUDA code, compiled in it, and afaik its ready to run on GPUs of most every kind (AMD & Nvidia) if you enable the switches. But know that running randomx on video cards is slightly slower than on the CPU (one of the main reasons we ended up going with this, as that should protect us in the future). There is a study in a pdf - I think its embedded in the source code - with hash speeds per architecture and video cards. There is a github discussion between the randomx developers talking about how to hose the video cards. Anyway the idea is, the randomx algo picks the machine language for your platform and runs it with a JIT compiler, so everyone is pretty much "equal". People with more RAM have an edge, but the RAM is also taken into account with cost of ownership too.
Yeah normally i just download directly from github, all about your taste i guess. Directly from pool page also a option. I am using port 3001 on rx.biblepay.org - the block height says 2062258 Height should be 184675. Am I mining on the correct chain? That block height looks awfully high, like it is testnet chain or something... I haven't tried xmrig in a long time, so I could be mistaken too.  What are the huge pages and 1gb pages in your miner? They both show as unavailable for me. Oh wow, we could be on to something with that (I've got your IP and I have been collecting some data btw). Anyway, my numbers arent exactly correct but I believe you need 1 gig of ram per huge page. The miner will automatically use them if it can. I believe you need 256meg of free ram per thread, minimum. How much ram does your machine have? I have 16gb total. Task manager is showing the miner is using 2.3gb for a single thread. Ok thats not it then, anything more than 4gb is probably fine. On a side note the only strange problem I see from your machine so far, is your machine constantly reconnects (about once every 10 minutes), authorizes in the pool successfully, we get your BBP address and Monero address (the correct ones) successfully and give you something to mine, but then we never hear from your machine again (it basically never knows when it solves a BBP share). So either it discards the reply, or, it cant contact us with a solution. Since you dont see rejects on your screen, it sounds as if its not really mining on the bbp side. I did extend the pool server timeout to 10 minutes to try to accomodate that behavior and it appears that did not help your case. Ill have to give you some commands to enable verbose logging. In the mean time is there any way you can try windows mining from another machine, just to ensure that it fails only on one machine? That will help isolating network issues and binary issues. Tried from another machine, no change in behavior. Hmm, that really points to your network then, I would think, since its not happening with anyone else yet. The good news is since we are only on block #2, we can still try to figure other things out. Do you have any strange networking setup, like VPN, and are your machines running any proxies, I mean do the tcp packets flow straight out of the LAN through a normal router?
Yeah normally i just download directly from github, all about your taste i guess. Directly from pool page also a option. I am using port 3001 on rx.biblepay.org - the block height says 2062258 Height should be 184675. Am I mining on the correct chain? That block height looks awfully high, like it is testnet chain or something... I haven't tried xmrig in a long time, so I could be mistaken too. What are the huge pages and 1gb pages in your miner? They both show as unavailable for me. Oh wow, we could be on to something with that (I've got your IP and I have been collecting some data btw). Anyway, my numbers arent exactly correct but I believe you need 1 gig of ram per huge page. The miner will automatically use them if it can. I believe you need 256meg of free ram per thread, minimum. How much ram does your machine have? I have 16gb total. Task manager is showing the miner is using 2.3gb for a single thread. Ok thats not it then, anything more than 4gb is probably fine. On a side note the only strange problem I see from your machine so far, is your machine constantly reconnects (about once every 10 minutes), authorizes in the pool successfully, we get your BBP address and Monero address (the correct ones) successfully and give you something to mine, but then we never hear from your machine again (it basically never knows when it solves a BBP share). So either it discards the reply, or, it cant contact us with a solution. Since you dont see rejects on your screen, it sounds as if its not really mining on the bbp side. I did extend the pool server timeout to 10 minutes to try to accomodate that behavior and it appears that did not help your case. Ill have to give you some commands to enable verbose logging. In the mean time is there any way you can try windows mining from another machine, just to ensure that it fails only on one machine? That will help isolating network issues and binary issues. Tried from another machine, no change in behavior. Hmm, that really points to your network then, I would think, since its not happening with anyone else yet. The good news is since we are only on block #2, we can still try to figure other things out. Do you have any strange networking setup, like VPN, and are your machines running any proxies, I mean do the tcp packets flow straight out of the LAN through a normal router? 2nd question, also, do you have all windows boxes or have you also tried the linux version by any chance?
Praise Jesus, we just solved the second RX block! Diff has dropped to 2033! Should help us much more on the next. Ill investigate to see if it was solo. |
|
|
|
Yeah normally i just download directly from github, all about your taste i guess. Directly from pool page also a option. I am using port 3001 on rx.biblepay.org - the block height says 2062258 Height should be 184675. Am I mining on the correct chain? That block height looks awfully high, like it is testnet chain or something... I haven't tried xmrig in a long time, so I could be mistaken too. What are the huge pages and 1gb pages in your miner? They both show as unavailable for me. Oh wow, we could be on to something with that (I've got your IP and I have been collecting some data btw). Anyway, my numbers arent exactly correct but I believe you need 1 gig of ram per huge page. The miner will automatically use them if it can. I believe you need 256meg of free ram per thread, minimum. How much ram does your machine have? I have 16gb total. Task manager is showing the miner is using 2.3gb for a single thread. Ok thats not it then, anything more than 4gb is probably fine. On a side note the only strange problem I see from your machine so far, is your machine constantly reconnects (about once every 10 minutes), authorizes in the pool successfully, we get your BBP address and Monero address (the correct ones) successfully and give you something to mine, but then we never hear from your machine again (it basically never knows when it solves a BBP share). So either it discards the reply, or, it cant contact us with a solution. Since you dont see rejects on your screen, it sounds as if its not really mining on the bbp side. I did extend the pool server timeout to 10 minutes to try to accomodate that behavior and it appears that did not help your case. Ill have to give you some commands to enable verbose logging. In the mean time is there any way you can try windows mining from another machine, just to ensure that it fails only on one machine? That will help isolating network issues and binary issues. |
|
|
|
Yeah normally i just download directly from github, all about your taste i guess. Directly from pool page also a option. I am using port 3001 on rx.biblepay.org - the block height says 2062258 Height should be 184675. Am I mining on the correct chain? That block height looks awfully high, like it is testnet chain or something... I haven't tried xmrig in a long time, so I could be mistaken too. What are the huge pages and 1gb pages in your miner? They both show as unavailable for me. Oh wow, we could be on to something with that (I've got your IP and I have been collecting some data btw). Anyway, my numbers arent exactly correct but I believe you need 1 gig of ram per huge page. The miner will automatically use them if it can. I believe you need 256meg of free ram per thread, minimum. How much ram does your machine have? |
|
|
|
|
Show Posts
