-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dev Call - Priorities #60
Comments
@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 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). |
Hi @leo816 I would like to add 6-10 payment methods over the next couple of months. I need help of a dev that is available to do the coding work required for adding them. @jmacxx has done three payment methods, I am unsure as to how many more @jmacxx can take on? It would be great if one or two more devs were available. |
Dev call 2021-09-10Topics1. Devin's Proposal
hybrid app development approach, a single codebase that could support both, Swift app for IOS and java for android. concerns from Christoph: too many dependencies, is it easy to do an audit? potential security issue? 2. API @ghubstan : Update: about 3/4 done with work to support XMR/BTC trading pair in API. 3.How can we attract more developers? Stan: Maybe we could narrow down the search for web UI devs. I can build a webapp over the core-api, and server Json. Also a consistent road-map... not too many detours on new projects that get suddenly dropped. I know it can't be helped sometimes. But detours should be taken thoughtfully. |
@Pazza has some great ideas, No one is assigned yet, feel free to put ideas out there. --> Where can I read up on the ideas? Would love to know more ... |
I appologize for posting this here, I can not find another way to reach out to @pazza83. For several months now, it appears as though you are getting tagged as @Pazza which is notifying me of everything issue/comment/PR. Just an FYI to your users (as well as yourself who may not be receiving notifications). |
Thanks for reaching out much appreciated, sorry that you are being notified. Hey everyone please can you tag me in to any discussion here as @pazza83 My user name on Keybase is pazza but on here it is @pazza83 |
Dev call 2021-09-20Topics1. Bisq on mobile 2. Release 1.7.4 3. API and Daemon update I posted a warning in #general & #api about an API bug that could have shown a changing "buyer cost" value in Fiat/BTC trades (market-price-margin offers) in the CLI console's 'gettrade --trade-id' output. So far, no API user has claimed they paid too much, but it's early. 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. Attracting new developers (who may want to contribute on their free time but don't know about bisq).
5. Review of priority list Click to see new priority listthese are Bisq's top priorities in the short-term: 1. Tor. v3:
2. API @ghubstan : 3. Messaging Problem
4. Mobile app and UX
6. XMR
7. Payment methods
8. Adding Tether
- Topics for next call: |
Hello everyone, this is Andres, author of JReleaser. In your own words, what's required to consider JReleaser as ready? Please feel free to post a discussion topic and/or issues at https://github.com/jreleaser/jreleaser |
Dev call 2021-09-28Topics1. X 2. 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. 3. Review of priority list Click to see new priority listthese are Bisq's top priorities in the short-term: 1. Tor. v3:
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
4. Mobile app and UX
6. XMR
7. Payment methods
8. Adding Tether
- Topics for next call: |
Priority list 1. BSQ<->BTC swap
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
4. Mobile app and UX
6. XMR
7. Payment methods
8. Adding Tether
- Topics for next call: |
Dev call 2021-10-15Topics1. BSQ<->BTC swap 2. Payment Methods 3. API update 4. XMR/BTC swap 5. Review of priority list Click to see new priority listthese are Bisq's top priorities in the short-term: 1. BSQ<->BTC swap 2. API Any work on a Bisq/WebApp POC will have pushed back to sometime in November or December. XMR: API work to support XMR / BTC trd pair was done, but also being held back until after atomic-tx work is merged. Then I will re-work that to. 3. Messaging Problem Possible solution is included in the next release. 4. Mobile app and UX
6. XMR
7. Payment methods
8. Adding Tether
9. XMR/BTC swap - Topics for next call: |
Dev call 2021-10-29Topics & Priorities
|
Dev call 2021-11-08Topics1. BSQ<->BTC swap 2. Payment Methods 3. API update 4. XMR/BTC swap 5. Research & Connectivity 6. Review of priority list Click to see new priority listthese are Bisq's top priorities in the short-term: 1. BSQ<->BTC swap @ripcurlx : all - getting the PRs reviewed and merged so there is ample time for system testing of release 1.8.0. 2. API 3. Messaging Problem Waiting for more bisq logs to better understand this issue 4. Mobile app and UX
5. 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:
6. Payment methods 7. XMR/BTC swap - Topics for next call: |
Dev call 2021-12-07Topics1. Provide ASIC resistant PoW scheme for BSQ swaps 2. sqrrm started reviewing the API PRs 3. Messaging problem 4. Review of priority list Click to see new priority listthese are Bisq's top priorities in the short-term: 1. Release testing for 1.8.0 2. misq/bisq2.0 3. API 4. Messaging Problem @ripcurlx found an error log that may be related to the messaging problem, specifically regarding it having an incorrect public key shown. more information will follow. 5. Mobile app and UX 6. XMR
8. Payment methods I started reviewing the API PRs, they should be fairly easy and it needs to be done |
Dev call 2022-01-10Topics1. Misq brainstorm and updates 2. Recommendation for power users 3. We need a full time UI developer 4. Growth 5. Review of priority list Click to see new priority listthese are Bisq's top priorities in the short-term: 1. bisq monitor fixing 2. misq/bisq2.0 3. API 4. Mobile app and UX 5. XMR - Topics for next call: |
Dev call 2022-02-11Topics1. Bisq2.0/Misq brainstorm and updates 2. We need a full time UI developer 3. Growth/marketing 4. Liquid implementation 5. Updates from last call 6. Running the numbers 6. Review of priority list Click to see new priority listthese are Bisq's top priorities in the short-term: 1. API I am working on a stand-alone bisq-apidoc project to parse pb.proto and grpc.proto files into Markdown for a Slate After bisq-apidoc is ready for review (probably next week), I will start commenting the Bisq repo's pb.proto The next phase involves several tasks, not necessarily done in the following order or serially:
2. bisq monitor fixing 3. misq/bisq2.0 next goals for bisq2:
@jimmyt: some simple python snippets showing how to call the api / rpc methods in 4. Mobile app and UX 5. XMR - Topics for next call: |
Dev call 2022-02-02Topics1. Comments on Tasks/priorities 2. Next release 3. Growth/marketing 4. Concerns 5. Review of priority list Click to see new priority listthese are Bisq's top priorities in the short-term: 1. API @ghubstan update for dev call 2-Mar-2022: I've been working on an API Reference doc generator: https://github.com/ghubstan/bisq-grpc-api-doc I have started work on my first Python API bot example: migrating ripcurlx's After this 'best' -- or rather, most 'competitive' -- price bot is deemed OK, I'll work on a market-maker bot. There is a guy from BTCPay named Wouter Samaey who wanted to talk about API integration issues, and now that there's an API reference and progress on Python bots, I'm more comfortable chatting with people like him about integration issues. I'll try to convince him that investigating Bisq API integration is worth his time. Last thing I want to say here is that the API users are going to bump into problems with the bitcoinj wallet. There is a hard limit on the number of v1 trade protocol trades that can be made during a single API daemon session: I'm pretty sure it is 33 trades. (Sqrrm and I struggled with this during his work on the BSQ swap changes.) I don't know how to work around that without shutting down and restarting the server, and I suspect it will be [EDIT "one of"] the most annoying problems for any businesses wanting to integrate the Bisq API. 2. misq/bisq2.0
next goals for bisq2:
3. Mobile app and UX 4. XMR 5. bisq monitor fixing |
Dev call 2022-04-20Topics1. Comments on Tasks/priorities security model in terms of how the offers are secured, reputation concept based to bring everything 0 and 1. this number will be calculated directly in the background, when you create an identity it has a timestamps and that is a small part of reputation. 2. Growth/marketing 3. Review of priority list Click to see new priority listthese are Bisq's top priorities in the short-term: 1. API navigation changes have been made, it won't be transferable to bisq2.0 ripcurlx will also have this as n1 priority. next goals for bisq2:
2. Mobile app and UX 3. XMR 4. bisq monitor fixing |
Dev call 2022-06-24Topics1. Comments on Tasks/priorities
2. Bisq 2.0 3. Growth/marketing 4. Review of priority list Click to see new priority listthese are Bisq's top priorities in the short-term: 1. API Now working on some java API bots these past few weeks, and just checked them into the https://github.com/bisq-network/bisq-api-reference project. There is still some polishing left to do in the code, but they're ready to run on mainnet. Next thing for me to do is explain them on the API reference site. New API java bots are at the bottom: Explanation for the TakeBestPricedOfferToSellBtc bot is here: 2. Mobile app and UX 3. XMR 4. bisq monitor fixing |
Dev call 2021-09-03
Topics
We all agree on Misq/Bisq's 2.0 long-term vision. for that to happen, we need the right developers with enough experience on this area. Bisq contributors should do all they can to attract the right talent.
With this in mind, these are Bisq's top priorities in the short-term:
1. Tor. v3:
2. API
3. Messaging Problem
4. Mobile app
5. UX
Once again the idea is to make small changes to the existing app that require low effort and that can potentially improve the overall user experience. Enabling new coiners to use bisq as they would use any other high volume exchange.
6. XMR
7. Payment methods
@Pazza I believe you are on this. How many payment methods do you plan on implementing in the next 2 months? what help do you need with this?
8. Adding Tether
- Topics for next call:
Click to see the example
what it would look like:
At 00:00, node A creates a SELL swap offer and publishes their public key, and then disconnects from the internet.
At 01:00, node B connects to the internet, scans the blockchain for new swap offers, and discovers node A's swap offer. Node B takes node A's swap offer, publishes their (node B's) public key, and then posts a message in the Matrix room containing payment method info, encrypted with node A's public key and signed with node B's private key. Then node B disconnects from the internet.
At 02:00, node A connects to the internet, realizes their offer has been taken by node B, and then gets all unread Matrix messages, searching for the payment method info message from node B, decrypting it with their own public key and verifying the signature with node B's public key. Upon success, node A posts a message in the Matrix room containing their payment method info, encrypted with node B's public key and signed with node A's private key. Then node A disconnects from the internet.
At 03:00, node B connects to the internet and gets all unread Matrix messages, searching for the payment method info message from node A, decrypting it with their own public key and verifying the signature with node A's public key. Upon success, the operator of node B can send fiat payment according to the payment method details specified by node A, and then can notify that payment is sent. Then node B disconnects from the internet.
At 04:00, node A connects to the internet, discovers node B has indicated that payment has been sent, and the operator of node A verifies that fiat payment has been received. Then, node A confirms that payment has been received, allowing each swapper to close their half of the swap and receive their stablecoin whenever they wish.
In this way, a swap can be completed from start to finish without the swapping parties ever being online at the same time, and without Bisq/Commuto devs having to design/test/maintain complicated P2P infrastructure.
The text was updated successfully, but these errors were encountered: