Open rodvar opened 1 day ago
Thanks so much, @rodvar, for putting this together. I've have read though it, but will wait to comment more fully until I've shared the materials I'm currently working on later today. I'll get back here in any case by noon tomorrow (Wed).
I'll get back here in any case by noon tomorrow (Wed).
hi @rodvar, all, as mentioned in the "async debate" video I published today, I'd like to give folks a chance to watch that video and consider my arguments as to why we should not implement the full node option on Android. If there's a consensus that we shouldn't, then we could update this proposal accordingly and I would give it a thumbs up after possibly some more minor discussions. As it stands right now, I wouldn't give it a thumbs up because of the full node aspect, but I'm really glad to see the rest of the proposal and wouldn't want to prematurely downvote it. So if you don't mind, I would wait until, say, Monday or Tuesday to weigh in here. Thank you again, in any case, for putting it together.
Background
This proposal is in line with making Bisq Network accessible on Mobile Platforms following the philosophy of Bisq2 - to make it easier for both, experienced and newcomers, to trade Bitcoin in a decentralized way as well as defending Bisq motto: exchange, decentralized, private & secure.
We want to do an MVP (Minimum Viable Product) from 0 to release in the market and hopefully grow from there if we see enough interest.
To achieve this goal, we are building a total of 3 mobile apps that can be divided in 2 categories:
Run a Bisq (Easy) Node in Mobile
An Android app (called
androidNode
) that runs bisq core in its veins aiming to bring a fully featured trading version of Bisq2 (also referred to as its main protocol - Bisq Easy) to Mobile for full privacy & security.Share a trusted Bisq Node
A thin Bisq App Client (coming in Android & iOS flavors) able to be configured to connect to a trusted Bisq node (over clearnet) to cater to people willing to try Bisq from somebody they trust (popularly described as "Uncle Jim") who is willing to share his Bisq node with them.
For more information on the challenges that this poses please refer to the:
Proposal Summary & Limitations
We propose a timed-effort of a well defined MVP scope for 3 apps:
androidNode
app includes curated security/anonymity related Bisq2 networking code will support bisq-easy clearnet only (for MVP, potentially adding tor in the near future though there is ongoing effort to bring this for the MVP) potential to support more options in the futurexClients
orandroidClient
andiosClient
apps allow users not willing to run a bisq node to configure a trusted node and still be able to use bisq2 from their mobile this option allow us to have bisq in iOS too that still has a big market share in developed countriesLimitations
xClients
apps depend on having a Bisq2 API and that is not part of this proposal. This is because there is still ongoing discussion on what the API should allow and how it should be implemented. However, this proposal includes developing the client apps with a mocked API implementation for them hoping the API will be done either in parallel or right after this effort is finished.What makes this mobile proposal attractive?
There have been many intents to bring Bisq to mobile with no real success, some Bisq maintainers called it specifically “big failures”.
We believe this is a winner proposal because:
xClients
since Bisq API is not developed yet.What has been already done prior to this proposal?
androidNode
appEstimations and Timeline
Assumptions:
Available Resources per Cycle:
The following describes the “Initial Team”. We hope being this is an open-source project some people will join in along the way, but we consider this the team to be responsible for “crossing the river”:
rodvar
: FT // bisq-mobile maintainer and devnostrbuddha
: PT // designer and devboilingfrog
andcbeams
: Hi experienced Bisq devs who offered to have a minor commitment of min 5h / week each for Bisq2-related tech barriers removal and project oversight.Being an open-sourced project, there could be (and looks like there will be) more people joining in to help along the way but the proposal is done with the initial time that is ready to get the goal to the other side of the river altogether from the get-go.
Total Cost and Timeline
Shared
Clients-Only Features
Node-Only Features
note: for the
xClients
connectivity related stuff will be mocked until we have APIs in place.Summary of Total Estimates:
Based on initial team availability, between 4 and 5 months of work is anticipated, details below:
Total Time Estimate: ~4.5 cycles
Total Cost Estimate: ~$90,000.- ( ~1.33 BTC at the time of writing)
Important notes:
This is a rough estimate based on all of the above
A report to the DAO will be done at the end of each cycle to keep everyone accountable, track progress and maneuver accordingly if needed.
Timeline
Cycle 1:
Cycle 2:
Cycle 3:
Cycle 4-5:
androidNode
app should be ready to release at this stage: prepare app listing on Google Play + upload and release on stagesxClients
apps: same if API is ready, otherwise API should start development to be able to release these