bisq-network / roles

@bisq-network contributor roles

Bisq Network Roles

The issues in this repository track specific roles within the Bisq DAO, including who owns each role, and they provide a space for those role owners to write monthly reports in the form of comments on their respective issues.

Proposals for new roles go in the proposals repository. Please do not open a new issue for roles that haven’t been approved yet. If you’re assuming a role that was just approved, please reach out to the roles maintainer for advice on how to open the new role issue and establish pertinent documentation.

See https://docs.bisq.network/roles.html for complete documentation.

roles's Issues

Bisq P2P Maintainer

Docs:
Team: @bisq-network/p2p-maintainers
Primary owner: @ManfredKarrer

Markets Website+API Operator/Maintainer

This role is responsible for operating the https://markets.bisq.network website and API as well as maintaining its source in the https://github.com/bisq-network/markets repository.
Primary owner/maintainer: @wiz
Secondary owner/operator: @Emzy

Vimeo Admin

This role is responsible for Bisq's Vimeo channel at https://vimeo.com/getbitsquare.

Slack: n/a pending transition to #youtube see #56

Spec: n/a
Bond: n/a

Transifex Admin

See https://www.transifex.com/bisq/public/

Keybase: #transifex

Team: @bisq-network/transifex-admins
Primary: @MwithM
Secondary: @ripcurlx

DAO Maintainer

This role is responsible for maintaining the bisq-network/dao repository, which principally exists as a place to capture issues about the Bisq DAO itself, often dealing with high-level 'meta' issues that don't fit in any other specific repository, or dealing with DAO activities like monthly voting. The dao repository is also where we aggregate all our ZenHub boards. So (with the ZenHub browser extension installed), one can go to https://github.com/bisq-network/dao#boards and see "one board to rule them all"—where all other @bisq-network org repositories show up in the same place.

