Order matching gets complicated, I think, because one (or both?) parties might end up paying a currency conversion fee for the (parts of) of their order that are matched against an order in a different currency - but presumably this should only ever happen where this is more advantageous then matching against orders in the same currency.  It's not at all clear to me whether it's possible to come up with a well-defined definition of how this should work (although presumably it must be, since I believe Gox does something like this).

ETA: The nice aspect is that, if done right, then worst case I'm no worse off in terms of fees than if I'd been forced to convert my GBP to EUR before buying XBT - but if I'm lucky and the native XBT/GBP liquidity is there I might do slightly better.

@Dargo

I first want to say that I firmly believe Kraken is going to be the exchange that dominates this market but there are definitely some adjustments early on that need to be made.
 
I think the problem Kraken is suffering from is not just on the market maker side (which will fix itself over time), not the regulation side (which hopefully you guys are hard at work on), but the ability for traders to actively trade. Currently, the charting is not overly impressive but more importantly, the act of placing a trade takes quite a bit of time to go from one tab to the other tab. You can't even see the chart and execute the trade on the same page without covering the page with the chart. I think you should take some notes from clarkmoody and rtbtc's platform and adjust the Kraken platform to truly meet the traders needs. You have the orders traders want, the security traders want, the leverage traders want, but not the platform to trade that traders want.

Keep up the good work and I truly hope Kraken succeeds.

Thanks,
Ian

Just a note for the API docs:

https://www.kraken.com/help/api#get-account-balance

says:


but returns:


Probably should say:


I'd highly recommend putting example JSON responses in for every API method, helps speed up debugging :-)

Rather predictably hit the API rate limit :-)

EAPI:Rate limit exceeded

Can you specify what the rate limit is? Bitstamp is 600 request per 10 minutes, ie. 1/second...

My bot is throttled, so just need an accurate quantity. Thanks!

I understand Loozik - I'm a hard-core chartist myself and I agree that our charts aren't much use. Personally I wouldn't find charts very useful while the volume is low though, but maybe that's just me. I'll make contact with some of these sites and at least get a discussion going. Does anyone know if there is a site that can integrate with API and offers basic charting tools? Sites that require a websocket will take us longer to integrate with.

We don't have a specific timeline for California or any other US state yet. Our launch in Germany is very close, then the focus will be US states and California is a top priority.

Your earlier suggestion on the API documentation is noted.

The basic API rate limit is 1 call every 5 seconds. You can do faster bursts up to 10 calls, but then you'd need to follow that by a 50 second pause before you could resume the 1 call very 5 second rate. If you get locked out, it's for 15 minutes.

For really active traders (including those who want to market make with us), we can offer much higher limits. Anyone interested in this should contact us with a support ticket.

Just found this site via blockchain.info

How didn't I know about this!? Lovely site, just waiting for verification to come through before depositing and trying it out

Have you wasted any of your time on RTBTC 




@Dargo It would be great to have Kraken data and trading on the RTBTC platform. A streaming data source is not required but strongly encouraged.