They aren't in the mempool, so you may want to resubmit them

Anybody looking to setup a MN I have coins available, contact me here or on Discord (eureka#0001)

do you know what recursion is? wouldn't you be able to recursively use your system to reduce the amount of power needed multiple times?

Most people running 0x

He mines Equihash, that's all you need to know.

I nominate this thread for Batshit Crazy Scam of the Year 2019, pretty sure it'll stay top tier for the rest of the year.

I don't get why you keep glossing over the fact that the wind would be supplying 2000 W effective power

gsrcrxsi314 where do I buy you a beer?

Spoilers: chipless works at a major battery manufacturer

... How are you going to apply 500W of power to rotating a generator and expect the generator to be able to output more than the input 500W (theoretical 100% efficiency)

literally, what

Why is that important? The reason the share is stale is because there was latency between you and the pool, a function of your internet connection, not a specific GPU. Just because the state share originated from a particular GPU doesn't put that GPU at fault.

Thanks tboy32c, very succinct explanation as to why this is the case.

OC only works on the Giant B with this mod.

You probably need to set fixed difficulty, Z1+ does 7.2GH/s and higher if configured properly.

Always been like that long before Circle was involved, kinda disappointing.

Yes, the ProgPoW thread confirmed that Claymore will be implementing support.

What makes you so sure that it's being stolen? Have you seen it sending shares to a foreign pool? Have you tried reducing the OC? It is very possible it is just malfunctioning, error reporting is not really guaranteed to work properly, especially when overclocking.

That's just normal for these units, many people report the same. A fix is not yet known.

@flexmeister it would be nice if you would disclose what actions your golang binaries are taking as well. I haven't run them in a sandbox to see what they do yet, but being golang they're a little hard to disassemble.


Thanks for releasing the source, will check it out =)

I haven't been responsible for any large hashrate spikes, I don't even own any Baikal equipment personally. My experience is limited to disassembly of the sgminer binaries (mostly before cod3gen released their work) as well as the stm32 firmware. A friend of mine did make changes to their X10 with the advice I recommended - with watercooling, they were able to get Qubit up to about 14GH/s before stability issues.