Keep in mind that solo mining is a lottery. Miners win block rewards randomly. You could be lucky and find a block in 1 minute or it could take a month or two to win a block. On average, miners will get rewards about the same as pools, but you have to look at it from the long term (months, not day to day). If you are looking for instant gratification, you are better off just mining XMR on a large pool.
Besides the financial interest in mining, there is also an ideological dimension. By solo mining, you are contributing to the project by helping to make the network more secure. Wownero is made up of altruistic, unpaid volunteers doing this stuff for fun. There was no premine, dev tax, or scammy "fast mined" emission curve like in other projects. If you don't have coding skills or the financial resources to donate towards proposals or the development fund, even if you never win a block, you can do your small part by solo mining. Every hash counts. The more decentralized nodes and miners there are, the stronger the network.
First, get a Wownero wallet address. You could use Wowlet](https://git.wownero.com/wowlet/wowlet/releases), [Wowstash](https://wowstash.app), [Wonerujo](https://forum.wownero.com/t/how-to-install-wonerujo-android-wallet/358), [wownero-wallet-cli](https://git.wownero.com/wownero/wownero/releases), or a [paper wallet (https://wownero.github.io/wownero-wallet-generator/wownero-wallet-generator.html).
You will need to use your "main address" (starts with "**Wo**") to mine, not a "subaddress" (starts with "WW"). You would use subaddresses when making transactions with other people in order to better protect your identity (https://localmonero.co/knowledge/monero-subaddresses?language=en). For mining, since you are directly interacting with the network, you only need your main address to start mining. If you are using Wowlet, to get the main address, click on "Wallet", and then click on "Keys", the main address is in "Primary address" section. In wownero-wallet-cli, type command `address`.
You will also need something called a "Private Spend Key (https://www.getmonero.org/resources/moneropedia/spendkey.html)%22.%20This%20key%20is%20used%20to%20sign%20transactions%20(and%20now%20blocks) and should not be shared with anyone. For Wowlet, you can find this key in the "Keys" section. If you are using Wowstash, you can find the spend key by clicking on "See Secrets" button. In wownero-wallet-cli, type command `spendkey` and copy the **secret** key.
## Windows
1. Download latest windows binary: `wownero-x86_64-w64-mingw32-XXXXXX.zip` from https://git.wownero.com/wownero/wownero/releases
2. Unzip folder
3. In Windows search bar, type "cmd" and click "Command Prompt" program
4. Drag and drop unziped folder to Command Prompt window
4. Type: `wownerod.exe --start-mining YOUR-ADDRESS --spendkey SECRET-SPENDKEY`
## MacOS
1. Download latest mac binary: `wownero-x86_64-apple-darwin11-XXXXXX.tar.bz2` from https://git.wownero.com/wownero/wownero/releases
2. Double-click the tar archive file and extract to a folder
3. Open terminal window with: Control + Option + Shift + T
4. Drag and drop folder to terminal window
4. Type: `./wownerod --start-mining YOUR-ADDRESS --spendkey SECRET-SPENDKEY`
## Linux
1. Download latest linux binary: `wownero-x86_64-linux-gnu-XXXXXX.tar.bz2` from https://git.wownero.com/wownero/wownero/releases
2. Untar archive file
3. Open terminal and change directory to location of files
4. Type: `./wownerod --start-mining YOUR-ADDRESS --spendkey SECRET-SPENDKEY`
If it is your first time opening wownerod, it will take a few minutes to sync up with the network. About 15 minutes or so.
By default, you will be mining with 1 thread. If you want to increase the number of CPU threads, add `--mining-threads` and the number, so it would look something like this:
```
wownerod.exe --start-mining YOUR-ADDRESS --spendkey SECRET-SPENDKEY --mining-threads NUMBER
```
To check your hash rate, type: `status`
To stop mining, type: `stop_mining`
To exit, type: `exit`
Total noob question I've never solo mined. How do I find the main receiving address with Wowlet? I can't solo mine to the listed sub addresses since I get the error that they're not supported for solo mining. Thanks.
To get main address in Wowlet, click on "Wallet", click on "Keys", the main address is in "Primary Address". You can copy and paste it in wownerod.
Thanks a lot for the quick reply. I'm sorry this should be the last question... I'm only able to mine with one thread.... I'm trying to use the command [threads|auto] after but I've tried every format I can think of.... start_mining then the address alone just starts up one thread...
Edit: lol nevermind I'm in idiot... After the address I just had to put a number alone and that's it. I'm looking forward to solo mining after the fork in July!
(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)
(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)
I'm currently mining on a pool (Herominers) but I want to continue support this amazing project and migrate to Solo mining. I have never done solo mining before. I have 5 x PCs that range between 1000 and 2000 Hash/s.
I have the following questions:
- 1) Should I wait until after hard fork takes place on 4th July, or should I start switching over to Solo mining now and therefore no need to do anything post 4th July hard fork?
- 2) Can I use a single Wowlet address across multiple mining PCs, or must I setup a separate wallet address for each mining machine?
- 3) I like Herominers as there is a central dashboard so I can see hashrates for each miner and notice if any of my miners go offline.
Is there any such feature to be alerted if a solo miner goes offline?
How can i monitor hashrate for my solo miner?
- 4) Are there any known traps I should be aware of as I migrate my multiple machines from pool mining to solo mining?
Thanks in advance for addressing my questions.
Thank you for your support.
1. Difficulty is way too high for solo mining right now. You could start a few hours before the hard fork on 4th July.
2. Yes. You can use the same address and spend key on multiple PCs. In Wowlet, go to "Wallet" --> "Keys" and you can see the primary address and spend key there.
3. No. But you could get someone to make you a bash script that calls each mining node via RPC (https://www.getmonero.org/resources/developer-guides/daemon-rpc.html)%20(something%20like%20%20%60curl%20http://IP_ADDRESS:PORT/mining_status%20-H%20'Content-Type:%20application/json'%60) to monitor hash rates and display stats on a simple HTML webpage.
4. Be sure your miners are in a secure environment. Anyone with access to the computer could technically steal the spend key and empty out your wallet. If you want to link multiple computers together, you could checkout **xmrig-proxy](https://github.com/xmrig/xmrig-proxy)** once this [PR (https://github.com/xmrig/xmrig-proxy/pull/458) is merged.
Quote from: "wowario, post:8, topic:551"But you could get someone to make you a bash script that calls each mining node via RPC to monitor hash rates and display stats on a simple HTML webpage.
I plan on doing this for my own rigs after the HF. I'd be happy to share the source code with anyone that wants to use it.
Keep in mind, I'm not a graphic designer so it won't be *WOW* pretty but it will give the information which is most important.
I've figured out how to get solo mining running through xmrig by setting daemon to true and setting the url to my full node but for after the fork is there a place I can enter the spend key or will I have to mine directly through wonerod (I get less hash rate than xmrig).
Thanks @wowario for addressing all my questions. Much appreciated. I now have a plan for what I need to do on the 4th July to switch from pool mining to solo mining.
Hi @jrswab, I'm not a technical coder and I'm a Linux noob. I have 3 desktop miners running Ubuntu and 2 laptop miners on Windows using XMrig.
I'm very interested in what you are planning to do with your RPC script to help you monitor your rigs.
Could you please share what you build and provide me with installation instructions for Ubuntu and Windows?
Many thanks.
I'd be happy to do so! Once I get some basic functionality working I'll make a post on this forum with the details :smiley: Happy Mining!
is it possible to use another miner like xmrig instead of the built-in one to solo mine ?
yes, you can use XMRig once this PR is merged (https://github.com/xmrig/xmrig/pull/2445).
Hi @wowario, after reading this post and comments I've come to the realization that wownerod and XMrig are quite different pieces of software.
Wownerod needs to download the Blockchain, however xmrig does not. Being a noob to solo mining , is this a correct assumption?
If that's correct, I have several miners, some running Ubuntu and others Windows. Will I need to have a copy of the entire WOW Blockchain local on each mining machine?
If that's the case, can you please provide guideance on what additional software I need to install and run in Ubuntu and Windows alongside XMrig and how I configure XMrig to reference the Blockchain when mining.
Sorry if I have got things completely wrong here. I want to continue mining wow but just now sure what exactly in need to do to each miner to do so.
Thanks for your help.
Newbe question here.. Testing the wownerod command for windows .. and it is stating that the
"--spendkey" is not a valid option? no issue with the "--start-mining" option.?? Am I missing something?
you need to have the latest version (v0.10) (https://git.wownero.com/wownero/wownero/releases). Windows binaries will be out soon.
You have two options.
1. Run wownerod on each computer with the same command. You would have to sync up for each miner, but the blockchain is small, only about 3 GBs last I checked. This is the simplest option.
2. Or..... sync up 1 wownerod and point all miners to that node using XMRig proxy (https://github.com/xmrig/xmrig-proxy), which is a different piece of software. I am not a miner, so I am too familiar how to configure it, but I guess it would be something like:
`xmrig -o IP_ADDRESS:34568 --coin wownero -u YOUR_ADDRESS --spend-secret-key SPENDKEY --daemon`
(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)
I followed the instructions but Im getting a message saying that the path is not recognized as an internal or external command. Any advice would be much appreciated.
I followed these instructions as well but I get the error "unsupported non-option argument' and then it lists my spend key. If someone could provide detailed instructions I'd greatly appreciate it.
Make sure you're using the lastest version of xmrig. Mine recognizes the added argument and is versionn 6.13+
I'm using the latest 6.13.0 xmrig proxy, made sure I'm copy and pasting these exact instructions so I don't know what I'm doing wrong.
Is there perhaps somewhere I can put the spend key in the config file instead?
Are you using xmrig proxy or just xmrig on one computer? I had no issue in using xmrig to connect to wownerod on the same computer but using the same instructions with xmrig proxy to a node on another computer is not working.
@wownerian
I'm working on getting the proxy working. (It's not picking up my hashes...)
> Is there perhaps somewhere I can put the spend key in the config file instead?
In the proxy, they added a `spend-secret-key` parameter to the pool section. Its not in their documentation... I had to read the source code to figure that out 😅
For now I'll mine with one machine and when we get the xmrig proxy working I'll get my other 2 going as well (currently mining monero). When I tried to mine with a full node on all 3 computers I run into router issues (they're all gpu mining as well).
Hi! I start mining at fork....I am find some blocks
but my balance is zero!!
Address and secret key provided at daemon, proxy and miners!!!
(http://forum.wownero.com/custom_avatar/cd33f706bfcebb6563c93c2e709c51610bd699e9.png)
Where monets???
are u using an up-to-date wallet to check your balance?
I am use wowstash and cli wallet
bbalance is zero!!!
check the block hash of mined blocks in Blockchain Explorer](https://explore.wownero.com/). If nothing comes up, the chain might have been reorged and your blocks orphaned. If your blocks are in the blockchain, then try restoring a new wallet with your seed from height 0. Make sure you are using [latest wallet cli version (https://git.wownero.com/wownero/wownero/releases) and synced up with network.
blocks in blockchain!!!
but balance zero in wowstash!!!!
try using latest wallet cli version (https://git.wownero.com/wownero/wownero/releases) and synced up with network.
no....zero zero
maybe problem has xmrigproxy?
maybe, check with XMRig support
(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)
I am sure this is in here somewhere but is there a windows build? I am trying to build but having issues with Cygwin and ZMQ headers.
https://git.wownero.com/dsc/wownero-special-release-for-nioc/releases
alguem ja conseguiu mineirar ou receber algo... sera posivel executar mais de um no com a mesma carteira
I have also tried to use an xmrig proxy for all my 64 nodes. Unfortunately without success. On the Linux VM with xmrig proxy I got your wownerod miner running and left it active (only stop_mining activated on the miner) Blockchain is completely downloaded and synchronised on the machine.
On this VM I also managed to get an xmrig miner running. But unfortunately no xmrig proxy!!!
I have only entered wallet data via command line `./xmrig-proxy -o 127.0.0.1:34568 --coin wownero -u YOUR-ADDRESS --spendkey SECRET-SPENDKEY --daemon`
xmrig proxy reports the following:
```text
./xmrig-proxy: unrecognized option '--spend-secret-key'
./xmrig-proxy: unrecognized option '--daemon'
[2021-07-05 02:23:52.081] ./xmrig-proxy: unsupported non-option argument 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
* ABOUT xmrig-proxy/6.13.0 gcc/5.4.0
* LIBS libuv/1.41.0 OpenSSL/1.1.1k
* MODE nicehash
* POOL #1 127.0.0.1:34568 coin wownero
* BIND #1 0.0.0.0:3333
* BIND #2 [::]:3333
* COMMANDS hashrate, connections, verbose, workers
[2021-07-05 02:23:52.084] net 127.0.0.1:34568 read error: "end of file"
[2021-07-05 02:23:54.085] net 127.0.0.1:34568 read error: "end of file"
```
So I can't find a way to start xmrig proxy in conjunction with wownerod.
But xmrig miner is running on this machine. My problem is that I cannot give internet access to my nodes and can only run a miner via proxy.
Please think about a procedure for this, otherwise there is no possibility to mine Wownero with my system of over 1.2 MHz/s.
Thanks!
check if connections are being blocked by a firewall. open ports 34567 and 34568
find out what is the local LAN IP (https://lifehacker.com/how-to-find-your-local-and-external-ip-address-5833108) for computer running the node and enable RPC by adding this to wownerod, `--p2p-bind-ip=NODE_LAN_IP --p2p-bind-port=34567 --rpc-bind-ip=NODE_LAN_IP --rpc-bind-port=34568 --disable-rpc-ban=1 --restricted-rpc=1 --rpc-ssl=autodetect` and ping the node from other PCs within the network to check it is reachable with this call:
```
curl http://NODE_LAN_IP:34568/json_rpc -d '{"jsonrpc":"2.0","id":"0","method":"get_info"}' -H 'Content-Type: application/json'
```
if you can ping the node, try running:
```
./xmrig-proxy -o NODE_LAN_IP:34568 --coin wownero -u YOUR_ADDRESS --spend-secret-key SPENDKEY --daemon
```
I'm sorry I'm not quite understanding. So I have 3 rigs, and I need to run wownerod on one of them, and then xmrig on that one that's running the node and xmrig proxy on the other 2 I believe. I tried to run wownerod with --p2p-bind-ip=NODE_LAN_IP --p2p-bind-port=34567 --rpc-bind-ip=NODE_LAN_IP --rpc-bind-port=34568 --disable-rpc-ban=1 --restricted-rpc=1 --rpc-ssl=autodetect with filling in my local lan IP but it won't start with these settings. My router cannot handle running a node on all 3 rigs unfortunately so I'm still only able to mine with one out of 3 (only 15kh/s). Running wownerod on one computer and linking xmrig to it is pretty simple to me but once I get into getting 3 computers on running off of one node with xmrig proxy I'm really at a loss. If we could have someone make step by step instructions I'd be more than happy to pay for it with WOW it's just that I've been trying for many hours and I can't seem to figure it out.
I am not very familiar with XMRig.
Perhaps you could open a bounty on WFS (https://funding.wownero.com/proposals) for someone to write a step by step guide on using XMRig proxy on multiple computers.
I tried to follow the instructions but when I drag and drop the unzipped folder into cmd, it doesnt work for me. It says that its not recognized as an internal or external command operable program
Download wownero.exe
https://git.wownero.com/dsc/wownero-special-release-for-nioc/releases
Open CMD and change directory to location (https://www.youtube.com/watch?v=MNwErTxfkUA) where you saved wownero.exe
and then run....
```
wownerod.exe --start-mining YOUR-ADDRESS --spendkey SECRET-SPENDKEY --mining-threads NUMBER
```
I use Xmrig-Proxy Linux,you can make a config for this ? to input only wallet and spend key ? is more easy for us ,like noobs :smiley:
./xmrig-proxy -o 144.76.113.157:34568 --coin wownero -u MyWallet --spend-secret-key SECRETKEY --daemon
./xmrig-proxy: unrecognized option: spend-secret-key
./xmrig-proxy: unrecognized option: daemon
[2021-07-06 06:04:24.994] ./xmrig-proxy: unsupported non-option argument 'b25e697dc37712d4549e848a5d1d9d3d6479f4957b150e5716e619ddda1c7000'
* ABOUT xmrig-proxy/6.13.0 gcc/9.3.0
* LIBS libuv/1.41.0 OpenSSL/1.1.1k
* MODE nicehash
* POOL #1 144.76.113.157:34568 coin wownero
* BIND #1 0.0.0.0:3333
* BIND #2 [::]:3333
* COMMANDS hashrate, connections, verbose, workers
[2021-07-06 06:04:25.330] net 144.76.113.157:34568 read error: "connection reset by peer"
[2021-07-06 06:04:27.320] net 144.76.113.157:34568 read error: "connection reset by peer"
Add the spend key and the daemon option in the config file.
As far as I can tell, there is no CLI flag for the spend key in xmrig-proxy.
Example:
```json
{
"autosave": true,
"cpu": true,
"opencl": false,
"cuda": false,
"pools": [
{
"algo": "rx/wow",
"url": "127.0.0.1:34568",
"spend-secret-key": "some-key",
"user": "Wo...",
"daemon": true
}
]
}
```
I've tried this and it still doesn't work. Unfortunately I think until we have a step by step guide on how to get the proxy working a lot of people won't be able to mine with multiple computers unless they run a full node on each one of them. I can't do this personally because I run into router issues.
I'm working on getting xmrig-proxy to see the hashes I'm sending it. Once I get that solved I'll be making a guide and posting it here.
(unless someone beats me to it lol)
thanks,and i have another question,where i see the block ,where i mine ? is a pool ?
2021-07-06 14:45:57.309] * upstreams active: 1 sleep: 0 error: 0 total: 1
[2021-07-06 14:45:57.310] * miners active: 51 max: 51 ratio: 1:51.0
[2021-07-06 14:45:58.724] proxy speed (1m) 0.00, (10m) 0.00, (1h) 0.00, (12h) 0.00, (24h) 0.00 kH/s
It will likely show in `wownerod` but I'm not 100% sure if you'll see it elsewhere just yet.
[2021-07-06 14:55:00.292] * upstreams active: 1 sleep: 0 error: 0 total: 1
[2021-07-06 14:55:00.292] * miners active: 51 max: 51 ratio: 1:51.0
[2021-07-06 14:55:03.138] proxy speed (1m) 0.00, (10m) 0.00, (1h) 0.00, (12h) 0.00, (24h) 0.00 kH/s
[2021-07-06 14:55:11.604] proxy 0.00 kH/s, shares: 0/1 +0, upstreams: 1, miners: 51 (max 51) +1/-1
and on miners, i have this
[2021-07-06 14:58:02.499] miner speed 10s/60s/15m 17170.8 17169.9 n/a H/s max 17386.1 H/s
I have the same thing going on...
xmrig-proxy shows no cumulative hashrate but the miners are getting jobs and showing their hashrate.
I'm still trying to figure out why and if it's something that can be fixed outside of the source code.
i understand,and where i see if i have a block,how she pay me ,where i see how much wow she give me ? i mine on darknes ? :))
is corectly if shom me shares 0/1 ?
[2021-07-06 15:06:11.801] proxy 0.00 kH/s, shares: 0/1 +0, upstreams: 1, miners: 51 (max 51) +0/-0
[2021-07-06 15:06:38.148] net 0000 new job from 144.76.113.157:34568 diff 11716466451 algo rx/wow height 332620
[2021-07-06 15:07:11.814] proxy 0.00 kH/s, shares: 0/1 +0, upstreams: 1, miners: 51 (max 51) +3/-3
[2021-07-06 15:07:32.739] proxy speed (1m) 0.00, (10m) 0.00, (1h) 0.00, (12h) 0.00, (24h) 0.00 kH/s
[2021-07-06 15:08:11.831] proxy 0.00 kH/s, shares: 0/1 +0, upstreams: 1, miners: 51 (max 51) +0/-0
[2021-07-06 15:09:11.849] proxy 0.00 kH/s, shares: 0/1 +0, upstreams: 1, miners: 51 (max 51) +0/-0
[2021-07-06 15:09:17.071] net 0000 new job from 144.76.113.157:34568 diff 11727306608 algo rx/wow height 332621
[2021-07-06 15:10:11.865] proxy 0.00 kH/s, shares: 0/1 +0, upstreams: 1, miners: 51 (max 51) +0/-0
[2021-07-06 15:10:21.119] net 0000 new job from 144.76.113.157:34568 diff 11668607772 algo rx/wow height 332622
> where i see if i have a block
When mining with `wownerod` alone, it shows up in the output.
> how she pay me
The funds are sent to the wallet address used in `xmrig-proxy`
> where i see how much wow she give me
It's a set amount. I don't remember how many coins are awarded though.
sorry for all what i ask...bu ti need to know....where i see when she got me one block ?
JRSWAB...why don`t get me block....i have Sum WOW from matched outputs (i.e., incoming WOW): 0.000000000000...i have 1,2 MH/s...and i have some hours.
[2021-07-06 17:39:58.801] proxy 0.00 kH/s, shares: 0/0 +0, upstreams: 1, miners: 57 (max 57) +1/-1
[2021-07-06 17:40:18.486] * upstreams active: 1 sleep: 0 error: 0 total: 1
[2021-07-06 17:40:18.486] * miners active: 57 max: 57 ratio: 1:57.0
Failed to parse arguments: unrecognised option '--spendkey'
why
pls help
It is `--` (2 dashes) not `–`
Ok i go try it
I let know how it work
Is there something similar to the huge pages option? I seem to only be getting the non huge pages hash rate
xmrig proxy + wownero = mining in darkness :rofl:
no hashrate, no block found notification, nothing
+1111
the same here, did it arrive?
i still can not connect to node to start mining
miner show error when connecting
miner says ''connection refuse''
check if ports are being blocked by firewall
update to latest version of xmrig
make sure you have the correct flags like this:
```
xmrig -o IP_ADDRESS:34568 --coin wownero -u YOUR_ADDRESS --spend-secret-key SPENDKEY --daemon
```
Hello everyone. Does anyone know why when I run the solo miner file (wowneros.exe) on my windows box an error pops up. It says I do not have enough permission to open the file. I've looked at all settings and I do have the correct permissions. Any guidance would be greatly appreciated.
When I start wownerod in the command prompt I'm getting Error opening database: Failed to open lmdb environment: Input/output error. How can I fix this?
[2021-07-11 07:39:25.755] net dev donate started
[2021-07-11 07:39:25.755] net new job from donate.ssl.xmrig.com:443 diff 76399G algo rx/wow height 333831
[2021-07-11 07:40:25.755] net dev donate finished
[2021-07-11 07:40:25.755] net new job from 10.100.135.5:8080 diff 13195M algo rx/wow height 333857
[2021-07-11 07:40:51.112] net new job from 10.100.135.5:8080 diff 13195M algo rx/wow height 333857
[2021-07-11 07:41:54.806] net new job from 10.100.135.5:8080 diff 13195M algo rx/wow height 333857
[2021-07-11 07:42:42.909] net new job from 10.100.135.5:8080 diff 13152M algo rx/wow height 333858
[2021-07-11 07:43:44.449] miner speed 10s/60s/15m 17056.3 17043.0 17047.3 H/s max 17284.6 H/s
Woohoo! I'm so excited, I just won my 1st block reward using Wownerod via solo mining.
It took nearly 3 weeks (btw I had to reboot my PC several times in between).
Patience is key Wownero miners, the rewards will come.
For those curious to see what is rendered when you win a block, see below...
(http://forum.wownero.com/custom_avatar/2bd910477261dcf81c985b48ab4df0575b8bbff0.png)
Special shout out to @wowario - I wouldn't be able to get my solo miner running without this post.
Hello y'all if you are still having problems setting up a miner and a wownerod node up then i have this video that will possibly help you https://forum.wownero.com/t/how-to-solo-mine-wownero-on-windows-10-and-hive-os-video-tutorial/824?u=mesmersie i only covered windows and hive os. Hope it helps!
I'm not sure if this is helpful, but here is what i used on xmrig (none proxy) 6.14
./xmrig 0 -o 192.168.1.38:34568 --coin wownero -u xxxxxxx --spend-secret-key xxxxxx --daemon -t 4
Below is my output. Currently mining from my macpro to my node in my vm farm. I know that 0 didn't do anything, but without it for some reason it fails to work. I have five more miners to put online. when i do, I'll report back how they're working.
[2021-08-12 08:59:39.916] ./xmrig: unsupported non-option argument '0'
***** **ABOUT** **XMRig/6.14.0** **clang/10.0.0**
***** **LIBS libuv/1.41.0 OpenSSL/1.1.1k hwloc/2.4.1**
***** **HUGE PAGES** **supported**
***** **1GB PAGES** **unavailable**
***** **CPU Intel(R) Xeon(R) CPU X5670 @ 2.93GHz (2)** **64-bit** **AES**
L2:**3.0 MB** L3:**24.0 MB** **12**C/**24**T NUMA:**1**
***** **MEMORY** **45.9/48.0** GB (96%)
DIMM 1: **4** GB **DDR3 @ 1066 MHz** 0x4D33393342353137304742302D5948392020
DIMM 2: **4** GB **DDR3 @ 1066 MHz** 0x202020202020202020202020202020202020
DIMM 3: **16** GB **DDR3 @ 1066 MHz** 0x484D543432475237424D5234432D47372020
DIMM 4:
DIMM 5: **4** GB **DDR3 @ 1066 MHz** 0x4D33393342353137304648302D4348392020
DIMM 6: **4** GB **DDR3 @ 1066 MHz** 0x4D33393342353137304648302D4348392020
DIMM 7: **16** GB **DDR3 @ 1066 MHz** 0x484D543432475237424D5234432D47372020
DIMM 8:
***** **MOTHERBOARD Apple Inc.** - **Mac-F221BEC8**
***** **DONATE 1%**
***** **ASSEMBLY auto:****intel**
***** **POOL #1** **192.168.1.38:34568** coin **wownero**
***** **COMMANDS** **h****ashrate,** **p****ause,** **r****esume, re****s****ults,** **c****onnection**
***** **OPENCL** **disabled**
***** **CUDA** **disabled**
[2021-08-12 08:59:39.929] **net** **use daemon** **192.168.1.38:34568** 192.168.1.38
[2021-08-12 08:59:39.929] **net** **new job** from **192.168.1.38:34568** diff **23490M** algo **rx/wow** height **343320** (2 tx)
[2021-08-12 08:59:39.929] **cpu** use **argon2** implementation **SSSE3**
[2021-08-12 08:59:39.929] **randomx** **init dataset** algo **rx/wow (****24** **threads)** seed c7b8adcca301bdbe...
[2021-08-12 08:59:43.362] **randomx** **allocated** **2336 MB** (2080+256) huge pages **0% 0/1168** **+JIT** (3433 ms)
[2021-08-12 08:59:47.009] **randomx** **dataset ready** (3647 ms)
[2021-08-12 08:59:47.010] **cpu** use profile ***** **(****4** **threads)** scratchpad **1024 KB**
[2021-08-12 08:59:53.349] **cpu** **READY** threads **4/4 (4)** huge pages **50% 2/4** memory **4096 KB** (6340 ms)
[2021-08-12 09:00:51.055] **miner** **speed** 10s/60s/15m **1306.8** n/a n/a **H/s** max **1336.8 H/s**
Noob here, running Wowlet on Mac Os and just synced the miner via terminal.
I'm not the most terminal savvy kind of person so I did my best to copy and paste the code with my addresses but I'm getting unknown command error for both --startmining and --spendkey.
Did I place my addresses in right piece of the command?
I'm grabbing the "primary address" and the "secret spend key" from WOWlet -> keys
I'm inputting it like this:
./wownerod --start-mining **my primary address entered here** --spendkey **my secret spend key entered here**
Am I doing something wrong?
See the pic, not sure if matters but I blacked out the keys, I figured one was a secret I should protect it.
Please offer some wisdom
(http://forum.wownero.com/custom_avatar/8a40960110054edfc772aa75efa5e3c4b502d8f8.png)
You're typing into the `wownerod` console, which recognises a different set of commands. Exit `wownerod` first with Ctrl-C, then at the `$` prompt, type in your command again.
Also, it's not really visible in the pic, but double check that your command is all one long line.
Thanks for the tips,
it's still not working, I've tried exiting Wownerod and entering the commands via terminal only and not getting anywhere. Command line is all one line, I copy and past the whole thing just as this tutorial above has it, I've only put in my key and addressed is the only difference.
Any ideas? I swear anytime I have to input commands into anything like this It hardly ever works. I feel like command line terminals are for the gifted.
Pleas help(http://forum.wownero.com/custom_avatar/d3670fa185205d0c64c0d574503408e1976352d5.png)
you first need to `cd` (change directory) to location where you saved the files.
and then enter `./wownerod --start-mining YOUR-ADDRESS --spendkey SECRET-SPENDKEY`
Thanks for the tip! I'm getting closer but still not quite there.
I am supposed to be changing directory and entering ./wownerod --start-mining YOUR-ADDRESS --spendkey SECRET-SPENDKEY in the MAC OS terminal and not the Wownerod terminal correct?
I tried to change directory in wownerod and didn't get anywhere. The OS terminal however did give me some form of progress despite the errors. Please see image.
Thanks for the help!(http://forum.wownero.com/custom_avatar/51533190110265a17e787ae106f9435d98611657.png)
(http://forum.wownero.com/custom_avatar/0919167df80c733157a1732048e0cf40f2cb25a6.png)
you get this when you already have an instance of wownerod running
you got it running, type `status` to check if you are mining
I have tried following the instructions, downloaded the files, installed, in Linux.
At the CLI I entered ./wownerod --start-mining Woxxxxx --spendkey xxxxxxxxx
I get messages like:
Sync data returned a new top block candidate: 5301 -> 348999 [Your node is 343698 blocks (3.3 years) behind]
SYNCHRONIZATION started
At the moment it is going no further than this, but earlier it got further with other messages such as some IP addresses followed by the word blocked, and messages about not being connected to the network.
So how do I get started?
download latest version
https://git.wownero.com/wownero/wownero/releases
make sure you have written down your wallet's seed and have it saved somewhere safe.
delete .wownero folder
run `./wownerod`
once you are fully synced, exit and run `./wownerod` again with --start-mining Woxxxxx --spendkey xxxxxxxxx
I'm not making any progress.
I downloaded latest version v0.10.1.0, extracted all contents to desktop and deleted the folder
Synchronized wownerod,
Opened a new terminal window, changed directory to Desktop and entered --start-mining Woxxxxx --spendkey xxxxxxxxx
Received the following errors:
|2021-09-02 03:54:01.851|F Error starting server: Failed to bind IPv4 (set to required)
|2021-09-02 03:54:01.851|I Deinitializing core...
|2021-09-02 03:54:01.856|I Stopping cryptonote protocol...
|2021-09-02 03:54:01.856|I Cryptonote protocol stopped successfully
|2021-09-02 03:54:01.856|E Exception in main! Failed to initialize p2p server.
I type status in wownerod terminal and get this:
Height: 349357/349357 (100.0%) on mainnet, **not mining**, net hash 119.23 MH/s, v19, 12(out)+0(in) connections, uptime 0d 0h 4m 49s
So I'm still not mining.
I guess the complication of this stuff is why I sold my ASIC miners in 2015, if I only could have figured that out then and not given up I'd have waaaaay more BTC.
I did notice a message in wownerod after syncing:
You are now synchronized with the network. You may now start wownero-wallet-cli.
tried running wownero-wallet-cli, moved my wallet file to desktop and entered the wallet name with no luck. Should I be attempting to run this wownero-wallet-cli or is the "--start-mining Woxxxxx --spendkey xxxxxxxxx" the optimal way to go?
Anyway please help, I would really like to understand how to cpu/gpu mine all sorts of coins. Getting this to work is a first step.
If I can succeed in getting this to run it'll give me some confidence.
Thank you
Peep the screenshot:
(http://forum.wownero.com/custom_avatar/73a8a68b98717451f794cb5d3a8a37aa2132a0ef.png)
you are almost there.
you should only run **one instance** of wownerod, not two.
type `exit` and restart it like this `./wownerod --start-mining Woxxxxx --spendkey xxxxxxxxx`
My dude thank you! I think understand now.
Mining Started!
(http://forum.wownero.com/custom_avatar/8fdd38366519fcfdfd514a721983d3dc0203a2e0.png)
congratulations, you are a solo miner. remember rewards are random and there is no guarantee when you would win a block. It could take a few days or a month or two.
Thanks! I did read that.
What else can be mined?
Did I read somewhere mining xmr is more lucrative?
is there similar simple route for that?
What else do you folks cpu/gpu mine that is profitable?
A post was split to a new topic: [Failed to find tx meta](/t/failed-to-find-tx-meta/914)
Quote from: "ruzindla, post:91, topic:551"Did I read somewhere mining xmr is more lucrative?
It depends on the price and network difficulty of Monero and Wownero at the time you're mining.
Usually, Wownero is more profitable (more $ per hash) and also you can get a slightly faster hashrate with Wownero's tweaked PoW.
Great guide
took a bit of to and fro but got wownerod running, got synced and finally got mining
protips [windwows x64]:
* make sure you don't have a . at the start of your commands that's for mac 'nd linux users only!
* you can copy and paste in cmd by right clicking on the top bar and selecting 'edit'.
* to start mining; make sure you exit wownerod by typing 'exit' > then use the command 'cd' to navigate to the wownerod folder on your pc [eg/ 'cd Documents' 'cd Wownero' etc.] then you can enter the command and it should spin the wheel
* using all threads available is max chances for profit but might affect pc performance, I keep one thread spare for ... other purposes so I can mine in the background.
* when mining use 'status' to check yoru mining stats, you can also set it to 'show hr' [show hashrate] to get a constant ticker of your hashrate and to see your pc's heartbeat.
* if it fails: triple check your syntax and comb through the instructions with a fine tooth comb
* be careful with your secret spend key - try and keep it off clipboard and any documents local or online.
that's the juice!
h00t
Quote from: "wowario, post:90, topic:551, full:true"congratulations, you are a solo miner. remember rewards are random and there is no guarantee when you would win a block. It could take a few days or a month or two.
Question: Does having a more powerful CPU improve your chances of winning?
Or as you said above "rewards are random" hence CPU power (hashrate) does not increase your odds of winning, is that the case?
Yes. Your chances are proportional to your CPU's hashrate over the network difficulty. However, exactly *when* you get your reward is random.
Consider it like a loterry where your hashrate is how many tickets you have. The total of everyone's hashrate is the total number of tickets. The lottery is spun every block time (5 minutes on average) to see who wins the block.
However, this is only a rough analogy. In the real mining algorithm, the lottery is continuously spun and there is a chance that no one will win, so there will be times when a block is won sooner or later than average. The chances (i.e., network difficulty) are dynamically adjusted to target that average 5 minutes per win.
This is what is meant by the rewards being random, but in the long run it all averages out.
Do note however that in the long run, the total network hashrate fluctuates too as miners join and leave the network, and with most coins there is a consistent upwards trend which you should factor into your ROI calculations if you're interested in mining.
Quote from: "orklemerkle, post:96, topic:551"Your chances are proportional to your CPU's hashrate over the network difficulty.
Thanks for the excellent answer. Here is a follow-up question...
Let's say there are 3 different miners with equal hash rate but differing configurations as follows:
* **Miner A: 5 x 1,000 Hash/sec** (5 x PCs that are solo mining individually not via XMrig Proxy)
* **Miner B: 1 x 5,000 Hash/sec** (a single PC that is solo mining)
* **Miner C: 2 x 2,500 Hash/sec** (2 x PCs mining via XMrig Proxy, hence I presume hashrate is combined)
Do any of these setups have an advantage over the other?
Miner A's five machines are completely independent, so there is no single point of failure. However, you might run into trouble if one machine or another falls out of sync with the blockchain, for example due to network issues or software/hardware problems. Also, you incur five PCs' worth of overhead in power, cost, and management.
Miner B could be the most power-efficient, but if that one PC has a problem for whatever reason (software errors, another program eating up the CPU, or reboot for update), you entire hashrate drops.
Miner C has the advantage of not going down completely if one PC drops out. However, you still have a single point of failure in the proxy and wownero daemon, unless you run two of those and cross-link them.
In this case I'd set up a third high-reliability machine to run the proxy and daemon, while the miners can run optimised for hashrate per watt (overclocking, undervolting, less cooling, etc.). The miners will need a reliable, low-latency connection to the proxy in order to avoid stale shares, although in practice they won't show up until you go transcontinental or something.
**TL;DR:** Each have advantages and disadvantages in terms of efficiency and reliability, though personally I'd avoid setup A.
Quote from: "orklemerkle, post:98, topic:551"In this case I'd set up a third high-reliability machine to run the proxy and daemon, while the miners can run optimised for hashrate per watt (overclocking, undervolting, less cooling, etc.)
Thanks heap @orklemerkle. the above is excellent advise and I will plan on doing this.
Would you recommend my backup proxy & daemon be built using this nice script by @qvqc -
https://forum.wownero.com/t/quick-start-wownerod-for-solo-miners-alliance-network/836 , or does this add a level of risk, I'd appreciate your thoughts?
You're welcome!
The script looks good, but it also makes your node public and exposes it via Tor and I2P. If this is for your backup node running behind the same IP as another node, that's rather inefficient at best. But if it's at a different location, go for it. We can always use more nodes.
I guess it's possible use the script and then manually close the ports, disable Tor and I2P, etc., but as I don't use the script myself I can't help much with that.
you can disable extra wownerod after running the script
* pick one machine to run wownerod and xmrig proxy
* on other machines run `systemctl stop wownerod` and `systemctl disable wownerod`
* follow the guide by @jrswab , How To Mine Wownero With Xmrig Proxy (https://forum.wownero.com/t/how-to-mine-wownero-with-xmrig-proxy/672)
* **Bonus:** add service files for xmrig and xmrig-proxy so they autostart on reboot
if you find some issue, lmk :)
Every three mining devices a proxy and a node, efficiency, scalability, redundancy.
In the miner side using config.json you can make it ready to switch the proxy in case of failure.
"pools": [
{
"algo": "rx/wow",
"coin": null,
"url": "IP_PROXY_A",
"user": "WALLET",
"spend-secret-key": "EXPEND_SECRET_KEY",
"pass": null,
"rig-id": "MINER_ID",
},
{
"algo": "rx/wow",
"coin": null,
"url": "IP_PROXY_B",
"user": "WALLET",
"spend-secret-key": "EXPEND_SECRET_KEY",
"pass": null,
"rig-id": "MINER_ID",
},
{
"algo": "rx/wow",
"coin": null,
"url": "IP_PROXY_C",
"user": "WALLET",
"spend-secret-key": "EXPEND_SECRET_KEY",
"pass": null,
"rig-id": "MINER_ID",
}
],
Yup, this is a good way of switching proxies automatically in case of failure.
Remember that you don't need to put your spend key in the miner config when you're mining to a proxy, though. You only need that if you mine directly to a daemon.
i see when 2 min after tx send,wownerod report this in red:03.22.22.015 E failed to find tx meta <8b5e53....whats that mean?
That message seems to be mostly harmless (https://forum.wownero.com/t/failed-to-find-tx-meta/914/2).
I have error at wallet
Known ring does not include the spent output: xxxx
version of wallet and daemon is last
how i can send transaction???
Hey all,
i've been at the mining game full on for about 6 months, I'm still learning and have even more to learn!
I've set up a monster WinX laptop with pathetic nvidea card, 2015 Macbok, 2020 M1 Macbook Air, and put a 32bit 1Gb netbook to good use a few months back as my xmrig-proxy, which has actually allowed me to block my mining specific devices at the router as their mining traffic is sent to the proxy.
But now I'm well out of my league and I'm hoping the community can help out as I can get everyone on the wownero train here and maybe find a block! Currently, the M1 is running the wownerod which is working fine and it can use xmrig to mine on itself. But that's as far as I can go. Nothing can mine against the M1, "connection is refused". I've gone so far as turning the firewall off completely and still no luck, yet I can ping it no problem.
I'm thinking it's not an Apple M1 firewall thing (as wownerod has been added and allowed) but more of a wownero configuration issue. I'm somewhat savvy with the xmrig setup so I naturally went configuration file route when setting up the wownero daemon. But it seems I have the "ultra black ops" Tor enabled configuration and it may be too restrictive for even local network mining. I'll put that config at the bottom is someone wants to take a quick look.
I then shifted to the 'bare bones' approach since most mining walk-throughs basically 1)download wownero and 2) run ./wownerod --spend-key ...... So I tried just firing it up with the --log-file /Volumes/MINIX/Chains/WOW/wownero.log --data-dir /path/to/external/ssd with still the same "connection refused".
Finally, I thought I may need to be less restrictive on my firewall (less restrictive than off!?!) so I dug around the Sharing but that's for access to my files, or remote control it. I just want to connect the xmrig-proxy to it and get everyone going.
So I think it's just the config of wownerod is not accepting external connections or isn't listen on ports. I just tried --add-peer IP.of.Peer.2add. with no luck. Any tips of commands I should be using? Seems like you can set --allow-local or --add-peer at start/run time but not while it's running?
Anyways, I'll leave it here as I suspect it's a total n00b issue and most everyone knows what's up. Please share! Thanks.
osf
```
#anonymous-inbound=YOUR_ONION_ADDRESS:34566,127.0.0.1:34566,64
check-updates=disabled
log-level=0
no-igd=1
no-zmq=1
restricted-rpc=1
p2p-bind-ip=0.0.0.0
p2p-bind-port=34567
public-node=1
confirm-external-bind=1
rpc-bind-ip=0.0.0.0
rpc-bind-port=34568
rpc-ssl=autodetect
disable-rpc-ban=1
db-sync-mode=safe
out-peers=64
in-peers=64
limit-rate-up=1048576
limit-rate-down=1048576
tx-proxy=tor,127.0.0.1:9050,23
add-priority-node=v2admi6gbeprxnk6i2oscizhgy4v5ixu6iezkhj5udiwbfjjs2w7dnid.onion:34568
add-priority-node=iy6ry6uudpzvbd72zsipepukp6nsazjdu72n52vg3isfnxqn342flzad.onion:34568
add-priority-node=7ftpbpp6rbgqi5kjmhyin46essnh3eqb3m3rhfi7r2fr33iwkeuer3yd.onion:34568
add-priority-node=j7rf2jcccizcp47y5moehguyuqdpg4lusk642sw4nayuruitqaqbc7ad.onion:34568
add-priority-node=aje53o5z5twne5q2ljw44zkahhsuhjtwaxuburxddbf7n4pfsj4rj6qd.onion:34568
add-priority-node=nepc4lxndsooj2akn7ofrj3ooqc25242obchcag6tw3f2mxrms2uuvyd.onion:34568
add-priority-node=666l2ajxqjgj5lskvbokvworjysgvqag4oitokjuy7wz6juisul4jqad.onion:34568
add-priority-node=ty7ppqozzodz75audgvkprekiiqsovbyrkfdjwadrkbe3etyzloatxad.onion:34568
```
That is indeed odd. You've already set `confirm-external-bind`, `restricted-rpc`, and `rpc-bind-ip`. Can you show your log file as `wownerod` starts up? I'm specifically interested in any log lines around `Initializing core RPC server`.
You might also want to try setting `rpc-bind-ip` to your actual LAN IP address and see if that helps.
Awesome. I'll have that out right away. Thanks! I really just dumped that conf in there, knowing enough that I didn't feel it was dangerous. Anyways, brb.
Sorry for the delay, I had wandered down the "put the proxy on the daemon" path even though that won't be my end setup. Got 1 device connected to proxy plus itself. Doesn't give a lot of feedback does it?
Anyways, started a fresh log.
|2021-10-29 02:08:30.502| 0x201d7fe00|INFO|logging|contrib/epee/src/mlog.cpp:273|New log categories: *:WARNING,net:FATAL,net.http:FATAL,net.ssl:FATAL,net.p2p:FATAL,net.cn:FATAL,daemon.rpc:FATAL,global:INFO,verify:FATAL,serialization:FATAL,daemon.rpc.payment:ERROR,stacktrace:INFO,logging:INFO,msgwriter:INFO|
|---|---|---|---|---|---|
|2021-10-29 02:08:30.503| 0x201d7fe00|INFO|global|src/daemon/main.cpp:294|Wownero 'Junkie Jeff' (v0.10.1.0-release)|
|2021-10-29 02:08:30.503| 0x201d7fe00|INFO|global|src/daemon/protocol.h:53|Initializing cryptonote protocol...|
|2021-10-29 02:08:30.503| 0x201d7fe00|INFO|global|src/daemon/protocol.h:58|Cryptonote protocol initialized OK|
|2021-10-29 02:08:30.505| 0x201d7fe00|INFO|global|src/daemon/core.h:63|Initializing core...|
|2021-10-29 02:08:30.505| 0x201d7fe00|INFO|global|src/cryptonote_core/cryptonote_core.cpp:515|Loading blockchain from folder /Volumes/MINIX/Chains/WOW/lmdb ...|
|2021-10-29 02:08:30.673| 0x201d7fe00|INFO|global|src/cryptonote_core/cryptonote_core.cpp:690|Loading checkpoints|
|2021-10-29 02:08:30.673| 0x201d7fe00|INFO|global|src/daemon/core.h:73|Core initialized OK|
|2021-10-29 02:08:30.674| 0x201d7fe00|INFO|global|src/daemon/p2p.h:63|Initializing p2p server...|
|2021-10-29 02:08:30.685| 0x201d7fe00|INFO|global|src/daemon/p2p.h:68|p2p server initialized OK|
|2021-10-29 02:08:30.685| 0x201d7fe00|INFO|global|src/daemon/rpc.h:63|Initializing core RPC server...|
|2021-10-29 02:08:30.686| 0x201d7fe00|INFO|global|contrib/epee/include/net/http_server_impl_base.h:79|Binding on 127.0.0.1 (IPv4):34568|
|2021-10-29 02:08:35.749| 0x201d7fe00|INFO|global|src/daemon/rpc.h:69|core RPC server initialized OK on port: 34568|
|2021-10-29 02:08:35.751| 0x201d7fe00|INFO|global|src/daemon/rpc.h:74|Starting core RPC server...|
|2021-10-29 02:08:35.751|[SRV_MAIN]|INFO|global|src/daemon/rpc.h:79|core RPC server started ok|
|2021-10-29 02:08:35.753|[SRV_MAIN]|INFO|global|src/daemon/p2p.h:78|Starting p2p net loop...|
|2021-10-29 02:08:36.761|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1795||
|2021-10-29 02:08:36.761|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1795||
|2021-10-29 02:08:36.761|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1795||
|2021-10-29 02:08:36.761|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1795| ██╗██╗ ██╗███╗ ██╗██╗ ██╗██╗███████╗ |
|2021-10-29 02:08:36.761|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1795| ██║██║ ██║████╗ ██║██║ ██╔╝██║██╔════╝ |
|2021-10-29 02:08:36.761|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1795| ██║██║ ██║██╔██╗ ██║█████╔╝ ██║█████╗ |
|2021-10-29 02:08:36.761|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1795| ██ ██║██║ ██║██║╚██╗██║██╔═██╗ ██║██╔══╝ |
|2021-10-29 02:08:36.761|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1795| ╚█████╔╝╚██████╔╝██║ ╚████║██║ ██╗██║███████╗ |
|2021-10-29 02:08:36.761|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1795| ╚════╝ ╚═════╝ ╚═╝ ╚═══╝╚═╝ ╚═╝╚═╝╚══════╝ |
|2021-10-29 02:08:36.764|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823||
|2021-10-29 02:08:36.765|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| @@@@&///////////////@ |
|2021-10-29 02:08:36.765|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| @@@@@@@@@@@@@@@@*/////////////////////#@ |
|2021-10-29 02:08:36.765|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| @#////////(&@@@@//////////////////////////////////@ |
|2021-10-29 02:08:36.765|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| @&////////////////////////////#@@@@@@@ *////////@ |
|2021-10-29 02:08:36.765|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| @%///////////////////////////&@@@@@@/ /////&@ |
|2021-10-29 02:08:36.765|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| @@//////////////////////////%@@@@@@ */////@ |
|2021-10-29 02:08:36.765|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| @@#//////////////#@@@@@@@@@@@@@@@& ,///////////* /////#@ |
|2021-10-29 02:08:36.765|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| @///////////*@@@@@@@@@@@@@ .////////////@@@#//////&@ |
|2021-10-29 02:08:36.766|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| @(///////////%@@@@/,%&&/ ,//////. */////////(@@@%///#@ |
|2021-10-29 02:08:36.766|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| @%//////////// *//////////////////////////// //////////@@@@///& |
|2021-10-29 02:08:36.766|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|@%//////////. *///////////////S/v/n/g/V/f/G/u/r/C/b/b/e//////@@@@/// |
|2021-10-29 02:08:36.766|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| @////////////*.///////%/////////////Z/n/a/f/Z/b/a/r/l/////////@@@(// |
|2021-10-29 02:08:36.766|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| @@@#////////////..///@@@(///////////////////////////////////@@@/// |
|2021-10-29 02:08:36.766|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| @@#//////////. //&@@(//////////////////////////((((*////(//// |
|2021-10-29 02:08:36.766|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| &//////// ///@@%////////////////////(((((((((,*///////// |
|2021-10-29 02:08:36.766|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| //&@@///////////((((%%%%(/////%%%%(,*//////// |
|2021-10-29 02:08:36.766|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| .//@@@/////////*(((///%%//%//%%/////*///////# |
|2021-10-29 02:08:36.771|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| //(@@@@////////**////(%%%%%%%%%//////**////// |
|2021-10-29 02:08:36.771|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| ////////////////,/////%%%//%%////////#*//// |
|2021-10-29 02:08:36.771|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| .////////////////*///////////////..,**///// |
|2021-10-29 02:08:36.771|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| ,////////////////*/////#...,***////////// |
|2021-10-29 02:08:36.771|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| &////////////////*,,**///////////////// |
|2021-10-29 02:08:36.771|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| #/////////////////////////////////// |
|2021-10-29 02:08:36.771|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| %/////////////////////////////// |
|2021-10-29 02:08:36.771|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| ////////////////////////// |
|2021-10-29 02:08:36.771|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823| //////////////// |
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1831||
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1831| ██╗███████╗███████╗███████╗ |
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1831| ██║██╔════╝██╔════╝██╔════╝ |
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1831| ██║█████╗ █████╗ █████╗ |
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1831| ██ ██║██╔══╝ ██╔══╝ ██╔══╝ |
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1831| ╚█████╔╝███████╗██║ ██║ |
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1831| ╚════╝ ╚══════╝╚═╝ ╚═╝ |
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1831||
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1831||
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1831||
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843||
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843|**********************************************************************|
|2021-10-29 02:08:36.776|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843|The daemon will start synchronizing with the network. This may take a long time to complete.|
|2021-10-29 02:08:36.776|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843||
|2021-10-29 02:08:36.777|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843|Caution: Wownero is highly experimental software compiled by a ragtag team of stoners with as much|
|2021-10-29 02:08:36.777|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843|skill as Verge developers. Storing your life savings in WOW is probably not a good idea.|
|2021-10-29 02:08:36.777|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843||
|2021-10-29 02:08:36.777|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843|You can set the level of process detailization through set_log command,|
|2021-10-29 02:08:36.777|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843|where is between 0 (no details) and 4 (very verbose), or custom category based levels (eg, *:WARNING).|
|2021-10-29 02:08:36.777|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843||
|2021-10-29 02:08:36.777|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843|Use the help command to see the list of available commands.|
|2021-10-29 02:08:36.777|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843|Use help to see a command's documentation.|
|2021-10-29 02:08:36.777|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843|**********************************************************************|
|2021-10-29 02:08:37.326|[P2P3]|INFO|global|src/cryptonote_protocol/cryptonote_protocol_handler.inl:2478||
|2021-10-29 02:08:37.327|[P2P3]|INFO|global|src/cryptonote_protocol/cryptonote_protocol_handler.inl:2478|**********************************************************************|
|2021-10-29 02:08:37.327|[P2P3]|INFO|global|src/cryptonote_protocol/cryptonote_protocol_handler.inl:2478|You are now synchronized with the network. You may now start wownero-wallet-cli.|
|2021-10-29 02:08:37.327|[P2P3]|INFO|global|src/cryptonote_protocol/cryptonote_protocol_handler.inl:2478||
|2021-10-29 02:08:37.327|[P2P3]|INFO|global|src/cryptonote_protocol/cryptonote_protocol_handler.inl:2478|Use the help command to see the list of available commands.|
|2021-10-29 02:08:37.327|[P2P3]|INFO|global|src/cryptonote_protocol/cryptonote_protocol_handler.inl:2478|**********************************************************************|
This may be a dumb question(s) but is it an accurate statement to say that:
* only the device hosting the bc and daemon can actually mine directly against it
* only that device can run xmrig-proxy against it
* and only then can other devices on the local network (or elsewhere) can connect to the proxy?
Maybe I'm trying to do something not doable. Again, M1 is currently running it, but the Chain, Daemon, and wallet is on a M2 SSD portable enclosure, hoping to delegate my old Macbook to that task as it's not a good miner. Win7Starter netbook is my proxy that I'd like to connect to the daemon, then have my 2 good ones have the most resources to grind away and see if I can't land a block within the 20 days it says it will take me.
Quote from: "onesmartfellow, post:110, topic:551"Awesome. I'll have that out right away. Thanks! I really just dumped that conf in there, knowing enough that I didn't feel it was dangerous.
Whoops, sorry, I think I worded that wrong. I meant that your config was already fine. (But you can leave out `public-node=1`.)
Your log looks as if if you'd erased the `rpc-bind-ip`, `restricted-rpc`, and `confirm-external-bind` lines. According to the
Monero docs. Could you please try to put the three lines back again, and then post *both* the config and relevant log here?
Awesome formatting on the log, btw.
---
Quote from: "onesmartfellow, post:111, topic:551"This may be a dumb question(s)
There are no dumb questions :stuck_out_tongue:
Quote from: "onesmartfellow, post:111, topic:551"but is it an accurate statement to say that:
* only the device hosting the bc and daemon can actually mine directly against it
* only that device can run xmrig-proxy against it
These two are only true if your daemon's RPC port is bound to 127.0.0.1 or localhost. If it's bound to 0.0.0.0 (which means all network interfaces) or a specific interface's address, then other devices on the connected network should be able to mine (or run a proxy) against the daemon.
Quote from: "onesmartfellow, post:111, topic:551"* and only then can other devices on the local network (or elsewhere) can connect to the proxy?
This is indeed the default on `xmrig-proxy`. You can play with forwarding or routing settings to access the proxy from elsewhere, but that doesn't sound like what you're trying to achieve.**EDIT**: Sorry, I misunderstood your question. See above; if your daemon is set up to listen on the local network, then other devices can either connect directly to it or to the proxy.
Quote from: "onesmartfellow, post:111, topic:551"Maybe I'm trying to do something not doable.
Don't worry, it's perfectly doable! :grinning: It would just take some work that depends on your specific network setup.
using xmrig for mining
how to check if i found a blok?
Assuming you're mining directly from xmrig to the daemon (not using `xmrig-proxy`), type `s` into the xmrig window and see how many results are accepted. Zero means your miner hasn't found any blocks.
I'm trying to solo mine for the first time time but I have some issues. Everything seems to work properly but the p2p server doesn't work as for the IPv4.
(http://forum.wownero.com/custom_avatar/c2b8b98798f36661b5b50c2431d597506e744518.png)
How do I fix this?
What's your OS? Can you post your config/command line here?
Also, make sure that no other instance of wownerod is running.
I'm happy to report that coming back fresh after a couple days, along with the invaluable guidance of @orklemerkle , I was able to get things up and running. As it wasn't very intuitive for a 20 year IT veteran, I thought I'd share the snags I came across.
First off, I'd like to reiterate that my goal was to get the daemon running on one device, xmrig-proxy on another, then have a bunch of devices, including the daemon runner to mine using the proxy. But most of my notes here will be helpful to first time installers just trying to get the daemon running and being able to connect to it.
The documentation seems to heavily rely on monero's, yet there are changes that I was not able to find the documentation for, granted I honestly didn't look too hard either as I assumed it was me that was doing something wrong and just troubleshot from that mentality.
The first piece is the config file, monero's documentation states that it looks by default for bitmonero.conf in the data directory (where the blockchain is located). Putting wownerod.conf in this directory does NOT have it read in, which I discovered by tweaking the values I could see during start up and they were not changing. Putting `--config-file path/to/config` resolved this.
The second hurdle encountered was an error message on start-up as follows:
```
2021-11-03 10:29:39.123 I Loading checkpoints
2021-11-03 10:29:39.124 E Invalid argument to --dns-versions-check: enabled
```
Through trial and error, as I had an original, yet not configured for my purposes wownerod.conf file that would not receive the error, was that `check-updates=disabled` is necessary. If `enabled`, the error appears and the daemon won't start.
After this, the daemon would start and it was a matter of applying @orklemerkle 's guidance on setting the `rpi-bind-ip` to what I wanted the xmrig-proxy to connect to, along with `restricted-rpc=1`, `confirm-external-bind=1`, and `public-node=0`
Once set up as above, I had no problem connecting xmrig-proxy and getting all miners to connect to it. I actually prefer using the proxy as there's more feedback as to 'yes, it's mining and yes all is well' as the shares are accepted as opposed to just the miner category logs popping up with one's hashrate at the configured cadence.
Good luck everyone. Hit me up with any xmrig miner or proxy related questions you may have as I've had a fair amount of exposure the past few months.
OSF
How do you tell **if** you are using xmrig-proxy? Does Owen Wilson run up behind me and whisper "Wow" in my ear? (I sure hope so)
WOW indeed. To see whether you're using a proxy, check xmrig's `config.json`. In the `pools` section, note the `url` and `daemon` values.
Assuming that the config works, `"daemon": false` indicates you're mining to a proxy (or pool) of some sort. `"daemon": true` implies you're mining directly to a daemon without a proxy.
To be extra sure, check the `url` value, denoted `"url": "`_`IP_ADDRESS_OR_HOST`_`:`_`PORT_NUMBER`_`"`. Note the colon before the port number. By default, `xmrig-proxy` listens on port `3333`, so the miner should connect to that port. Daemon mining uses `wownerod`'s RPC port, by default port `34568`. If your proxy and daemon IPs are different, check that too.
Sorry, still figuring out the nuances of this forum's linkages. Probably best if I just do this:
(http://forum.wownero.com/custom_avatar/3524b18ed3ea748e993a59a4e75423221fed8571.png)
How do I check if I found a block **if** I'm mining to xmrig-proxy.
(lost the ability to preview the markdown so apologies if this looks weird)
OSF
Ah, sorry. I *thought* you meant for me to be instructive for the benefit of everyone else here.
Look at `shares` in the xmrig-proxy output. 0 means no blocks yet. More than that means you've found a block. For an example of what finding a block looks like, there's an example on the other thread here:
https://forum.wownero.com/t/how-to-mine-wownero-with-xmrig-proxy/672/41?u=orklemerkle
As you can see there, `shares` increases to 1 and there's a little `+1` on that one line when the block is found.
**EDITED**: Sorry about the incomplete post--should be fixed now.
Hello, total noob here. I tried following the guide to get set up solo mining and was not smart enough to finish the last step, actually starting. Got the node all synced.
For reference I'm barely smart enough to pool mine XMR with xmrig (not actually profitable just doing this to learn and contribute)
So then I saw some instructions to mine wownero with xmrig and that its faster, so I tried setting that up and I think its working, but since I havent recieved a block reward yet, (nothing in my wowlet) and I dont know if the fact that I'm mining through xmrig means that my wownerod cant tell I'm mining? because it says "not mining" on status check, whereas xmrig is definitely getting "new jobs from localhost..."
Feel free to call me stupid, but would love some help. Might cross post to reddit too.
The "not mining" status on `wownerod` only tells you that `wownerod` itself isn't doing any mining. It looks like your `xmrig` is working properly, though, so you're in the clear.
Hey, I have a question because I noticed something weird.
I was mining for about 10 days straight with no luck and today after requiring an emergency reboot I noticed my start script didn't have the spend key specified. Does this make a difference? the only difference I've noticed so far after specifying the spend key is that my hashrate went up by a little bit (Only about 50 H/s) but otherwise I get the same outputs and everything.
I'm using debian 11 and the installation of wownerod was done with the cli .deb package btw.
thought the spend key was needed to sign the block, weird strange that it works with out. maybe it hashes as expected until you win and then fails because no key is available to sign?
I am trying to set up the mining on MAC OS
I get the notification unknown command: ./wownerod --start-mining HereIHavePutMyKey --spendkey HereIHavePutMyspendKey
what am I missing here?
Help would be appreciated. Thank zou.
"./wownerod" is the path to the wownero daemon, so you must be on the same folder :)
Hi ... what do you mean exactly with this "same folder" ?
I got it to work ... Thank you Kryfi !!!!
I have one more question .... I tried to increase the threads ... the command --mining-threads does not seem to be a known command .. in fact I get an "unknown command" response
Do you have any idea about the threads?
Yes it's working, you need to enter the argument like this:
./wownerod --start-mining HereIHavePutMyKey --spendkey HereIHavePutMyspendKey --mining-threads 8
Yes .. .I got that to work, too
So if you dont mind I have two more questions.
1. How many threads can I run?
2. I noticed that I get these type of notifications
|2022-03-21 20:55:30.401|I [xx.xxx.xxx.xxx:xxxxx OUT] Sync data returned a new top block candidate: 406553 -> 406554 [Your node is 1 blocks (5.0 minutes) behind] |
|---|---|
|2022-03-21 20:55:30.401|I SYNCHRONIZATION started|
|2022-03-21 20:55:31.197|I Synced 406554/406554|
|2022-03-21 20:55:31.197|I SYNCHRONIZED OK|
|2022-03-21 21:18:28.011|W wownerod is now disconnected from the network|
|2022-03-21 21:18:28.011|W wownerod is now disconnected from the network|
|2022-03-21 21:18:31.524|I [xx.xxx.xxx.xxx:xxxxx OUT] Sync data returned a new top block candidate: 406555 -> 406559 [Your node is 4 blocks (20.0 minutes) behind] |
|2022-03-21 21:18:31.524|I SYNCHRONIZATION started|
|2022-03-21 21:18:31.756|I Synced 406559/406559|
|2022-03-21 21:18:31.756|I SYNCHRONIZED OK|
How many of these are normal and what could I do to improve the connection?
How bad is this for the actual mining?
Thank you a lot.
1: For best results, set it to number of your physical cores.
2: You lose connection and your node is out of sync with the network.
Thank you ... I really appreciate your help
I am running three Computers right now ... two MACs and a PC with Ubuntu. All of them get these disconnection messages. I have 1.2kH/s and 1.0kH/s and 0.7kH/s right now. The 0.7kH/s is running with one core only, as I use that computer for music production and do not want to eat from it too much calculation power. They all get these disconnections at different times, I did check that. So it is not my internet connection.
I am also not sure what happens when I close the Laptops. How do I know it continues mining?
I know a lot of silly questions.
If you have several computers, I advise you to watch this tutorial instead https://forum.wownero.com/t/how-to-mine-wownero-with-xmrig-proxy/672 :) After if you still have problems you can try to ask for help on Discord.
Solo mining is now available inside wowlet https://git.wownero.com/wowlet/wowlet/pulls/89
video (http://51.195.219.52/mining.mp4)
A new version of WOWlet should release soon^tm that has this feature included.
Any tutorials for wowlet xmrig mining, cant get it to work