Yes, i can confirm an update will be released this week to get the new trading pairs of cryptsy inside. We are issuing a small update to get everything updated again. This update is relative late because we wanted to release the big update, but we are behind schedule with it. I am sorry for this.
This is a
very simplified image of how the arbitrage-bot will work. In reality it is much more complex and more options are possible. Please do not think about this to much, because the software will take about this. We have made this fully automated for you so it will be very easy to use.
We are currently in Alpha testing stage to see how the arbitrage-bots are working out. Once we have something solid and approved then this functionality will come as a free update to all licenses.
About order execution speed, please have good look of what you see. For the software and logic it is really important to place the order as soon as possible. After this it does not matter how fast the order itself is filled. The exchange itself will handle this process itself. It is also pointless to rush this tracking of an order because it will only flood the API and there is no advantage to it. So in conclusion it is very normal to see a delay between EXECUTING and the FILLED state. Please do not worry about this, its by design and for the best.
Prices and amounts are NOT rounded at all. We also do not use doubles or floats are something a like, instead we use pure numbers called decimals. These numbers are really exact and they show themselves to as many decimals as possible. However, there is a small drawback to this, sometimes a rounding can not be avoided like at multiplying numbers. If its needed then the software will implement a method called cutting. This a very common way in the financial work it out this way, and the impact of it can be fully ignored.
To get the most pure way to see what the software sends to the API please have a look to the debug logbook. In here you see the exact numbers that are send from the software. We can not show this more pure then this because this information comes from the lowest level of the software API implementation.
We are looking after a few recent reported bugs and i can not yet clarify them yet. There is a 403 error, possibly caused by the APi of bitstamp and there are a few reports about the fee reading of cryptsy. For the last one i would like to give out the advice to use the PercentagePrice -insurance. Its the same as the FeeOvercome insurance but with the exception then the software does not have to read the fee percentages, in this setup you can edit them yourselves. So its avoids the fee reading at cryptsy. - In anyway, please know we are aware of these strange bugs and we will resolve them as soon as possible. Its my target to solve them directly when we release the small update to add in the new coins.