Skip to main content

DAO Roles empowered with Hats

In order to make operations more efficient and reduce the coordination needed at the share holder level, we've elected to create some discreet roles and give them budgets and other decision-making authorities during their appointment.

These roles are generally appointed by motivated individuals but elections can be facilitated if there are multiple Raiders interested in a role for the same term. These roles are created and appointed by the full community and can be removed/unwound in a similar fashion. We're continuing to use other good principal-agent hygiene by using quarterly budgets or streams in longer cases. Streams can be canceled with a proposal since the funds are flowing from the DAO itself.

The roles here are powered by Hats Protocol. Skip to the RG Hats Tree section to learn more about RaidGuild Hats Tree and proposing a role.

Current Roles​

loosely ordered by permanence/value shown so far

tip

Create a new Role via a proposal, read more about Proposing a Role.

Ganggang - Quality assurance delegates​

The Ganggang role acts as a trusted delegate for the DAO and while they can provide several interim functionalities for interacting with the outside world, the primary function is being the releaser for escrowed Raid Guild Improvement Proposals (RIPs). Currently the process is largely manual, but RIP members should request release of milestones from the #Ganggang thread or #ops channel in Discord, please tag the @Ganggang role also.

The Ganggang safe lives at 0xCFFF4a6EB44bA088EEa89A84Dd113eCfDEDA9641 on several chains, however, only on Gnosis is it a Hat-gated Safe. The others will use a bridge module to be controlled from Gnosis.

The Ganggang role is executing 1-2 transactions per month and is currently an unpaid role. This role is effectively perpetual since the expectations are fairly minimal and members can renounce if they are looking to become inactive.

There are a couple of temporary budgets also being escrowed by Ganggang

Claiming the Ganggang role​

The Ganggang role requires holding two other roles in order to claim:

Currently the Ganggang multisig (Safe) authority exists as a 3/7, so up to 7 Guild Members can hold the Ganggang role at one time and it will require 3 to confirm a transaction. If a member needs to be rotated we can raise a proposal to transfer the role from an existing holder(s) to the new appointee(s). A member of Ganggang can also renounce their role (and signing authority) at any time, if needed.

Infrastructure Maestro - Holders of the devops keys​

The Infrastructure Maestro(s) are responsible for making sure the infrastructure accounts are secured and pipelines are deploying when other members push updates. Since these SaaS services tend to charge per seat, we've elected to consolidate these permissions to a couple of representatives acting as backups for each other.

The Infrastructure Maestro (IM) role also has its own multisig (Safe) for receiving ongoing resources for these SaaS services that keep the Guild running. There is an active stream running from the Guild to the IM Safe and this stream can be deactivated at any time with a proposal from the Guild. The Safe is configured as a 1/1 with either of the current wearers able to claim the signing authority.

Current services handled by Infrastructure Maestro:

If you need to deploy new infra, reach out to one of the IM for updating.

Latest budget

~2k per year

Claiming the Infrastructure Maestro role​

The Infrastructure Maestro role requires holding two other roles in order to claim:

  1. RaidGuild Member
  2. Healer (Operations)
  3. Claim the Infrastructure Maestro role and associated Safe signing authority

Brand Steward - Unifying our shared aesthetic and persona​

The Brand Steward is responsible for providing a cohesive brand across the feel & aesthetic of the Guild's digital domains. Several resources are offered to provide guidance to Guild members applying the brand to their project or implementation.

The Brand Steward requests a regular budget where needed to ensure the project and maintenance are advanced. The Steward will document goals for the current budget and provide regular updates throughout the duration of the epoch.

Latest budget

~6k per year

It's expected that a majority of the budget is allocated to completing the actual execution/implementation tasks. Roughly, up to a third of the budget should be used for Steward coordination responsibilities and planning.

Claiming the Brand Steward role​

To claim the Brand Steward role a member will need to claim two other roles:

  1. RaidGuild Member
  2. Archer (Design)
  3. The Brand Steward role is appointed by the Ganggang role via offchain consensus
    • Claim the Brand Steward role

