Aeternity Windows Release (experimental) - Call for Testers


No, I picked it from a MacOS test run, but I’d expect it to be similar on Widndows


It seems, that log are different in ubuntu and windows…Anyway i not seeing mesages about block finding in mining.log.


if you are mining on mainnet it will be a while for you to see a block.


Ok, this may be a stretch, but how can i start several epoch’s on the same computer?

I tried going to the vm.args file to change the erlang name to [email protected], but when i do that the epoch node will not start and ports won’t open. I don’t see any other reference to [email protected] anywhere in the code though.

What am i missing?

Edit: answering my own question. you need to set it to “epoch1” without host. and it will run properly.

Yay! I can set up an easy demo network with this thing now.


changed network id and mining for hours, can’t find mined block in log file…what to do know?
i have 6 x gtx1070 cards.

    # CUDA mining configuration
         executable: cuda29
         extra_args: "-d 5"
         edge_bits: 29
         hex_encoded_header: true
         # Number of GPU devices which should be used in parallel.
         instances: 5


On 8Gb cards cuda miner gets out of memory error in stock (not always). You need -E 1 extra arg. But my OS hangs up in this case. I Returned to ubuntu and it works more better (solutions goes more rapidly). I think, guys with 1080Ti has no this bug.


yes, use -E 1 working on test network, but same as you, OS hang up when mining on mainnet…

win10 64bit, 4gb ram. g3900 cpu.


Win 10 64, 8Gb, G4400
Ubuntu is the only way, while they recompile cuda29.
Can you try -E 2 param?


not working. i have 6 cards, if use 3-5 cards, it only can running for minutes and crashed…or OS hang up…


Don’t combine extra_args: "-d 5" with instances: 5 - the latter will automatically add -d 0, -d 1, …, -d 4 respectively to the miner-commands being run…


Which 8GB card are you using when this error comes up? Also is the card also being used by your OS?


@aeminer @zimkan The -E parameter doesn’t apply to the CPU miners, it is only used by the CUDA miner. Thus, the memory allocation of the CPU mining process (3.x GB) might for some reason crash your system. Before such a crash the node should have written some logs. Could you post these somewhere?


there is only cuda29 in my epoch.yaml


I am looking forward for a version that includes the new Cuda miner and epoch with support for better context usage


And I am too wait. Please do it asap.


Just wanted to pop in and say hi. Been waiting for this windows version, going to see if i can get it to work on my 1060, 1070ti, 1080, and 1080ti rigs. It’s been a no go so far, but I’m going to keep at it and I’ll report back here/post any questions.

Update: So I am pretty sure I have this running smoothly on my 1080/1080ti rig with 5 cards. Just to double check, where is the best place to look for active mining happening? the epoch_mining.log (or epoch_pow) or elsewhere?


Good to hear. The log files epoch_pow_cuckoo.log and epoch_mining.log will show you what’s going on. Also in the task explorer you should see the binary cuda29 starting up frequently.

The next epoch release will come out later this week. I will then prepare another Windows release based on that one, which will include a few mining efficiency improvements.


I think it is funny you call it 1.0.1 but epoch says it is 1.1.0, can’t use aexplorer on this one without changing a few things.


Yes, because these releases were using changes from after v1.0.1, epoch itself reports to be v1.1.0, which wasn’t released at that time. I guess it makes more sense to stick to what epoch thinks while making experimental releases.


Epoch Windows Is it possible to mine in a mine pool?