Browse Source
Fixes #1120. As per the discussion in that issue, while we can only return 'processing started' by default, and the client must monitor progress/state to see if the maker service has connected successfully, nevertheless if the maker startup is immediately invalidated by the fact that the already-synced wallet does not contain confirmed coins, we can and should return an error message instead of a 202. This commit does that, adding to the spec a 409-No-Coins response type which indicates to the API client that the setup of the maker failed for this specific reason.master
5 changed files with 46 additions and 15 deletions
Loading…
Reference in new issue