Snapshot Vote: 01/10/2021
1.0 - Summary:
The proposal set forth here will define an organisational structure for the BBH. Designed with inspiration from the Index Coop, a proven and tested method of decentralised governance. This proposal will define the parameters for different working interest groups and their powers in relation to the BBH community and its resources.
2.0 - Abstract:
The proposed change is to introduce titles for new working groups and broadly define their powers and responsibilities within the BBH community. If implemented, this proposal will lead to the creation of an official hierarchy, providing Bears with the structure and process they need to push forward their ideas. The proposed hierarchy is represented in this rudimentary figure below:
(if somebody with artistic skills and time could produce a high-quality illustrated version of this, that would be a fantastic resource for BBH marketing)
3.0 - Motivation:
As a community we have been bursting out with valuable and credible ideas that have the potential to further the BBH DAO. Unfortunately, it is rare that these ideas are followed through with. A large reason for this is that motivated community members lack the guidance and defined processes and procedures necessary to make their voices and ideas heard. This diminishes the effectiveness of the DAO and impedes upon our ability to accomplish community goals.
4.0 - Specification Overview:
What it is that the proposal will do to solve the problem will be detailed in this section.
4.1 – Groups & Roles:
This is where the proposed working groups are defined and labelled.
[Click on the drop down for more details on Groups & Roles]
Nests & Drone Bees:
A completely free and independent group of motivated individuals called Nests. Individual members can form Nests to work on anything they believe will further the interests of the community. The fundamental differentiation here from Hives is that Nests are NOT endorsed by the Colony. Meaning there will be no funds or resources granted to these groups unless or until they become Hives.
Hives & Worker Bees:
This group will be fundamental to driving some of the most important community initiatives such as marketing and investments. Hives can only be formed by explicit consent from the Colony. This is done by making a very well-constructed proposal to the community. When a Hive is formed it is on a quarterly probation period. The Colony decides at the end of this period if it is worthy of continuing via a fresh community vote.
As we are a decentralised community, and our goal is to become increasingly decentralised, it is important that this role is defined. The Colony is the community at large, each one of you comes together to form the BBH Colony. The Colony and its members act as the gatekeepers. They protect the HoneyPot and BBH resources from nefarious, ill-considered, or simply clumsy initiatives.
Powers and resources granted to Hives can ONLY be granted by the Colony. Meaning the location of power remains decentralised.
4.2 – Responsibilities:
In this section, the minimum requirements from newly formed groups are detailed. Please note that these will be non-negotiable requirements. All groups/roles will be required to operate in accordance with one simple principle:
Growth & Improvement: Whatever the goals are for your group, they must be designed to further the financial, strategic, or social interests of the BBH community and its members.
[Click on the drop down for more details on Responsibilities]
Nests don’t have many responsibilities. This is the benefit that is derived from being unendorsed. If you have an idea that you think could work, have at it. Form a Nest of people who are interested in progressing your idea and work together to achieve them. You are still entitled to retroactive remuneration as detailed in section 4.4. If the time comes that your Nest feels in need of community resources, make a proposal to become a Hive. The Colony will decide if your group is viable.
The objectives of Nests should be defined at the outset.
Must not conduct themselves in a way that would harm the reputation of the BBH.
This is where responsibility becomes much more important. Hives will be formed with the intention of utilising HoneyPot funds and BBH resources to achieve important goals. Therefore, they are answerable to the community.
Key performance indicators (KPIs): These must be determined within the initial proposal. The Colony will then measure the Hives performance over their first quarter against those KPIs. Using this information, the Colony votes to continue or end the group.
Objectives: The goals and objectives of Hives must be very clearly defined within the initial proposal.
Size: A Hive must consist of at least three members to ensure that checks and balances exist to protect the community interest.
Conflicting Interest: Hives must be careful to ensure their goals are not conflicting with the goals of other existing hives.
Funding: The expected costs and funding required must be carefully considered and included in the proposal. The community would decide based on the quality of your proposal if the amount specified is justified.
MultiSig: For a Hive group to function and steward the BBH community funds, it is an essential requirement at the proposal phase for members to create and evidence a multi-signatory wallet on Gnosis Safe. It is crucial that spending of community funds is mutually agreed between the Hive members.
Reputation: Members of Hives must also refrain from conducting themselves in a manner that would damage the reputation of the BBH.
Imposing requirements on the community seems ridiculous because you’re all Chads with alpha brains. There should however be a few moral requirements that protect the wider interests of the community:
Solicitation of Votes: There should be absolutely no efforts to pay or court any individual within the community to vote in your own interest or the interests of others. Votes should remain the result of an individual’s thoughts.
Fracturing: All efforts should be made to maintain the integrity of our community. If a significant rift should form between different interest groups, there should be a concerted community effort to bring those groups back together around shared ideals [a community code or goals should maybe form another proposal].
4.3 - Limits & Power:
The powers and the limits of those powers granted to Hives must be adequately defined within the initial proposal. Any plans to significantly alter or expand these powers must be done so following a community approval vote. Failure to do so may result in the immediate disbanding of said group following a community vote.
Additionally, the Colony retains the right to end any working group at any time following the success of a community vote, irrespective of circumstances.
4.4 - Remuneration:
All members that form a Hive are entitled to retroactive remuneration for their work and services to the BBH community. Detailed logs should be taken for time worked and the details of the work they have done. This work will be assessed for its impact to the BBH and appropriate remuneration will be distributed based upon that assessment.
At present remuneration is handled by the Motherland (founding team). In the future however as we develop we would look to establish a remuneration hive that handles these claims and sets the framework for remuneration. If you believe you are suitable for this role, the team are always looking for trustworthy and competent members to hand over responsibility to.
5.0 - Rationale:
The proposal has been made in this way because as a DAO we must protect ourselves from irresponsible use of community resources. After much consideration and discussion between the proposal team and even further conversation with our defi experts; we decided that a tiered group system enabling less restrictive oversight, but greater resource protection would be the ideal structure. This method would encourage more considered proposals that wish to utilise our resources but should also prevent voter fatigue from incessant, half-baked proposals.
Initially our proposal was a much more rigid structure with a single working group (a committee). It was designed to establish rules for the formation of committees and their election processes. Due to the reasons discussed above, it was decided this wouldn’t be an effective long-term solution.
6.0 - Technical Specification:
Technical changes resulting from this proposal should involve:
Codifying the new structure and proposed governance of said structure within official BBH documents found here: https://docs.buzzedbearhideout.com/.
Newly formed working groups should be assigned groups on the BBH forum.
A Discord channel that allows community members to seek out others for the formation of Nests & Hives.
7.0 - Test Cases:
A similar model of decentralised governance has been successfully tested and implemented at the Index Coop. A successful FTSE 500 organisation.
8.0 - Copyright:
Copyright and related rights waived via CC0.