[bisq-network/roles] Growth Team Lead (#100)
m52go
notifications at github.com
Sat Nov 20 00:46:53 CET 2021
## Cycle 30 Report
A [better DAO status page](https://bisq.network/dashboard/) was merged earlier this cycle. Page generation is automated, and all details are documented [here](https://github.com/bisq-network/bisq-website/tree/master/.dao).
Bitcoin Magazine began publishing their quarterly paper magazine again this month, and the first issue featured an in-depth look at El Salvador. The back cover features Bisq and Mempool. This back cover is the last remaining item of our conference deal with them.
[[source of images](https://twitter.com/nikcantmine/status/1458829757706084354)]
Otherwise I've become frustrated with the direction of the project. Bisq has largely saturated existing avenues of growth in its current form. It's a wonderful tool for power-users in USA and Europe. Beyond that, it's unlikely to gain significantly more traction, as it's cut off from millions in USA and Europe and billions in emerging markets.
The solution for this is to improve accessibility. The way to do this is to create additional interfaces (e.g. mobile and node-in-a-box availability like Umbrel) and enable integrations with other services (e.g. with other wallets, exchanges, etc).
These things can only happen with an API and a headless version of the core software that can run on a server and/or Raspberry Pi. While efforts to produce an API and daemon have been ongoing for years, and for the past several months in particular, I cannot promote what we have now. The [mobile app in progress right now](https://github.com/bisq-network/proposals/issues/342) promises to bring such functionality eventually, but when I asked if API and daemon completion could be delivered in parallel with the mobile app, no one could give a clear answer. This means the mobile app may never actually be capable of delivering growth.
I have met several projects and companies in my travels over the past several months who would love to integrate Bisq into their offerings and effectively extend Bisq's reach overnight, but the lack of software tools make these growth avenues impossible. Payment processors, exchanges, wallets, custody services, merchants...I've had preliminary conversations with many such people under the impression an API and/or Bisq 2.0 would be ready before 2021 ended, but the end of 2021 is almost here and all those people will be left hanging now.
What's left? Education and marketing can only do so much. New payment methods are mostly irrelevant if the target users cannot actually use Bisq in sufficient numbers (e.g. China and India). Altcoin trading isn't something most Bisq users care about. The core function of trading remains vulnerable to fee spikes, and a new protocol doesn't appear to be on the horizon.
In a nutshell, I don't see the project growing meaningfully (i.e. order-of-magnitude steps) without major changes. So I don't want to be held responsible for growth anymore. I have trimmed my other roles as well and generally expect to be less available across the project going forward.
@cbeams please unassign me from this role.
--
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/roles/issues/100#issuecomment-974543678
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20211119/29a6f1c9/attachment-0001.htm>
More information about the bisq-github
mailing list