Hats Protocol Docs
hatsprotocol.xyzGithub
  • ๐Ÿ‘‹Welcome to Hats Protocol
  • ๐ŸงขGetting Started with Hats
  • โญQuick Start
  • Using The Hats App
    • ๐Ÿค Essentials For Hat Wearers
    • ๐ŸŽฉCreating My First Hat
    • ๐Ÿง™Admins: Creating, Issuing, and Revising Hats
    • ๐Ÿ‘ฅWhat Hats Do I Need?
    • ๐ŸŒณDrafting, Exporting, and Deploying Tree Changes
    • ๐Ÿ—๏ธSetting a Hat's Basic Properties
    • ๐ŸฅณAdding Wearers
    • ๐Ÿ”Connecting Hats w/ Permissions & Authorities
      • Types of Hat-Powered Authorities
      • Connecting Hats to Token Gates
        • Hats Protocol Contract Addresses
        • Finding a Hat's Token ID
      • Documenting Hat Powers & Responsibilities
    • ๐ŸŒŸRevocation & Eligibility: Requirements for Wearers
    • โšกDeactivating & Reactivating Hats
    • โœ…Making Hats Claimable
    • ๐Ÿ”—Linking Trees Together
    • โ›“๏ธHats Protocol Supported Chains
    • โ“Glossary & FAQ
  • Hats Integrations
    • ๐Ÿ”Permissions & Authorities
      • Coordinape
      • Council Voting Vault
      • Charmverse
      • Discord
        • Collab.Land --> Discord
        • Guild.xyz --> Discord
      • Farcaster Casting Rights
      • Fileverse
      • Google Workspace
      • Hats Account
      • Role-Based Compensation
      • Safe Multisig Signing Authority
      • Telegram
        • Collab.Land --> Telegram
        • Guild.xyz --> Telegram
      • Snapshot: Voting, Weight & Proposal Creation
      • Wonderverse
    • ๐ŸŒŸEligibility & Accountability Criteria
      • Agreement Eligibility
      • Allow-List Eligibility
      • CoLinks Eligibility
      • ERC20 Eligibility
      • ERC721 Eligibility
      • ERC1155 Eligibility
      • Hat-Wearing Eligibility
      • Hats Election Eligibility
      • JokeRace Eligibility
      • Pass-Through (Hat-Based) Eligibility
      • Staking Eligibility
      • Subscription or Membership Fee (Unlock Protocol)
      • Gitcoin Passport Eligibility
    • โšกActivation & Deactivation Criteria
      • Seasonal/ Time-Expiry Toggle
      • Pass-Through (Hat-Based) Toggle
    • ๐Ÿ‘ทHatter Modules
      • Multi Claims Hatter
      • DAOhaus Moloch v3 Membership & Share Allocation
  • For Developers
    • ๐Ÿ‘ทHats Protocol, for Developers
      • Hat Properties
      • Wearing a Hat
      • Hat Admins & Hatter Contracts
      • Hats Trees
      • Hat IDs
      • Linking Hats Trees
      • Eligibility Modules
      • Toggle Modules
      • Hat Mutability and Editing
      • Creating Hats
      • Minting Hats
      • Transfering Hats
      • Renouncing Hats
      • Batch Actions
      • Hat Image URIs
      • ERC1155 Compatibility
      • โ›“๏ธSupported Chains
    • ๐Ÿค–v1 Protocol Spec
      • Hats.sol
      • HatsEvents.sol
      • HatsErrors.sol
      • HatsIdUtilities.sol
      • Interfaces
        • IHats.sol
        • IHatsIdUtilities.sol
        • IHatsEligibility.sol
        • IHatsToggle.sol
    • ๐Ÿ–ฅ๏ธv1 SDK
      • Core
        • Getting Started
        • Onchain Reads
        • Onchain Writes
        • Multicall
        • Claiming Hats
        • Utilities
      • Subgraph
        • Getting Started
        • Fetching Hats
        • Fetching Wearers
        • Fetching Trees
        • Misc
        • Types
      • Hat Details
        • Getting Started
        • Usage
    • ๐Ÿ”ญv1 Subgraphs
    • ๐ŸงฉHats Modules
      • ๐Ÿ”ŒModules SDK
        • Getting Started
        • Get Available Modules
        • Create New Instance/s
        • Composing Modules
        • Interact With Instances
        • Utilities
        • Types
      • โš’๏ธBuilding Hats Modules
        • Inside a Hats Module
          • Immutable Arguments
          • Module Setup
          • Versioning
        • Creating New Modules
        • How Module Instances Are Deployed
        • Modules Registry
        • About Module Chains
    • ๐Ÿ”Hats Signer Gate v2
    • ๐Ÿ‘’Hats Signer Gate SDK
      • Getting Started
      • Creating New Instances
      • Hats Signer Gate
      • Multi Hats Signer Gate
      • HSG & MHSG Handlers
    • ๐Ÿ’ผHats Account SDK
      • 1 of N Hats Account
        • Getting Started
        • Creating New Instances
        • Executing From An Instance
        • Constants
        • Types
    • ๐ŸŒHats Security Audits
  • Legal
    • Terms
      • Terms of Service
      • Acceptable Use
      • Privacy Policy
      • Cookie Policy
      • Attribution
