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

[leo816]

## Dev call 2021-09-28
### Topics


**1. X **
@cbeams Q&A

**2. API update**
@ghubstan API  update:

I am working on a new API CLI getrades --category=<open|closed|failed> method.  Submission of a PR for that will be preceded by some preliminary refactoring work in a couple of desktop module trade views and models (another PR). I think it will be ready ~6-SEP, +/- a couple of days.

After that (bugs or other priorities permitting), I was planning to build a Bisq webapp POC that depends on Core API (no gRPC), and will serve json to thin web/mobile clients.  The POC would respond to browser HTTP REST requests by serving them raw json.  I will not be building a UI.

API (gRPC Daemon+CLI) 'editoffer' support has been merged into the master branch;  it might be included in the next Bisq release.

Consensus among core devs about what I should work on next would determine my short term priority.  Otherwise, I work on a new 'gettrades' API method. 


**4. Review of priority list**

<details>

<summary>Click to see new priority list</summary>

 these are Bisq's top priorities in the short-term:

 **1. Tor. v3:**

- Done.

**2. API**

I am working on a new API CLI getrades --category=<open|closed|failed> method.  Submission of a PR for that will be preceded by some preliminary refactoring work in a couple of desktop module trade views and models (another PR). I think it will be ready ~6-SEP, +/- a couple of days.

After that (bugs or other priorities permitting), I was planning to build a Bisq webapp POC that depends on Core API (no gRPC), and will serve json to thin web/mobile clients.  The POC would respond to browser HTTP REST requests by serving them raw json.  I will not be building a UI.


**3. Messaging Problem**

- Some messages aren't going through, the reason is yet unclear.
- There seems to be a gap of information in the log. for 6 min. 
- Chimp mentioned the hybernate mode could be the cause for the messaging problem.
- PR to advise users when their PC has been in sleep mode (action item for @jmacxx) **DONE**
- upon starting mediation, prompt users to expect a mediator response within 48 hours or contact them on keybase (action item for @jmacxx) **DONE**

**4. Mobile app and UX**

- @Devinbilek update:
- Assign bounties and whether it needs consensus.
- Once that is decided, it will be advertised on twitter to look for the right talent
- Also some tasks will require ux design so hoping Pedro can mock them up.


**6.  XMR**

- Monero is our most traded altcoin, we should learn as much as possible and make sure we are doing what we can to attract as many users. these are the main complaints so far that users have reached out to us for:

1. If the auto-confirm is not activated, some sellers never respond and that can entail to having their funds locked for days. (are they all aware that they can activate this tool on settings?)
2. If the trade were to go to mediation, users have to write down their tx id and tx key to the mediator which is an annoying.
3. Given that trading on Bisq is tantamount to routinely checking if somebody hasn't lowered the price below your level it would be nice to have an option to one-click decresase or increase the offer price by 0.01% instead of manually entering the deviation when editing the offer.


**7.  Payment methods**
- @jmacx continuing to make progress,
- 23 payment methods was the goal of which 9 have been added already.


**8.  Adding Tether**

- @pazza83 already created the proposal.  https://github.com/bisq-network/proposals/issues/170#issuecomment-927207827
- We should add tether, just choose the most used chain(Omni, ERC20 or TRC20)

**- Topics for next call:**






-- 
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-929522731
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210928/bdd0a9ce/attachment.htm>