snip
Well first of all i dont solo mine, i just use an pool.
No when solo mine you must not use stratum+tcp, an stratum part u need to setup what also need a lil knownledge.
So the mining adres should be: ip:port (127.0.0.1:port)
Your wallet config should be look like this:
Code:
rpcuser=JoenNL
rpcpassword=X
rpcallowip=127.0.0.1
rpcport=420
server=1
listen=1
daemon=1
Password: X
server ip: 127.0.0.1:port
In my eyes: for the coin and for the safety its beter to mine on an pool (spread the hashes) instead of put an big rig into solo mine.
This right here is pure gold. Most people and how-to's kinda graze over the necessity of these settings and either tell you to leave them alone in the json; or don't even mention what they really do.
I have yet to mine to any of my wallets in the past; so this is a nice bit of info in my eyes.... I know for as long as ive been doing this, I should have known this already... but i have always been using places like xpool/zpool historically... and avoided "wallets" for any non-major coin like the plague.
Ill get it set up and give it a whirl.
my hashrate isn't insane; (rather mundane) but I would rather point my gear to my internal addresses to mine; than to point it to a pool. I wanna do the full-solo on this one... just because.
Do you know what dictates the address that the mined earnings go to by the wallet? or is it automatically a new address for each signed block?
FYI; I have added the nodes and everything; but can't get past either 50% or 75% synced....
*edit* FYI; I corrected some typos in my quote for others....
now im getting somewhere:
[2018-08-09 05:16:22] NVAPI GPU monitoring enabled.
[2018-08-09 05:16:22] 1 miner thread started, using 'xevan' algorithm.
[2018-08-09 05:16:22] JSON-RPC call failed: Method not found
[2018-08-09 05:16:22] get_work failed, retry after 30 seconds
looks like ill need to set up a stratum host. Looks like a few firsts on this. But worth it for the know-how in my eyes.
*double edit*
A bit later, and presto. Wallet seems like its all synced (no progress bar). Put on setgenerate true; and ~25Kh off my i3 its currently running on.
Turns out I don't want to dive into node.js; so I am looking at takng my Dell Precision R5500 sporting 2x SLAED and 64Gb ECC that is literally just sitting here doing nothing but collecting dust at the ranch (no, literally....), and ill bring it to where my .com is hosted and plug it in.....
Gonna jump down the rabbit hole and install yiimp.... It has room for GPU's and HDD's galore... so I may go full ham on it and set up my own full-on solo pool. It seems easy enough to set up all the API keys and configs for autoexchange when all is said and done; so If I decide to add any old wallet after; I just need to have HDD space considerations, and do some quick reconfigs.
Right this second I am doing a trial run remotely via ssh on a Pi that's hooked up in that location; and so far; its going rather smoothly... I may have a yiimp web admin interface to play with shortly.
I do see why you recommended just using a pool; but I have the gear; and the knowhow to get it done or figure it out.... and if I run into trouble; I am always willing to ask or dig into some reference materials.
ccminer just flat out doesn't speak the type of work requests that wallets do.... sgminer still has the support; but what's the point since AMD cards fall way short on these types of algos.
Im the kind of guy who runs his network connections under at least 3 layers of VPN tunnels. They are all my own; and they all do their job... but all of them serve a special and independent purpose primarily. Secondarily it's the only way I can truly get all of my devices; everywhere; to be able to talk to each other as if they were on the same network. (the wonder of a common TUN). This just makes several devices end up encapsulated under at least 3 parallel encrypted connections. (my middle finger to the legal limit of encryption you are allowed to apply to a datastream)
now. although mine from the first day of the project
. It would be nice if this get fixed in the next update.
instead of random ones people make haha
)
