0xmountaintop

@gcomte you might also want to remove account table's l2_pubkey combine it as ```rust# [derive(sqlx::FromRow, Debug, Clone, Serialize)] pub struct AccountDesc { pub id: i32, // TODO: i32 or i64?...

TODO: foreign key for user-id

we can bind a user to a public_key. (for example, extract publickey from signature, then check hash(publickey) == address) then we can follow https://huobiapi.github.io/docs/spot/v1/cn/#urls for user: ```go package main import...

for server, 1. check current_timestamp-1s (?) < timestamp < current_timestamp 2. the request is not replayed (binded to timestamp) 3. verify (hash, pubkey, signature)

> > Question: I guess an order can become inactive just at the same time we reply it as an active one under a query. And this issue will not...

> At least we can implement 'get all my orders' by merging 'get all my open orders' and 'get all my closed orders' One thing we need to be careful...

> I guess trader may be much interested in the opened orders then the closed one I totally agree. > by doing that we are in fact have another API...

> Framework: actix-web? ( We need to implement websocket stuff later, actix-web is a good choice for this ) Yes actix-web seems the top option for now, in terms of...

Thanks for reporting the bug, we will look into it!

I prefer Option2. Besides, `get_all_open_orders` seems more frequently used than `cancel_order`, checking `len(market_orders)` each time querying `get_all_open_orders` seems redundant.