At Hats, we love organizations. And we have an idea for what’s coming next.
It all starts with the organizational graph.
Check out our new vision post below ↓
Put on your party hats... Hats Protocol and the Hats App v2 are now live & ready to use! 🥳
Give revocable roles and authorities to your people and code, save time, and get things done.
What makes Hats the ultimate coordination tool? ohhh baby, here we go...
1/15
Introducing
HATS PROTOCOL 🧢🎩👒
A new protocol for flexible & composable DAO-native roles ("hats") represented as NFTs
Using Hats, DAOs can:
- delegate & revoke authorities
- hold contributors accountable
- create role legibility
Today we are launching Hats Modules!
This is the most impactful release we've shipped since the protocol itself, and it's already catalyzing a new era for programmable organizations
Here's why:
TODAY IS THE DAY — Hats protoDAO has launched! 💥
This is a major step in our commitment to decentralizing the governance & operations of Hats Protocol 🌀
A short 🧵👇
- what the protoDAO is all about 🌿
- how to join the community and get involved 🧢
1/9
Beyond immutable & persistent code, we are committed to imbuing decentralization into our governance and operations to extend those benefits to the human dimension of our ecosystem.
To that end, Hats protoDAO will be launching this Thursday Sept 21 -- stay tuned 👀
7/10
DAO governance is getting in the way of DAO effectiveness.
How can DAOs get things done with the same (or better) level of effectiveness as tradOrgs, while maintaining their core values of decentralization & individual autonomy?
By bringing your roles onchain.
A short 🧵...
The dream of composability is alive inside Hats protoDAO!
There are so many incredible composable tools for collectively managing an organization
And Hats is what ties it all together 🧢
Here are the ones we're already using:
🧵👇
Hats are roles. When roles are linked together they create structures that you can use to supercharge your organization
This unlocks a whole new design space:
FORKABLE HATS TEMPLATES! 🧢
Here are 4 Hats templates you can fork today from groups like
@cabin
.city &
@ATXDAO
:
1/6
It's hattening — the first ever Hats Protocol Demo Day!
Join us to check out the future of onchain organizing, presented by a diverse set of orgs using Hats in innovative ways.
Demos include:
Sneak peek: Hat Tree Visualization
This is the one thing the Hats community has been raving about. Seeing the structure of delegation in your DAO is a huge unlock.
It's a major takeaway from our friends at
@Coordinape
— the power of giving the DAO a mirror to see itself 🪞
We believe that DAOs can get things done at scale without resorting to the hierarchical power structures of traditional organizations.
This is why we’re building Hats.
Imagine...
You can even hold a
@jokerace_xyz
that automatically gives the winners special authorities like multisig signing, voting rights & more
Once the election term ends, or if the winners become losers, the hat & its associated authorities are *automatically* revoked
8/15
If we are to truly realize the potential of DAOs, we need to empower the people who make them go.
Working with dozens of DAOs has revealed there are three things your contributors absolutely need in order to do great work:
Context
Authority
Accountability
A 🧵 (link inside)...
SO MUCH MORE
9. EOA wallet ownership (yes, hat-controlled wallets)
10. many more web2 permissions via
@LitProtocol
11-100. literally anything that's token-gateable
ahhhhhhh we're composinggggg
7/15
This is why Hats composes w/
@tallyxyz
Governor,
@DAOhaus
Moloch v3 &
@AragonProject
to enable DAOs to delegate revocable roles to people & groups
Hierarchy is no longer the enemy when the top of the hierarchy is the DAO itself
12/15
When roles are clear:
- work is no longer chaotic
- ppl know who to turn to for critical info
- ppl are empowered to make decisions and take action
- ppl can be held accountable!
Good news! Hats is easy to use, & it composes w/ all the DAO tools you already know and love:
3/15
WHY HATS
Hats are roles & roles are how people coordinate to get things done
Why are so many DAOs so chaotic? There are no roles! No roles = no structure = no accountability. The tyranny of structurelessness wins again...
It doesn't have to be like that.
2/15
DECISION MAKING
2.
@SnapshotLabs
proposal creation & voting
3.
@delv_tech
council voting authority
4.
@coordinape
circle access
Ensure only the right people can vote and dynamically tie voting eligibility to other conditions
5/15
Orgs can be decentralized AND have the structures and accountabilities they need to get things done
Hats enables orgs to create CAPTURE-RESISTANT structures to get shit done (safely)
11/15
HOW TO BRING YOUR ROLES ONCHAIN
Step 1. Create roles 🧢
Step 2. Connect power to roles ⚡️
Step 3. Customize logic for how the role will be issued, revoked & deactivated 🤝
Step 4. Mint hat tokens to any Ethereum or L2 addresses: EOAs, Safes, DAOs & smart contracts 🤠
10/15
HOW HATS WORKS
Role-based governance is the future, and Hats bundles all the things roles need: responsibility, authority, accountability
How does Hats empower orgs to ensure the right ppl & addresses always have the right permissions?
4 steps. It's really quite simple.
9/15
CONTROL RESOURCES
With Hats you can give contributors all kinds of different revocable (!) onchain & offchain permissions, including:
1.
@safe
multisig signing
delegate & revoke multisig signing authority based on specific eligibility criteria (eg
@jokerace
winners)
4/15
Hats Protocol is committed to open source, decentralization & composability
We value each of these in their own right, but more importantly, the combination of these tenets is critical to the long-term success of Hats
The Hats Protocol ethos, a 🧵
1/10
Role-bound, not soul-bound.
Separating roles from souls allows the collective to effectively coordinate the work without having power over its members.
Do you ever find yourself
- manually managing your community,
- tracking permissions,
- onboarding/offboarding members,
- logging addresses in spreadsheets…?
You can Hats that
Thinking about building something with Hats?
Yesterday's Hats Modules launch makes it 10x faster and easier to ship something of value and get it in front of users
Here's how it works👇
Today we are launching Hats Modules!
This is the most impactful release we've shipped since the protocol itself, and it's already catalyzing a new era for programmable organizations
Here's why:
If you're inspired by Hats, please like & retweet this thread to help us get the word out. We love our hatvocates!
And give us a follow to stay tuned for the launch of the Hats protoDAO in t-minus 1 month... 👀
Hold on to your hats, lots more to come...
Put on your party hats... Hats Protocol and the Hats App v2 are now live & ready to use! 🥳
Give revocable roles and authorities to your people and code, save time, and get things done.
What makes Hats the ultimate coordination tool? ohhh baby, here we go...
1/15
Or you can use Hats directly via the app -- Hats is permissionless and open-source!
Use Hats at
See the new website at
Visit our docs and guides at
And get in touch if you need help getting started
14/15
Interested in trying Hats?
Get a free consultation with one of the founders here:
Hats is currently deployed to Ethereum,
@arbitrum
@gnosischain
@optimismFND
@0xPolygon
and Goerli, and will be wherever DAOs are
13/15
“Hats Protocol is going to be one of the key components of NFT governance … and involves the attribution of roles within DAOs via NFT ‘hats’. It is very early in the conceptualization phase of its development, but the ideas and design are truly innovative.”
💖
Here’s my write up of DAO Camp.
An incredible experience, with incredible people, at the cutting edge of the most important technological design space going.
This was the DAO coming of age moment. The next bull run has started you just can’t see it yet.
ATX DAO is using Hats to enable members to permissionlessly level up and claim new roles & authorities as they accrue reputation (REP) in the community
Tip of the hat to
@ATXDAO
for "enabling the autonomy of their members through automated transparent systems rather than…
The Reputation & Roles System Proposal has passed with a staggering 96% yes votes! This officially marks the beginning for a way to track trust and assign authorities/responsibilities in new and exciting decentralized and permissionless ways! Check out the proposal here:…
3 common ways people are using Hats:
1. ELECTIONS: automatically grant permissions based on election results
2. ORG-CONTROLLED MULTISIGS: delegate & revoke signing authority
3. COMMUNITY MANAGEMENT: automate onboarding, offboarding, & cross-platform permissioning
All forkable
So excited by the potential of Hats templates
I think of them as *structure legos*
For the first time, we'll be able to directly fork the best structures of the top orgs
eg:
- the top grants programs
- the best delegate structures
- effective arbitration systems
all forkable
Hold on to your hats... we're seeking contributors to build the new standard for DAO roles!
In particular:
- UI/UX design,
- front-end dev,
- protocol eng,
- subgraph dev,
- branding & memelording
This you? Connect with us here to get involved:
Hats Modules tl;dr
🧢 Modules are programmable extensions for roles
⚡ Automate granting and revocation of roles and permissions based on specific conditions
🦾 Discover open-source modules or create your own!
🌀 Available in any app via the Modules Registry and SDK
Looking forward to this public deep dive tomorrow with
@DrNickA
of
@FactDAO
!
@DrNickA
is one of the best thinkers in the space, so we're keen to see what it looks like for him to be "thinking in hats" 🤠
Spaces link below 👇
Voting is now open!
We'd love to see a
@hatsprotocol
<>
@AragonProject
integration 🔥
Why? To "increase execution speed & give teams operational autonomy while token holders preserve the ultimate control"
Anyone who's participated in an Aragon app proposal is eligible to vote
Even as the project has grown, we are still spending 25-30% of our time on *calls* with users
Our new docs are great! But if you get stuck on something:
— which roles to create
— integration with existing contracts / front-ends
— automation
— custom module dev
…give us a call!
Why Hats?
Not everything can be governed by consensus
For many key DAO operations, the most effective approach is to delegate responsibility to a person or pod
Such delegation today primarily occurs implicitly, with little accountability & requiring a lot of trust
And finally, to our incredible community of hat wearers, builders, and contributors -- thank you thank you! A sincere tip of the cap to you all. You were there when it all began.
INTRODUCING HATS MODULES
With the modules available today, you can automate the granting & revocation of hats and their associated permissions based on any of the following criteria:
Quests: Hats protoDAO uses
@QUESTS__
and
@0xSplits
as the primary tools for tracking contributions
Contributors use Quests to log their contributions, which are then linked to the Hats Protocol Quest and other relevant Quests to create a network graph of contributions
5/13
Today's the day! No more waitlist. 🙅
Quests is here, for real. If you're on the waitlist, you'll have received an email to create your Quests profile.
It's time to have one link for who you are…and what you do.
Sign up at:
Once you grok the problem that
@hatsprotocol
is solving, you see its use case everywhere.
This V2 launch is not only a major contribution to DAOs, but governance in general.
What kinds of Hats Modules will you build?
Developers now have the power to create programmable roles that users can bring with them across the internet 🧢🦾
Here are three types of modules you can build today:
1. Eligibility modules
2. Toggle modules
3. Hatter contracts
👇
Today we are launching Hats Modules!
This is the most impactful release we've shipped since the protocol itself, and it's already catalyzing a new era for programmable organizations
Here's why:
If you’re a governance facilitator, network coordinator, community manager or DAO operator, modules...
- Save you time
- Increase security
- Simplify your life
Dive into the world of modules & experience the magic of programmatic granting & revocation:
But this is just the beginning!
What is truly powerful about the Hats Protocol Stack is that ANY BUILDER can create their own module, plug it into their own Hats tree permissionlessly, and make it available to ANY APP that supports the Hats Modules Registry 🤯
Safe multisigs: Hats protoDAO uses hat-gated
@safe
multisigs to collectively manage its resources
Revocable signing authority is delegated to individuals & teams using Hats to ensure the multisigs are ultimately controlled by the protoDAO as a whole
3/13
WORKSTREAM W/ DAO-CONTROLLED MULTISIG
Allocate resources to workstreams & enable them to govern themselves, while ensuring that the DAO retains ultimate authority over signing permissions in those
@safe
multisigs, for strong capture-resistance
4/6
Hats Protocol uses NFTs to make that delegation explicit!
This gives DAOs much more control over who is able to act on the DAO's behalf
Hats Protocol also empowers a DAO to revoke any authority it delegates, alongside other forms of accountability for authority holders
@RuzhyoX
Based on past experiences, we've chosen to use hat-gated Telegram groups (via
@Collab_Land_
) as the primary community chat tool for Hats protoDAO, with
@CharmVerse
as our go-to information depository
Why the🚩?
DeForm:
@deformapp
handles all the protoDAO's information-gathering needs
By hat-gating our DeForms using its web3 capabilities, we ensure only the right hat-wearers (e.g., Hats Community Members) can access and submit the forms meant for them
8/13
and... the space got rugged again 🫠 with only a few minutes left and 2 rugs in we'll call it a day there
but we will return with another space soon! next time perhaps with
@Livepeer
casted to X to avoid rugging...? and to enable a shared display so we can all watch
@0xNN2
build…
Over time, some Community Members may deepen their engagement to become Active Contributors and eventually Stewards
Hats Stewards are responsible for collectively governing the shared resources of the protoDAO and supporting the progressive decentralization of the project
6/9
To join the Hats Community and get involved, claim your Hats Community Member hat here:
There you'll find ways to contribute to Hats and stay in the loop as the protoDAO evolves
5/9
Join us tomorrow at 3:30pm ET for a conversation on:
- ungovernance,
- automated governance, and
- delegated responsibility
with our friends
@CupOJoseph
and
@pi0neerpat
from the
@open_dollar
team!
I was today years old when I learned that sea urchins naturally use shells as hats to make them feel safer and camouflaged so some aquarists had the genius idea to make them tiny hats
At this stage, Hats protoDAO is not a true DAO, as it is not truly decentralized
It's a protoDAO!
We commit to progressively decentralizing the project by giving more power to the protoDAO with each season (using Hats ofc!) until we have collectively cultivated a true DAO
3/9
This means that an entire ecosystem of brilliant DAO nerds, governance designers, and smart contract developers now have a way of building and sharing their best approaches to creating an onchain organization
Programmable organizations FTW 🔥
Looking for an ETH Tokyo hack project?
We've got a bunch of fun ideas for building on Hats Protocol 🧢
Check 'em out and hit us up if you wanna jam — we'll be in Tokyo to support you!
CharmVerse:
@CharmVerse
is the go-to information repository and wiki for Hats protoDAO
Charmverse pages are hat-gated with nuanced read/write/admin permissions: Community Hat-wearers can read & comment, Contributors can add new pages, and only Stewards can delete pages
9/13
Splits: Within each Quest, contributors add a
@0xSplits
address to split up the protoRep awarded to the contribution among themselves
Splits +
@QUESTS__
creates a hyperstructure of contributions and reputation that will span the life of the project (and beyond)
6/13
There’s a lot we plan to build on top of Splits, but we’re more excited to see what you’ll build. Please try out the app, explore the contracts, and let us know what you think.
Sobol: Meanwhile,
@TeamSobol
's Hats Composer app makes it easy for protoDAO members to connect their
@hatsprotocol
hats,
@safe
multisigs, and
@DAOhaus
DAOs together into a unified onchain governance system
4/13
We've leaned into this early and started building a Hats Composer app. 🟣🤝🧢
This Sobol Labs app makes it easier to compose
@hatsprotocol
@DAOhaus
@safe
and other contracts to visually express your organization's onchain ops.
Give our 🧪 a try.
Flat DAOs don't work, and roles are good 👍
@magentaceiba
shares her learnings on organizational structures from her time as a community organizer in co-ops and DAOs in the latest episode of Rehash
CollabLand: Hats protoDAO uses
@Collab_Land_
to hat-gate access into the protoDAO's Telegram channels
The moment someone loses their hat, they're automatically kicked from the appropriate TG group by the bot
10/13
Coordinape: Hats protoDAO uses hat-gated
@coordinape
circles to intersubjectively allocate protoRep based on a contribution's impact, using GIVE as a voting mechanism
Each node in a Coordinape circle is a contribution identified by Splits address w/ its Quest for details
7/13
🚨Community Call today at 4PM UTC 🚨
Join us in the Discord to hear
@nintynick_
with
@hatsprotocol
talk about how DAO's can manage roles with NFTs!
Discord link 👇
“DAO members will wear many hats in DAOs and driving those roles towards more trust minimized designs is going to be a foundational component of progressive decentralization.”
Hats is the connective tissue that ties all your other tools together, an organizational roles and permissions layer that composes with all your favorite tools and is fully controlled by the org itself, mitigating risk of internal or external capture
13/13
With that recognition, Hats Protocol is designed explicitly to compose, integrate, & interoperate with as wide a variety of tools, apps & protocols as possible.
We extend that practice to all other aspects of Hats Protocol-related technologies, from infrastructure to apps.
9/10
Hats & Accountability 🧾
Composable data legos like
@GovrnHQ
contributions,
@QUESTS__
NFTs,
@jokedao_
results,
@otterspace_xyz
badges &
@eas_eth
attestations feed into Hats to determine whether someone is eligible for a role automate granting & revocation accordingly
DAO Roles Principle
#1
: The ultimate authority needs to be held by the DAO to maintain decentralization and gain the benefits of capture resistance.
(see by
@spengrah
)
Roles must be able to be grantable and revocable by the DAO as a whole.
DAOHaus v3: Hats protoDAO governance runs through
@DAOhaus
and Moloch v3 contracts
Hats Contributors earn protoRep based on their contributions. Once they put on a Steward hat, their protoRep converts into protoVotes to govern the protoDAO commons
2/13
Hats protoDAO exists to
1) create & steward the best possible primitive for roles, and
2) explore & curate how to use the protocol to solve real problems
It will do this by:
- cultivating the Hats ecosystem
- developing net new functionality
- governing the commons
2/9
Builders of other applications can also tap into the Hats Modules infrastructure to offer these same module options to their end users.
The Hats Modules SDK makes this easy: