How to solomine Trezarcoin

This is a guide on how to solomine Trezarcoin, a relatively new cryptocurrency that I believe has some legs behind it.

So on to the instructions on Windows. Sorry I don’t have a Linux box handy to doc this with.

What you need

Trezarcoin wallet. You can download that here.

ccminer. I am using an older build because I am seeing better performance with it on my Nvidia 1070 GPU. YMMV. You can download that here.

Setup

Install the wallet. I created a directory on the desktop and named it TrezarCoin. Instructions assume that path.

Create a file named trezarcoin.conf and place it in the Desktop\Trezarcoin\data folder.

Edit said file in notepad and fill it with some details:

irc=1
dns=1
qtstyle=1
daemon=1
server=1
stakegen=1
logtimestamps=1
minersleep=2000
stakemindepth=1000
stakemintime=24
stakecombine=40
stakesplit=80
port=17298
rpcport=17299
rpcallowip=#.#.#.#
rpcuser=USER
rpcpassword=PASS
addnode=162.217.249.198:17298
addnode=46.4.0.101:17298
addnode=113.176.188.121:57514

replace the “rpcallowip”=#.#.#.# with your IP address of your mining node on the local network. If you are mining local on your machine with the wallet, then do 127.0.0.1 for example.

Replace USER and PASS with something stronger than my defaults.

Run your wallet program, \Desktop\TrezarCoin\trezarcoin-qt.exe

Let it sync up with the network. This may take some time.

While you are waiting configure your miner.

I make batch files for my various mining antics so I made a localtzc.bat file in the same folder as my ccminer program.

The command line is:

ccminer64_75 -a neoscrypt -o http://#.#.#.#:17299 -u USER -p PASS -s 2

Replace the #.#.#.# with the IP of your machine running the trezarcoin-qt.exe program. Replace USER and PASS with what you defined in the .conf file above.

Save the localtzc.bat file and run it.

You are now solomining.

picofsolomining

If you have issues. I have no idea. It seems to be working for me. Work for you? Leave a comment, let us know. Didn’t work? Let us know.

Want to know your solomining output expectations?

Go to “WhattoMine” and put in your hashrate and power costs and whatnot and see how many coins/day. A block is 100, so for every 100 a day, you will find one solution.

 

Edited Why I shouldn’t write while dealing with a fever… under discussion.

So I am mining some coinage in the Cryptocurrency world. Mainly because the miners make GREAT performance testing resources. Nothing like maxing out CPU or GPU or both whenever you need it (and making a little speculative coin on the side).

But, Windows the mining program was doing me wrong. By default, the thread scheduler thing sets a new process to use ALL cores available and apparently go in sequence. This is ‘ok’ but I find I get MUCH better results when I don’t let the thread scheduler miner handle my CPU-based miner threads.

Case in point:

miner going slow

Note CPU #6. Why is it 70,000 hashes/second faster than it’s peers? Because it’s the only miner thread that doesn’t have it’s partner CPU also running at 100%.

Let’s look at this in Task Manager, this is what it looks like:

task manager core count.png

So see the pairings? CPU 0/1, CPU 2/3, CPU 4/5, CPU 6/idle.

That’s why CPU 6 can run faster. It’s hyper-threaded pair isn’t mussing it up. Plus it perhaps has better caching since it isn’t using pipeline cache for another busy thread (conjecture).

Anyway, changing this is trivial. I found my miner in task manager and right clicked it and selected Processor affinity.

proc affinity

See how it’s spread out on all CPUs? Yeah we’re going to fix that.

better proc affinity.png

Now I’m using every odd CPU, and every even CPU is not used by my miner process. Fair enough. I am only allocating 7 miner threads by the way, so we’re giving the miner an extra thread. Who cares. It might not use it. Don’t care.

Hit ok and see the results:

change.png

See, CPU 0, 2, 4, 6 are falling. The odds are all increasing.

The results? Pretty damn good. I went from 990 kH/s on 7 mining threads to 1746 kH/s.

I’ll take it.faster.png

All this because Windows thread scheduling leaves something to be desired…since like, a while ago. But that’s another story…

Carl schooled me.