This role is not about maintaining BSQ validation logic, voting logic, or other DAO-related code that resides in the bisq-network/exchange repository. This is, for now, at least, still a function of the Exchange Maintainer role (#3).

L1 Support Agent

Docs: https://bisq.wiki/Support_Agent
Team: @bisq-network/l1-support-agents

Keybase Admin

Closed as superseded by #79.

Writer/Editor

BSQ record keeper

During phase zero of the DAO, we track BSQ stake, voting and bonding manually, via spreadsheet and other primitive mechanisms. This requires a trusted record keeper who is in control of these spreadsheets, etc.

This role will go away as we move DAO operations on-chain.

See https://github.com/bisq-network/docs/blob/master/dao/phase-zero.adoc#track-stake-voting-and-bonding-via-spreadsheet and the rest of the phase zero paper for further details.

Pricenode Maintainer

Docs:
Team: @bisq-network/pricenode-maintainers
Primary owner: @wiz

Exchange Maintainer

This role is responsible for maintaining (esp. merging PRs into) and releasing the Bisq exchange client repository at https://github.com/bisq-network/exchange.

Slack Admin

This role is responsible for owning (in Slack terminology) and administering Bisq's Slack workspace at https://bisq.slack.com.

• Slack: #slack-ops
• Issues: https://github.com/bisq-network/slack
• Invites: https://bisq.network/slack-invite

---

Docs: none, other than the above
Team: @bisq-network/slack-admins
Primary owner: @m52go

GitHub Admin

Docs: WIP at bisq-network/bisq-docs#64 (should move to https://bisq.wiki/GitHub_Admin)
Team: @bisq-network/github-admins

Note: @ripcurlx uses the Owner-privileged service account @bisq-github-admin-3 to perform GitHub administration duties.

Economic advisor

Seednode Maintainer

Docs:
Team: @bisq-network/seednode-maintainers
Primary owner: @freimair
Secondary owner: @wiz

BSQ Explorer Operator

This role is responsible for operating an instance of the BSQ explorer webapp. See also the BSQ Explorer Maintainer role at #103.

Docs: TBD
Team: @bisq-network/bsq-explorer-operators

Instances and their operators:

• bsq.ninja (@wiz)
• bsq.sqrrm.net (@sqrrm)
• bsq.bisq.services (@devinbileck)
• bsq.vante.me (@mrosseel)
• bsq.emzy.de (@Emzy)
• bsq.bisq.cc (@m52go)

Forum Operator

This role is about operating and administering the Discourse forum at https://bisq.community.

Spec: https://github.com/bisq-network/roles/blob/master/forum-operator.adoc

Bisq Docs Maintainer

This role is responsible for maintaining the bisq-network/bisq-docs repository, which backs the https://docs.bisq.network site.

---

Docs: none, other than the above
Team: @bisq-network/docs-maintainers
Primary owner: @m52go

Establish README.adoc for repository guidance

README: https://github.com/bisq-network/roles/blob/master/README.adoc

The README.adoc should help navigating through the repository, give an overview over all the bonded roles within the dao and guide the process of role creation. Furthermore it will help facilitate the process of compensation.

Founder

Docs: none
Team: @bisq-network/founders

Reddit Moderator

This role is about being a moderator for the r/Bisq subreddit.

---

Docs: none, other than the above
Team: @bisq-network/reddit-moderators
Primary owner: @alexej996

YouTube Admin

This role is responsible for managing the Bisq YouTube channel where folks can follow demo videos, talks, interviews, etc.

Slack: #youtube
Issues: https://github.com/bisq-network/youtube

---

Docs: none, other than the above
Team: @bisq-network/youtube-admins
Primary owner: @m52go
Secondary owner: @flix1

@ripcurlx and @flix1 have "Manager" rights
@ManfredKarrer and @cbeams have "Owner" rights (over the larger "Google Brand" account)

Analytics Maintainer

Spec: https://github.com/bisq-network/roles/blob/master/data-analyst.adoc

Bitcointalk Moderator

This role is about keeping the Bisq thread on the Bitcointalk forum up-to-date.

---

Docs: none, other than the above
Team: @bisq-network/bitcointalk-moderators
Primary owner: @flix1
Secondary owner: @alexej996

MailChimp Admin

This role is responsible for every aspect of the Bisq Newsletter, including crafting its content, determining its frequency of publication, and owning and administering its Mailchimp account.

The Bisq Newsletter currently has 2,500+ subscribers, but we don't send news out very often simply because of resource constraints.

Bitcoin Node Operator

The idea here is that a number of Bisq contributors take on this role, run a full node and publicly attest that their full node will run the latest major version of Bitcoin Core. Doing this provides a service to Bisq users who want to ensure they're on the correct chain during contentious forks like that posed by the forthcoming SegWit2X project.

See https://lists.bisq.network/pipermail/bisq-contrib/2017-November/000006.html for further details and links.

operator	clearnet IP:port	clearnet name	onion address
@ManfredKarrer	159.89.16.222	btc1.0-2-1.net	r3dsojfhwcm7x7p6.onion
@ManfredKarrer	165.227.34.56	btc2.0-2-1.net	vlf5i3grro3wux24.onion
@ManfredKarrer	165.227.44.202	btc3.0-2-1.net	i3a5xtzfm4xwtybd.onion
@Emzy	78.47.61.83	kirsche.emzy.de	fz6nsij6jiyuwlsc.onion
@Emzy	62.75.210.81	node2.emzy.de	c6ac4jdfyeiakex2.onion:8333
@Emzy	163.172.171.119	node1.emzy.de	sjyzmwwu6diiit3r.onion:8333
@Emzy	n/a	n/a	poyvpdt762gllauu.onion:8333
@ripcurlx	174.138.35.229:8333	btc.christophatteneder.com	lgkvbvro67jomosw.onion
@mrosseel	138.68.117.247:8333	btc.vante.me	4jyh6llqj264oggs.onion
@mrosseel	67.207.75.7	btc2.vante.me	mxdtrjhe2yfsx3pg.onion
@sqrrm	185.25.48.184	btc4.0-2-1.net	3r44ddzjitznyahw.onion:8333
@sgeisler	5.189.166.193:8333	bcwat.ch	z33nukt7ngik3cpe.onion
@jhoenicke	88.198.39.205:8333	btc.jochen-hoenicke.de	sslnjjhnmwllysv4.onion:8333
@tbocek	192.41.136.217:8333	bitcoin4-fullnode.csg.uzh.ch	n/a

Seednode Operator

This role is responsible for operating one or more Bisq seednodes.

See: btc_mainnet.seednodes

---

Docs: none, other than the above
Team: @bisq-network/seednode-operators

Growth Maintainer

Team: @bisq-network/growth-maintainers
Primary owner: @m52go
Secondary owner: @ripcurlx

Spec: https://github.com/bisq-network/roles/blob/master/growth-maintainer.adoc

Twitter Admin

This role is responsible for managing all aspects of the https://twitter.com/bisq_network Twitter handle.

---

Docs: https://github.com/bisq-network/roles/blob/master/twitter-admin.adoc (should be reworked per instructions in Roles doc.
Team: @bisq-network/twitter-admins
Primary owner: @m52go

Complete roles-maintainer.adoc

Spec: https://github.com/bisq-network/roles/blob/master/roles-maintainer.adoc

Arbitrator (legacy 2-of-3 model)

This role is responsible for arbitrating Bisq exchange trade disputes.

See:

• The Arbitration section of the original Bisq whitepaper
• The dedicated Arbitration System doc

Facebook Admin

This role is responsible for the Bisq Facebook page at https://facebook.com/bisqnetwork.

Proposals Maintainer

Docs: https://docs.bisq.network/proposals.html#maintainer
Team: @bisq-network/proposals-maintainers

Website Operator/Maintainer

This role is responsible for the Bisq website at https://bisq.network, including maintaining its source in the https://github.com/bisq-network/website repository and its operation / hosting on Netlify's static site hosting infrastructure.

---

Docs: none, other than the above
Team: @bisq-network/website-maintainers
Primary owner: @m52go

Add "role specification" as requirement for bonded roles in phase-zero.adoc

phase-zero.adoc: https://github.com/bisq-network/docs/blob/master/dao/phase-zero.adoc

In order to ensure the role specification completion of all assigned roles I will add it as a requirement in the phase zero document.

Ambassador

This role is responsible for representing Bisq online and in the physical world whenever and wherever it is useful to do so. Ambassador work ranges from answering questions about Bisq on Reddit to giving talks about Bisq at conferences and anything in between.

This is ideally a role that will be filled by many people, not just one or two, but we'll get there over time. Note that certain extra-important outreach channels like Twitter have their own infrastructure and dedicated roles—see #21 for an example of that.

Slack: #ambassadors

---

Docs: none, other than above
Team: none, role is open to all
Primary owner: none, see #35 (comment)

Bisq Maintainer

Docs: https://bisq.wiki/Bisq_Maintainer
Team: @bisq-network/bisq-maintainers

Statsnode Maintainer

Docs: none
Team: @bisq-network/statsnode-maintainers
Primary owner: @ManfredKarrer

I dropped that role as it can be seen as part of the general code base.

Telegram Admin

Mailman Operator

This role is about operating our Mailman / Pipermail-based mailing lists at https://lists.bisq.network up and running. It also encompasses normal Admin activities for this resource.

Spec: https://github.com/bisq-network/roles/blob/master/mailman-operator.adoc

Pricenode Operator

Docs: https://bisq.wiki/Pricenode_Operator
Team: @bisq-network/pricenode-operators

Bisq Bitcoinj Fork Maintainer

This role is responsible for maintaining Bisq's fork of bitcoinj at https://github.com/bisq-network/bitcoinj. This includes but is not limited to doing big, valuable work like implementing Bisq's needs around SegWit and integrating that support into Bisq (see bisq-network/bisq#1139).

This role is (or at least can be) more than narrowly bitcoinj-specific: we need one or more contributors to can stay on top of all Bisq's Bitcoin needs, to stay abreast of what's happening at the protocol level, to get proactive about things.

Note that Bisq also maintains a federation of Bitcoin Core nodes as a service to its users for the purpose of mitigating privacy risk caused by bitcoinj's approach to bloom filter-based SPV. The contributor playing this role could also become one of the @bisq-network/btcnode-maintainers (see #66) and help tune settings for all the nodes in our federation, maintain common bitcoin.conf files for the set of @bisq-network/btcnode-operators (#67) that run them, etc.

---

Docs: none, other than the above
Team: @bisq-network/core-maintainers
Primary owner: @oscarguindzberg

Director of decentralization

Roles Maintainer

Docs: https://docs.bisq.network/roles.html#roles-maintainer-role
Team: @bisq-network/roles-maintainers

Freenode IRC Admin

This role is responsible for administering the #bisq and (legacy) #bitsquare Freenode IRC channels, as well as the #chat-bridge bot / channel in Slack. Owners of this role have op (operator) status in Freenode IRC terminology.

---

Docs: none, other than the above
Team: @bisq-network/irc-admins
Primary owner: @mrosseel

Compensation Maintainer

In lieu of a proper spec, here are the basic requirements for this role:

1. Maintain the bisq-network/compensation repository, which mainly consists of compensation request issues
2. Conduct monthly compensation request voting, including emails to bisq-contrib list
3. Maintain the BSQ stake and vote tracking spreadsheet

See also: https://github.com/bisq-network/docs/blob/master/dao/phase-zero.adoc#track-stake-voting-and-bonding-via-spreadsheet

---

Docs: none, other than the above and a WIP PR
Team: @bisq-network/compensation-maintainers
Primary owner: @ripcurlx
Team: @bisq-network/compensation-maintainers

DNS Admin

This role is responsible for administering DNS for the bisq.network and bisq.io domain names via Cloudflare. This role does not include administering and renewing domain name registrations at Namecheap; this is the job of the Domain Name Owner role (#77). Other bisq-related domains such as bisq.wiki and bisq.community are independently managed.

---

Docs: none, other than the above
Team: @bisq-network/dns-admins

Payment Method Maintainer

Docs:
Team: @bisq-network/payment-method-maintainers
Primary owner: @pazza83

---

This role is responsible for the vetting new payment methods in Bisq, as well as maintaining existing ones and monitoring their performance. This is not a technical maintainer role, i.e. it is not about development, but rather about managing the process around payment methods.

Tasks

• Monthly reporting on payment method volume and health
• Monthly reporting on role issues
• Payment methods prioritization
• Payment methods requirements verification and required fields description
• Maintain payment methods roadmap
• Develop payment method addition process

Goals

• Proactively find payment methods to support Bisq's growth in coordination with growth experiments
• Support to proposed payment methods addition
• Develop payment methods maintainer role

KPIs

• % of transaction problems related to payment methods
• % of market share represented by supported payment methods (TBD)
• % arbitration requests / payment method, speed, etc.

Slack: #payment-methods
Issues: https://github.com/bisq-network/bisq-desktop label-> in:payment-methods

Monitoring Operator/Maintainer

This role is responsible for operating @bisq-network monitoring infrastructure and for maintaining any related sources and issues in the https://github.com/bisq-network/monitoring repository.

Team: @bisq-network/monitoring-operators
Docs: https://github.com/bisq-network/bisq/blob/master/monitor/README.md

Travis CI operator