Yobit offers different ICO pricing to run ICOs, for example
    - 0% buy wall (20% fee + 0.5 btc prepay)
    - 50% buy wall (10% fee + 0.25 btc prepay)
    - 100% buy wall (10% fee)

Since 0% buy wall is more expensive than 50% buy wall in yobit, and even 100% buy wall is for free, your explanation makes no sense to me.
If a buy wall is what you described (a wall which does not let the coin value drop below it), then 100% buy wall should be much more "valuable" for the person who runs ICO, since it would guarantee him somehow better price. But it's the opposite. So I am afraid I still do not understand what those payment walls at yobit mean.

Yobit even offers something like "105% price wall", which makes the thing even more confusing

Anybody has a clue wht these buy walls or price walls are?

Isn't it that nheqminer mines only on your processor? (CPU)

Hello Claymore.

I am using Dual Eth miner on my Linux servers to mine for Nicehash. Nicehash offers API which I use to find out what coin is most profitable to mine. Sometimes it is ethereum, sometimes it is not. My problem with your software is that when I stop mining other algo and I start mining Ethereum using your software, there is a big delay until your software starts actually mining. It does something for preparation, I do not know what it is, perhaps generating some DAG, or some other things. Anyway, my rigs are effectively making zero profit during the initialization of your miner, which can be 30 seconds or even more.

Would it be possible to implement something into your miner to allow it to start mining faster? I would suggest maybe two solutions, but I am sure you may came up with even better one. My proposed solutions are:

1) if there is a need to prepare something on miner startup, would it be possible to implement some commandline parameter, which would cause generating of the initial data only once, on the first run, and store it on disk, so it could be reused from disk later?

2) alternative solution, if the idea with temp data files on disk doesn't work, would it be possible to, for example, implement a command line parameter for your miner, which would specify a path to file to execute, after your miner knows it is ready to start mining? This way, I would keep my previous mining software running, then I would launch your miner in parallel, and your miner would execute my custom script just before it starts mining, and this executed script would simply kill the previous miner. So this way it would at least continue mining the previous algo during your miner initializes.

All of this may seem complicated, so perhaps if you know a better solution how to make your miner start faster (ideal is immediate), then it will be greately appreciated.

Thank you