Superfluid

Raid Guild

Hats Protocol 🧢

RaidGuild is innovating on role-based compensation through the integration of Hats and /superfluid streams, establishing transparent accountability for key roles

Here's how they did it

A /raidguild + /hatsprotocol case study...

1/8

The Organizational Graph Protocol. Encode your organization's roles, agents, and permissions into a programmable graph with Hats Protocol.

Today, RaidGuild uses both Hats Protocol and CharacterSheets (a gamification layer on top of Hats, built by RaidGuild) to harden core roles and "departments" in the guild, and clarify expertise

3/8

As an example, Hats has enabled RaidGuild to set up 
Superfluid payment streams to people in key positions, which the DAO has historically been against doing due to a lack of clarity in the role.

4/8

The hat wearer now knows more precisely what their job is, what their pay is, and when their term is up. At the end of each quarter, the hat wearers are assessed and re-elected if the job is done well.

5/8

CharacterSheets by /raidguild (think of a DnD character sheet) logs member activity on-chain & expresses it visually in the form of classes, XP, levels & items

Under the hood, the permission structure is powered by Hats 🧢

6/8

While Hats brings clarity and accountability to roles within the guild, it also has the extensibility to allow something like CharacterSheets to make the structure fun and gamified

7/8

Hats x RaidGuild = role-based compensation and accountabilities to coordinate and get things done

See the full case study here:

Hats x RaidGuild = role-based compensation and accountabilities to coordinate and get things done

See the full case study here: https://www.hatsprotocol.xyz/wearer/raidguild-case-study

And get in touch if you want to apply this use-case to your own organization:

And get in touch if you want to apply this use-case to your own organization: https://hatsprotocol.deform.cc/getintouch/

Primarily organized through Moloch DAO smart contracts and a Discord server, @raidguild has reached a level of complexity where these tools alone no longer suffice in understanding who is responsible and qualified to hold different roles and permissions.

Enter Hats...

2/8