Skip to content

Commit

Permalink
Update phase-zero.adoc to reflect bonding and spec changes
Browse files Browse the repository at this point in the history
  • Loading branch information
cbeams committed May 4, 2018
1 parent 6a07b71 commit 56ebd62
Showing 1 changed file with 2 additions and 9 deletions.
11 changes: 2 additions & 9 deletions dao/phase-zero.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -286,7 +286,7 @@ _Status:_ *pending.* See https://github.com/bisq-network/dao/issues/11 for detai

We enumerate and define the roles necessary to operate, maintain and administrate the Bisq project, Bisq network and Bisq DAO, such that responsibilities can be transferred from founders to other reputable contributors. Because each of these of these roles require a degree of trust, filling the role requires putting up a BSQ bond. Initially, founders will use their BSQ stake to bond into these roles, and will then transfer those roles to contributors who (a) wish to take the role over and (b) have earned sufficient BSQ to do so.

_Status:_ *work has been started* in the <<roles-repo>>, where each role has been enumerated in the form of a GitHub issue, but most roles do not yet have a _specification,_ i.e. a detailed description of the responsibilities required to fill that role. The Twitter operator role https://github.com/bisq-network/roles/issues/21[issue] and https://github.com/bisq-network/roles/blob/master/twitter-operator.adoc[specification] are an exception, and provide an early example of what's to come for the other roles.
_Status:_ *in progress.* Each role has been enumerated in the form of a GitHub issue in the <<roles-repo>>, and we continue to add to and modify these roles as appropriate. Bonding is not yet in place for any role.

=== Establish and refine the fair market value of the BSQ token

Expand All @@ -310,7 +310,7 @@ _Status:_ *ongoing.*

Initially, founders use their BSQ stake to assume all bonded contributor roles, reflecting the fact that they do already "have all the keys" and do already carry out most of these duties. As contributors earn sufficient BSQ for bonding, they can approach founders and request to take these roles over. Contributors have a twofold incentive to do so: (1) the BSQ they earn by carrying out the duties of the role, and (2) the interest they earn on their BSQ bond over time.

_Status:_ *in progress.* Initial bonding levels https://github.com/bisq-network/dao/issues/10[will be set], and founders and other contributors will be officially bonded into all roles by February 1st, 2017.
_Status:_ *in progress.* Founders _are_ distributing responsibility to contributors by having them take on bonded contributor roles, but bonding itself is not yet in place, and may not be until BSQ goes live. We are still sorting out exactly how to handle this during phase zero.

=== Grow exchange volume organically

Expand Down Expand Up @@ -535,11 +535,6 @@ To submit a compensation request, create a new issue in the <<compensation-repo>

See https://github.com/bisq-network/compensation/issues/2[bisq-network/compensation#2] for an example compensation request.

To submit a compensation request for a <<bonded-contributor-roles,bonded contributor role>>, the following prerequisites also apply:

- The role must have a complete and up to date https://github.com/bisq-network/roles[role specification] document
- The reporting requirements (if any) for the role must be fulfilled. Usually reporting happens in the form of a comment on the https://github.com/bisq-network/roles/issues[role's dedicated GitHub issue]. See your role specification for details.

Once submitted, your request will be added to the https://docs.google.com/spreadsheets/d/1xlXDswj3251BPCOcII-UyWlX7o7jMkfYBE-IZ5te5Ck/edit#gid=912569327[voting spreadsheet] where stakeholders can <<how-to-vote,vote>> on it.

=== submit a proposal
Expand Down Expand Up @@ -578,8 +573,6 @@ NOTE: It is important to vote "no" if you believe a request should not be approv

=== earn interest on my BSQ bond

=== propose changes to my role specification

=== transfer my role to the successor of my choosing

== As a maintainer, I can… [[maintainer-use-cases,maintainer use cases]]
Expand Down

0 comments on commit 56ebd62

Please sign in to comment.