Handbook Steward - Keeping our knowledge maintained​

The Handbook Steward is responsible for budgeting and directing maintenance of this Handbook. The main resources for the Steward are the Handbook repo and the #handbook Discord channel.

The Handbook Steward requests a regular budget where needed to ensure the project and maintenance are advanced. The Steward will document goals for the current budget and provide regular updates throughout the duration of the epoch.

Latest budget

~6k per year

It's expected that a majority of the budget is allocated to completing the actual execution/implementation tasks. Roughly, up to a third of the budget should be used for Steward coordination responsibilities and planning.

Claiming the Handbook Steward role​

To claim the Handbook Steward role a member will need to claim two other roles:

  1. RaidGuild Member
  2. Scribe (Content)
  3. The Handbook Steward role is appointed by Ganggang via offchain consensus
  4. Claim the Handbook Steward role

Sync Guild - Coordinating the synchronous layer​

The Sync Guild is responsible for coordinating the Guild's synchronous meetings so they are efficient and useful to members and attendees. As a part of the Sync Guild there are 3 roles activated to spread the burden for this role across a small group.

Sync Guild Roles

  • Sync Steward - Sync Steward coordinates with other members of the Sync Guild and wider Guild to make sure topics to be discussed are relevant. They also encourage members to pick up the other roles for meetings in which they'll be in attendance.
  • Jester - Sync Jesters are responsible for emceeing the synchronous gatherings. They can leverage known topics and field topics that are relevant to current goals of the Guild.
  • Scribe - Sync Scribes are responsible for recording meeting notes and sharing insights with the wider Guild

Sync Steward​

The Sync Steward is responsible for coordinating with other members of the Sync Guild and wider Guild to make sure topics to be discussed are relevant. They also encourage members to pick up the other roles for meetings in which they'll be in attendance.

The Steward requests a regular budget where needed to ensure the members are incentivized to participate. The Steward will document goals for the current budget and provide regular updates throughout the duration of the epoch.

Latest budget

~3k per quarter

It's expected that a majority of the budget is allocated to completing the actual execution/implementation tasks. Roughly, up to a third of the budget should be used for Steward coordination responsibilities and planning.

Claiming a Sync Guild role​

To claim a Sync Guild role a member will need to claim two other roles:

  1. RaidGuild Member
  2. Tavern Keeper (Community)
  3. The Sync Steward role is appointed by the Ganggang role via offchain consensus
    • Claim the Sync Steward role
  4. The Jester and Scribe roles are appointed by the Sync Steward role via offchain consensus
    • Claim the Jester or Scribe role

Roles Chart (Hats Tree)​

app.hatsprotocol.xyz/trees/100/92

RaidGuild Hats Tree

Overview​

Top (Root) Hat​

The top (root) hat is the parent of all the other hats. It is held by the DAO itself and can manage all the other hats via DAO proposal.

Auto Admin​

The Autonomous Admin hat is a helper hat that allows members to claim hats where they are eligible rather than require them being assigned directly. This is a contract that has the limited ability to assign hats to members.

RaidGuild Member​

The RaidGuild Member role is the foundation of all the roles that are part of the Guild. It is a requirement to claim most other roles. It can be claimed by having at least 100 DAO voting shares.

Proposing a Role​

To propose a new role, head over to the Hats App and view the RaidGuild Hats Tree.

  1. Switch to Edit Mode in the top left corner
  2. Find the role that will be the parent of the new role
  3. From the parent role, click the + button to create a new child role
  4. Complete the new role details and Return to the roles list
  5. You're now ready to deploy the changes for this new role
    • Since you likely aren't a wearer of the parent role, you'll need to make a proposal to deploy the changes
    • If you are a wearer of the parent role, you hit the deploy button to deploy the changes directly
  6. Get the necessary data for the proposal
    • Open the Transaction Call data section of the roles list
    • Copy the Hats contract address and use as the target of the transaction for this proposal
    • Copy the Hats transaction calldata and use as the calldata of the transaction for this proposal
  7. Submit the proposal