The pool still seems unreliable. Case in point, yesterday pool was unresponsive for a good part of the day I had to switch to another pool.

yes, already made the qibuck.cfg from the OP thread

The updated wallet still isn't connecting and sync'ing for me.

Can anyone get the client to sync. I'm not getting any peer connections. Is there a peerlist somewhere?

Did the exchange operators actually say they're going back on their plan to implement a trading api? The last relevant post I found regarding this is here:


So whatever the hell happened to this plan? Any serious exchange must have some kind of trading api imo.

It doesn't mean a bot can't be made to work with atomic-trade though. For example, you can program the bot to issue trades right through the web interface using site scrapping techniques. This is exactly what I did for mintpal despite them not having a trading api publicly available.

I haven't bother with atomic-trade only because the volume isn't there.

So there's still no trading api for atomic-trade after all these months?

When is this suppose to happen?

I'm getting timeout connecting to server.

That's how you know you're doing something right.

Two suggestions:

• Please add a backlink to this thread on the pool's support or contact page somewhere. This makes it easier for visitors to find past information and issues and gives another avenue for support.
• Please do something about the dust tx being sent. For example, put a minimum payout threshold or similar. This is a major problem atm because dust payouts from the pool becomes exorbitantly expensive, or even impossible, to spend.

That's a range check, it means if dAmount is below 0 or over 150,000,000. Or to put it differently if dAmount is not between 0.00000001 and 150,000,000 then do whatever is in the code block that follows.

See this alone should be enough to encourage people to use poloniex more over the other exchanges. Kudos to busoni for the code review.

A restart and -rescan seems to make it move again.

I'm getting a similar problem, syncing isn't going pass 20660 for me (27.73% done). On another note, the client version is still showing v2.0.0.0 for me. Are you sure you uploaded the hotfix v2.0.1.0?

Are you sure because I did not receive anything. I had a pending balance of about ~0.0006btc on coinfu that was never payed out.

Why is the starting diff showing 25000 when I connect to mine.moneropool.com but the 'getting started' section clearly states the starting diff should be 2000?

Were you referring to that? Did you mean for that to be interpreted as "only a Win64 AES-NI binary is available" because when I first read it, it sounded like there was a non AES-NI build available somewhere. And you also mentioned some optimizations done to the legacy part as well so I'm a bit confused.

This crashes on my intel Q6600 4 core processor.

Please remove the minimum trade size and replace it with total btc instead like how poloniex and mintpal does it.

Putting a restriction based on a trade's position size is ludicrous considering it does not take into account current price per unit. I haven't considered bittrex thus far for this simple reason.

Consider this simple scenario, imagine the price of a given coin doubles. The total price of our trade will also have to go up since the minimum trade size remains constant. Say a given coin's minimum trade size is 10 and current price per unit is 0.002btc; the min total price per trade is 0.02btc. When that coin doubles to 0.004btc, the min total price per trade has just went up to 0.04btc. It's not hard to see why this is undesirable.

I expect a patch correcting this flaw asap before I can really consider using this exchange.