Powered by GitBook
On this page
  • Congratulations, you've received a hat!
  • What are hats?
  • What hats do I have?
  • What can my hats do?
  • What else can my hat do?
  • Can I transfer my hat?
  • How do I keep this hat?
  • Can I create other hats?
  • What else do I need to know?
  1. Using The Hats App

Essentials For Hat Wearers

So you received your first hat. Now what?

PreviousQuick StartNextCreating My First Hat

Last updated 1 year ago

Congratulations, you've received a hat!

We hope this hat gives you the context, authorities, and accountabilities you need to get things done.

What are hats?

What hats do I have?

You'll see all the hats your wallet address is holding in your My Hats page. Hats are ERC1155-compatible tokens that can be held by any address including an EOA or a contract (e.g. a multisig). When an address has a balance of 1 of a given Hats token, it is considered a "wearer" of that "hat".

What can my hats do?

In this information panel you'll find lots of information about your hat, including a description for the hat, any responsibilities associated with the role, and any authorities you receive by wearing the hat. The links found in the authorities section will usually direct you to the right place to claim those authorities. If you do not see any way to claim the authorities associated with your hat, contact the group or person who sent you your hat.

What else can my hat do?

Your hat is an admin for any hats in the direct lineage below it.

To see which hats your hat is an admin of, click on your hat in the My Hats page and take a look at the tree within which your hat exists.

As a wearer of hat 6.1.2.3 in the tree above, you are an admin for any hats in the direct lineage below it, including 6.1.2.3.1, 6.1.2.3.2, and 6.1.2.3.3.

Similarly, the hats that are direct ancestors of your hat have admin authority over your hatโ€”unless, of course, your hat is immutable.

Can I transfer my hat?

Just like you can't transfer or sell your job online without your organization's approval, you can't transfer your hats unilaterally either.

How do I keep this hat?

To see the accountabilities embedded in your hat, view your hat's information panel or contact your organization.

Can I create other hats?

Yes! As a hat wearer you can also create new child hats -- these are new hats directly beneath yours that you can set up and manage however you wish.

What else do I need to know?

A hat is a "role in a box". More specifically, hats are programmable roles which can be imbued with responsibilities, , and accountabilities. can be big and ongoing, or small and discrete.

To learn what kind of hat(s) you have, visit the , connect your wallet, and click My Hats.

Hats often come with special which you can only access as long as you're wearing that hat. To see what authorities your hat grants you, click on the hat in your My Hats page. This will open up the full structure of hats (called a "Hats tree") within which your particular hat lives, along with a information panel for your hat.

Authorities granted by the as seen in the Hats App

As an admin, you can change a hat's name, image, description, max supply, authorities, and accountabilities, grant the hat to new wearers, and transfer the hat from one wearer to another -- but ONLY if the hat is . When hats are immutable, your admin powers are diminished.

You can find the hats you're wearing in this tree based on the little green hat icon seen in the hat cards. For example, in the image below, you would see that you are wearing the Product Workstream Facilitator hat 6.1.2.3 ().

No. Hats are nontransferrable by the wearer. Hats can only be transferred or revoked by its as well as the accountability addresses for your specific hat.

To keep your hat, you'll need to fulfill whatever responsibilities are associated with your hat, as well as remain eligible according to . Accountabilities could include things like holding certain tokens or NFTs in your wallet, staking, winning an organizational election, or agreeing to specific conditions. If you don't follow these accountabilities, your hat could be manually or automatically revoked or deactivated.

But take note! Any hats that are the admin of your hat will ALSO be the admin of the child hats you create. Additionally, if you are not the sole wearer of your hat (as hats can be worn by multiple addresses up to the ), then any of the other wearers of your hat will also have admin powers over the child hat you created.

If you'd rather ensure that you are the only admin over the hats you create, it's probably best or create a new child hat that you then make immutable.

Those are the basics. If you have other questions or are unsure of what a term means, visit the .

For everything else, you'll find the information you need in the docs found here or via the group that sent you your hat. And if that's not enough, you can always , we're here to help.

๐Ÿค 
authorities
Roles
Hats App
authorities
for more on hat IDs, see here
admin hats
the accountabilities embedded in your hat
to create a new Hats tree
Glossary & FAQ
get in touch with us here
Hats Community Member hat
max supply
mutable
The My Hats page is your portal to accessing all your hats. If you don't see the My Hats link, be sure to connect to the app with the correct wallet address.
Admin relationships