1711
Archived Proposals / Re: RandomX Giveaway for New RandomX Miners
« on: March 31, 2020, 02:04:42 PM »BDqBhSccJqqe262DP7Y8x5QMhDShojwfg8-0-188-168-21-206
Sent, and welcome aboard!
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.
BDqBhSccJqqe262DP7Y8x5QMhDShojwfg8-0-188-168-21-206
BNiBV6Abeqd4XK56fBRb5PL8K1LxGbrkdN-0-159-148-142-214Sent, and welcome aboard!
Sorry for the delay. Sent!
Got it, thanks!
BEnG96E4bTH9JDXhnDUFMnZ6k1XCnMXq8o-10-68-4-207-37
BRwZqE6HFHrLAFJwHubTEJAwDbo7FGWfAv-27-141-237-237-55Sent, and welcome aboard!
Hi Rob! The command faucetcode doesn't seem to work in the console. I am using 1.5.0.7. Thanks!
BCrVXG8defzw28H5JMbmofSz2drRr3yoyQ-0-193-95-249-3
:miningloop
xmrig.exe -o rx.biblepay.org:3001 -u bbpaddress -p moneroaddress --threads=8
goto miningloop
Pinning this for the future in case anyone else has this issue (a silent exit by the miner after a random amount of time, especially on ryzen 1700s):
https://www.reddit.com/r/MoneroMining/comments/e4k7cq/xmrig_ryzen_7_1700_fix/f9e676q/
So there is a workaround, (Im experiencing this myself), we can make a loop in a batch file like this (pretend this is miner5.bat):
:miningloop
xmrig.exe --params
goto miningloop
I will probably be doing this myself.
And just to give a little background on the problem, first of all there is a CPU setting on some motherboards called 'opcache' that might fix the underlying issue.
But the reason we aren't trying to handle this inside the program is since the JIT machine language is generated on the fly, the actual error signal is a segfault, but in a machine language area that can't have an error catch around it - and - segfaults cause program instability if you try to program around them. Another words the only safe way to handle this is to let the process die and restart the process at the OS level.
Hopefully not many of our users will have to do this - but I appear to be one in this category with my early version of the 1700, etc.
I havent tried the bios change yet but Ill post if it works later.
configuring rigs so they are ready for mainnet launch
2 more days right, will be intresting!
Ok, so I did have to expose the XMR Charity address in the pool configuration file, that is being checked in now.Test
Now all, you can go to the home page of the pool (rxtest.biblepay.org) - in the 4th row under Global Stats - and see:
- The XMR Charity address (this lets people monitor the pools gains per month. You can just paste the charity address in the XMR lookup tab btw and see the mined amount - easier than monitoring the XMR wallet balance).
- The picture of an orphan
- The suggestion that Earl made on the configuration option for the last option
Afaik, I think we are ready to go live.
Are there any other requirements for the pool besides updating the code and daemon? Do I need to add a Monero wallet or anything like that?
You would need a monero SPV prod wallet address (like a miner has), dedicated for the pool.
While you are getting that, let me see if we need any code changes to expose the address on the front page of the pool for people to see how much charity we collected.
What Im thinking is we leave it like this for 3-4 months and then reassess the situation. If the satellite pools only collect say less than $100 per month (and successfully spend it on orphan charity for biblepay) Im not in a super hurry to re-write the whole pool in c# just yet.
But we will need to agree on some type of liquidation plan even in this interim stage. Im thinking about doing this: SAI.NGO (Venezuelan orphans) has agreed to allow us to sponsor 20-30 orphans. Once I pay for those upfront (out of my own pocket), I think I will ask Steve if he will be willing to accept XMR payments from us.
I will most likely ask you to send your monthly donation to him, and for now that will be the benefit (and of course we will give you the bios of the orphans your pool is sponsoring through SAI) so you can post those bios on one of your pool pages, etc.
It's mainly lack of time for signing and for testing because of the CV emergency. I will try to create a signing script and DMG today. Without signing, anyone can use the binary but disabling the gatekeeper protection for that specific binary.
Are there any other requirements for the pool besides updating the code and daemon? Do I need to add a Monero wallet or anything like that?