-
Notifications
You must be signed in to change notification settings - Fork 16
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
Ops Team Lead #101
Comments
Initial ReportOps Project board: https://github.com/bisq-network/ops/projects/1 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:
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 bisq-network/proposals#198 and the project proposal will be forthcoming. |
Per @wiz's request, I've added @Emzy as an assignee to this role issue, indicating that he is the secondary owner, with @wiz remaining the primary owner. See the similar change made to the Support Team Lead role documented at #102 (comment). |
@wiz wrote:
Thanks, @wiz for all your efforts! And thanks, @Emzy for taking it on.
Done. Both @bisq-network/ops and @bisq-network/team-leads teams have been updated accordingly. |
Sad to see you leave the Ops Team role. |
Docs: https://bisq.wiki/Ops_Team
Teams: @bisq-network/ops, @bisq-network/team-leads
The text was updated successfully, but these errors were encountered: