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

[leo816]

## Dev call 2022-02-11
### Topics


**1. Bisq2.0/Misq brainstorm and updates** 
Update of current plans and review of in progress work from Chimp.
Connecting from i2p y Tor simultaneously.
Liquid for multisig and swaps will work. 
social aspect -  moderators who will have to burn btc and will be compensated.


**2. We need a full time UI developer**
working for the next 4-5 months
It would also be great to have someone develop the mobile app.

**3. Growth/marketing**
BSQ/BTC Swap Have been adopted nicely but no marketing and virtually no one knows about it.
Team lead for growth is key and people engaging more on platforms like reddit is key.

**4. Liquid implementation**
Alva already implemented it this week.

**5. Updates from last call**
"API examples documentation. to show that the API is fully functional, have 3 examples that companies can embrace." 
first examples from ripcurl: https://github.com/ripcurlx/bisq-api-examples
@ghubstan :
I'm still working on api reference doc generations, then commenting api protobuf files (api reference doc content), then snippets for api calls, then the "3 examples" (complete bot trading scripts) 

**6. Review of priority list**

<details>

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

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


**1. API** 
n1 priority. It will boost volume.
@ghubstan says:
What I am doing may increase Bisq1 API usage, bringing additional funds to support Bisq2 work.

I am working on a stand-alone bisq-apidoc project to parse pb.proto and grpc.proto files into Markdown for a Slate
based gRPC API Reference document site.
Here is a sample: https://ghubstan.github.io/slate

After bisq-apidoc is ready for review (probably next week), I will start commenting the Bisq repo's pb.proto
and grpc.proto files. Those .proto file comments become the descriptions of gRPC services, methods, messages, fields
and enums displayed in the gRPC API Reference doc.

The next phase involves several tasks, not necessarily done in the following order or serially:

1.  (a) Work with reviewers of the [WIP] API Document to find protobuf definitions that need to change to make the
    gRPC API more usable and intuitive -- not worrying about backward compatibility.

    (b) Make appropriate changes to the API, update API Reference doc, repeat...

2.  Start creating code snippets showing how each API method is called from the CLI, Java, and Python.
    The code snippets will appear to the right of each gRPC API method described in the API Reference doc.
In the longer term:

3.  Work with others (ripcurlx, sqrrm, pazza, ?) to build simple Python trading bot scripts.

4.  Work with @m52go and others to figure out how to integrate a more polished Bisq1 gRPC API into
    interested businesses.


**2. bisq monitor fixing** 
@ripcurlx 's top priority from last call, still waiting for an update before editing this.

**3. misq/bisq2.0** 
@chimp's main focus.

next goals for bisq2:

- reputation based trading protocol
- Monero btc swaps
- lighting implementation (3 party based trading protocol, similar to the function of the multisig)


@jimmyt:  some simple python snippets showing how to call the api / rpc methods in 
https://ghubstan.github.io/slate
 would help a lot.  Another guy named @langfield may also help out. 


**4. Mobile app and UX**
@Devinbilek : No update on the mobile app. Had no time to work on it recently.


**5.  XMR**
Monero/btc swaps is one of the main goals, right now no one is on top of this.


**- Topics for next call:**


-- 
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/projects/issues/60#issuecomment-1036613336
You are receiving this because you are subscribed to this thread.

Message ID: <bisq-network/projects/issues/60/1036613336 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20220211/0afb71ab/attachment-0001.htm>