mjbrichards

Thanks for your speedy response, @grisumbras. I had already tried changing the order of the #defines and it made no difference; but disabling autolinking worked immediately. Would it be possible...

I don't think that you'd want to include a timestamp range for (some?) queries by user data. For instance, if I wanted to see all the ledger entries relating to...

I agree that you'd want to organise your storage like that, but imo that shouldn't be visible to the user of the API. They should just be able to say,...

I'm assuming that the entries in TigerBeetle will represent the system of record relating to transfers in the switch. Information (much of which will be additional to the information that...

Thanks very much as usual, @ehenrka, for your detailed and penetrating comments. I attach a revised version of the proposal with changes tracked, and a commentary on your points below:...

Sequence diagram to illustrate the transfer flow: 

Thanks for your comments, @ehenrka, and my apologies for not responding to them sooner. I should have said "charges" rather than "fees". The FXP will, I think, need to ensure...

My thinking on this point was as follows. If the FXP can only express charges by incorporating them into the conversion rate, then the charges will inevitably be passed on...

Attached is a detailed sequence diagram of a transfer including currency conversion. Let me know if you have any comments. 

Apologies for the delay, folks, but I have now completed a general revision of the structure of the FX API, based on @ehenrka's comments. I have versioned it as 2.0....