Wilmer Paulino 9a2d6c4c50 clientdb: stage batch updates under distinct bucket ... If trader A provides a signature for a batch, disconnects, and trader B, who is also in the auction, bails, then the auctioneer will re-attempt matchmaking. If trader A hasn't reconnected by and a successful batch is made without them, then the updates would need to be rolled back. Previously, since we would overwrite the main account and order state, we'd lack information in order to do so. By staging the update under a distinct bucket, we can now do so properly by simply removing the state within it.		2020-04-27 15:51:58 -07:00
..
account.go	clientdb: specify src and dst buckets for updateAccountTX	2020-04-27 15:50:03 -07:00
account_test.go	multi: allow account closure through expiration and multi-sig paths	2020-02-05 12:09:47 -08:00
batch.go	clientdb: stage batch updates under distinct bucket	2020-04-27 15:51:58 -07:00
batch_test.go	clientdb: stage batch updates under distinct bucket	2020-04-27 15:51:58 -07:00
codec.go	clientdb: add missing types to codec	2020-04-14 15:41:22 +02:00
db.go	clientdb+order: use 2-step commit for batch persistence	2020-04-24 10:57:41 -07:00
log.go	multi: add persistent bolt storage	2019-12-11 18:59:58 -08:00
metadata.go	clientdb: stage batch updates under distinct bucket	2020-04-27 15:51:58 -07:00
order.go	clientdb: specify src and dst buckets for updateOrderTX	2020-04-27 15:48:42 -07:00
order_test.go	client: add batch persistence	2020-04-03 21:53:04 +02:00