[bisq-network/roles] Ops Team Lead (#101)

wiz notifications at github.com
Sun Aug 9 19:37:22 UTC 2020


## Initial Report

Since we restructured the DAO into teams and established the Ops Team a few months ago, we've been working on decentralizing all the critical Bisq infrastructure in order to remove our reliance on TTP and CPOF, as well as increasing performance and usability. So far the current progress is:

- [X] Decentralize the Bisq Explorer https://github.com/bisq-network/proposals/issues/143
- [X] Decentralize the Bisq Mempool Fee Estimation https://github.com/bisq-network/projects/issues/37
- [X] Decentralize the Bisq Pricenode data source https://github.com/bisq-network/projects/issues/35
- [ ] Decentralize the Bisq Markets API https://github.com/bisq-network/projects/issues/41
- [ ] Decentralize the Bisq Domain Names https://github.com/bisq-network/proposals/issues/211

After the decentralization efforts are completed and things are running smoothly, looking to the longer term the next priority for Ops team will likely be researching how to get Bisq working on a Bitcoin Sidechain like Liquid in the event that Bitcoin TX fees skyrocket and result in Bisq trades becoming priced out of Bitcoin Base Layer. This was proposed in https://github.com/bisq-network/proposals/issues/198 and the project proposal will be forthcoming.

-- 
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/101#issuecomment-671092461
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200809/423a5dfa/attachment.html>


More information about the bisq-github mailing list