[bisq-network/projects] Dev Call - Priorities (#60)

[Stan]

>> 2. API > What help do you need to reduce the time of this task?

@ripcurlx has been using the api for personal stuff and that helps with testing.  @sqrrm has done all of the api reviews.  It will help if he continues.  They both have their own chores, so I'm not hoping they can take on much more than in the past.  Other devs said I was making steady progress before api work was put on hold.  I think I can return to that speed again pretty soon.

A fully functional api containing most/all features of UI is a long term task, and involves some refactoring (indirectly related to api, and not visible to end-users) to avoid duplicating code.  No ETA on delivering the "finished" api.  And adding some trading bots to the release is something I want to do, but we have to be cautious about it.  Up till now, the consensus was to let end users build and run their own bots at their own risk. It sounded kind of straight-forward and easy in the dev call, but much more discussion and prototyping is required. 

In the short term, I'm making sure the api will support creating swift payment accounts soon after @jmacxx's [PR](https://github.com/bisq-network/bisq/pull/5672) is merged.  I have it working in a local copy of his branch, and have asked him to review the swift account json-form (api analog to the ui's swift acct form).

I intend to start work on XMR <-> BTC trading w/ api tomorrow or Monday (06-Sept).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/projects/issues/60#issuecomment-913024353
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210904/02e62201/attachment-0001.htm>