-
Notifications
You must be signed in to change notification settings - Fork 1
Home
Welcome to the pawcloud-xmr wiki!
Here you can learn just a little bit about this project with this Quick (-er than normal) Start Guide.
PawCloud is a toolchain designed for exoscale that will allow you to easily mine monero (XMR, rx/0 currently) using the platform. More CPU coins may be supported in the future, but monero is the most profitable way for now.
To get started, move on over to exoscale and create an account. Verification takes a while. When complete, you will be able to warm up a few pawcloud instances. Before you do so, there are some perliminary steps.
-
On 8 instances with 8 vCPUs pawcloud mines approximately 0.05 xmr per day at a rate of 36-50 kh/s or $19.48 USD at the time of writing.
-
It costs $0.19 an hour on x19 2 vCPU nodes to run your proxy + your instance pool which is another $0.035 which is $0.22 an hour
-
We'll go ahead and multiply that by 24 to get $5.28 a day in exoscale costs
-
Subtract the exoscale costs of $5.28 a day from the mining profits of 19.48 USD a day and you get $14.20 a day in profits
-
Multiply this by 30 to get your profits per month which is $426.00
-
If you want to know how much you're going to refill your exoscale account with, the figure is in CTF or CryptoDask, we'll convert that from USD of $0.22 an hour to a weekly figure. Billing weekly is easy to manage... So that's $5.28 a day
-
Multiply $5.28 from earlier by 7 and you get $36.96 a week in USD
-
Lets do our reading-writing-arithmetic and google up the current exchange rate for CTF which is: 0.64103 to 1 USD. Multiply $36.96 a week by 0.64103 and you get 23.3228688 CTF or somewhere around:
25 CTF / $37 bucks a week to run PawCloud!
At a profit of $426.00 a month
Profitable? YES!
Check the releases section, and download the tarball. You will need to go through and remove my wallet address and my choice of supportxmr pool. Configure the embedded json bash here documents to your liking. These are only minor changes. Be very careful of syntax errors!
Pawcloud needs its own private network on 10.0.0.1/24 to function correctly, which allows you to have a maximum of 254 nodes running through its proxy. You will need to create a "Managed" private network with this configuration. When you are done, continue.
You should use the following configuration:
| Name | Setting |
|---|---|
| Hostname | pawcloud-proxy |
| OS | Ubuntu 20.04 LTS |
| Instance Type | Small 2 vCPU |
| Memory | GB 2 x 2198 MHz |
| Disk | 10 GB |
Paste the contents of config_proxy.yaml into the UserData field. Verify that all of the information is correct, and then spawn the instance.
I know, this step takes patience. But you are to wait a good 15 minutes. At this stage, save your ssh password, as it comes in handy for maintenance purposes. You will be unable to save your password if you refresh the page, so keep this in mind. Write it down, or put it in a safe place. The default username is still ubuntu.
If you ever want to check on your instance, you can log into PuTty with the Instance IP and the password that you have saved here.
After a time, you may notice proxy is not up, and not accepting blocks from the pool. Why is this? Well, this is because I don't want to have to write an entire python api for exoscale, to automanage your instances. Go to your instance manager screen for pawcloud-proxy, scroll to the bottom, and change your Private Network IP to 10.0.0.2, and then reboot your instance.
Log in to your instance with PuTty, and then send commands:
su - nodeproxy
password: pawcloud-proxy1
pm2 log proxyYou should see that the proxy has been accepting some blocks, and that there are no miners connected. This is normal, and it means that your proxy instance is working correctly. You may want to keep this PuTty window open, as your next step is to install your node.
What is the Prime Node? The prime node is the main image that contains a node that connects to the pawcloud-xmr-proxy head node. There can be any number of these nodes, up until your quota limit. On a standard account, you can have many of these. I would recommend for price reasons a 8 vCPU node for your miner node. You can use the following to start with:
| Name | Setting |
|---|---|
| Hostname | pawcloud-node |
| OS | Ubuntu 20.04 LTS |
| Instance Type | CPU Large 16 vCPU |
| Memory | 16 x 2198 MHz |
| Disk | 10 GB |
Using this offering takes $0.19 an hour, you should not go above $0.30 an hour offerings or else this is no longer profitable. This is why we no longer use AWS or Azure to mine, they are too expensive and make it an unprofitable process, and no longer splendid.
We like the splendid process here at pawcloud, those only. :-)
You should paste the contents of config_node.yaml from the repository into the UserData field provided.
We are waiting again this time for our node to come up. Why don't you stand up and have a stretch? Its good for you. Maybe grab a cup of coffee or actually take care of your doge? You may need to wait 30 minutes or so. During this time, ensure that you save your prime node SSH password before closing the page! Put this in a safe place, or write it down.
Log into your node, and issue the following:
sudo systemctl status xmrnode.serviceYou should see that the xmrig process is mining. If you have a connection error, you have not configured your proxy's Private Network underneath the instance manager properly. Ensure that it has the IP of 10.0.0.2, and then reboot both of your instances and wait again...
Log into your pawcloud-proxy node again, and you should see your miner submitting shares. If you have messages like 'Invalid Block Data' than you have invalidly configured your json in xmr-node-proxy. As the copy provided is from my repository and contains the default of my wallet address and pool address, you probably ran into this one, and need to make changes to /home/nodeproxy/xmr-node-proxy/config.json, which is fine. You can use nano text editor to do that while logged into the pawcloud-proxy, like so:
su - nodeproxy
password: pawcloud-proxy1
nano ~/xmr-node-proxy/config.jsonAfterwards, you will need to restart your proxy to apply your changes.
pm2 stop proxy
pm2 start proxy
pm2 save
At any given point in this, remember that to check your proxy logs for debugging, you will be using:
pm2 log proxy
If you have any configuration errors, the proxy will have crashed, and you will see the error here in the log.
At this stage, you should have a working prime node connected to a working proxy instance. From here, I would recommend taking a snapshot of your prime node, and then creating a template from your prime node snapshot with the exo.exe command line tool:
exo vm template register pawcloud-primenode ^
--from-snapshot [get this guid from the instance manager Snapshot page] ^
--description "PawCloud-XMR Mining Node" ^
--zone de-fra-1 ^
--username ubuntu ^
--boot-mode uefi ^
--disable-ssh-keyYou can now use your template to spawn more nodes in an instance pool! These nodes will auto-connect to the proxy and start mining through the proxy! Move to the instance pool tab to create a new pool. Ensure that it is on the Private Network we configured and DO NOT select an Ubuntu Base image, you will move to the grey person on the right, and select pawcloud-primenode user template for your instance pool. See? Isn't that convenient.
After spawning your pool, it can take up to 30 minutes. Go to your mining dashboard, and watch your hashrate soar to crazy heights over time! Its like a parabola of income! How exciting!
I know I did! Support is not offered beyond the scope of this documentation. You should learn and figure out some things yourself, like xmr-node-proxy's options, and xmrig's options. As everything is default, you can't just install this and forget it unless you want to mine directly to me for donations! (Hey if you do, I appreciate that, but you should learn how to configure things yourself!)
Mau~! Thank you for trying out pawcloud-xmr-proxy.
~ HeavyPaws