Thanks for the overview @wrapper .
Does anyone know a website that shows which pool has how much hashing power on FTC(similar to e.g. https://coin.dance/blocks) ?
Or does anyone know a open source website for Bitcoin/Litecoin one could adapt?
There was little development in other miners then (1 yes ago). The situations seems improved, so other miners are worth testing. You may find that they are using custom configurations, I remember Wolf did some (custom AMD bins).
If you find any more specific info, post it here, I’m sure @Ghostlander would be interested in new developments (that might be portable to NSGMiner, if he missed it.
It’s interesting, that I didn’t notice that problem. My cudaminer can use one pool at a time only, so it simply waits and and tries every 30 seconds to connect and get work. It seems to return to work as soon as the pool is back
Is constantly forking to fight off ASICs worth it? (not saying we are, just a general thought) There are some advantages of ASICs on a network and it seems like eventually they will be developed for every algorithm.
That being said, I think this is likely a scam. Im sure @ChekaZ will confirm once he has more info.
Uploaded NeoScrypt CUDAminer v1.0.1. It supports Kepler (GK110) in addition to Maxwells and Pascals. The original Titan, Titan Black, Titan Z, GTX 780 Ti and GTX 780. Keplers were never energy efficient, so the hash rate is about 400KH/s for 200W TDP. Well, it works at least.
@ghostlander said in Mining... am I doing it right?:
It doesn’t matter much what driver version is in use. All CUDA miners have kernels built at the compile time by a specific CUDA toolkit.
but it does matter. eg, using alexis with driver newer than 184.xx gives only half of hashrate and does not matter how is intensity set. It has something to do with used CUDA version. I am windows user and I am not able to compile ccminer directly to my system, so I would depend on what is available on the internet.
If I use later driver than 184 and want to use alexis - it gives me max about 450kh/s.
Using tpruvot with the latest driver gives me back about 770kh/s.
you can look at a chart here which shows the avg
https://bitinfocharts.com/comparison/feathercoin-confirmationtime.html
the target is 1 min block time…so every min 1 block should be confirmed
60 mins in every hour so roughly 60 blocks an hour give or take a few…
