Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 10. (Read 243417 times)

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?

Sure, no problem.  Here is a screenshot.  It happens on all web browsers but was working fine just a couple days ago.



https://1drv.ms/u/s!AjuxSfKebyTRgcFIBZKV6Y2xf8Q6UA

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?

CPID---f8c2cf21c724f019c300c1ae8d98eb71

http://c.radikal.ru/c34/2003/7e/1760eb33f02c.jpg

http://c.radikal.ru/c08/2003/19/a7425b97404a.jpg

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.

I receive PC notifications for incoming rewards although some of them are never credited to my wallet. Both solo wallet mining and Boinc. Any thoughts?

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.

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.

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 [email protected].
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.

Sorry, Invalid Destination Address (Code: 65002) when trying to enter your address and CPUID on the screen gives this error

Android Mobile version   version 1.5.0.7 available in Google Play store

- Support RandomX blocks
- Update CMC price API

minexmr.com's SSL configuration is causing issues for some people. I don't know if it is related to your pool issues. Also, their certificate is expiring in 3 days. I've let them know, but not sure if that's an issue too. Anyway, it is possible the rx's issues may be related to the upstream xmr pool.

Welp, I didn't upgrade yet and was on a fork indeed

But just wallet mining solo, yeah.

How do you solo mine? Just wallet mining solo? It is only for BBP (but not XMR I assume).

About 197k hps with a Ryzen 1700X with 32 genproclimit.

Thats awesome, just for reference what kind of HPS are you running solo mining?

I was worrying already that I might be on a fork since I got 8 blocks within the last 6 hours.

Hmmm, I see an error in the log, something about work queue depth exceeded.

Ill restart it and look into the root cause today.

Same here, must be a glitch with the BBP daemon. Will come back up soon. Solo miners, enjoy this brief session of luck

Hallo,

Is the pool dead? Only getting XMR charity jobs at the moment...