Summary: Hats Protocol is an onchain roles-and-permissions system that represents organizational roles as revocable, non-transferable ERC-1155-style tokens (“hats”). Its official materials emphasize programmable delegation of authority, automation modules, token-gated access across crypto and offchain tools, Safe signing controls, and broader organizational-graph infrastructure for humans, multisigs, contracts, and AI agents.
What it does:
Lets organizations create role trees (“hats trees”) that encode admins, wearers, accountability relationships, and delegated authorities onchain
Represents roles as non-transferable tokenized objects that can be granted, revoked, automated, and linked to permissions in other tools
Connects hat ownership to practical authorities such as Safe multisig signing, Snapshot voting, Discord/Telegram access, Google Workspace access, and other token-gated resources
Exposes protocol-spec docs, SDKs, subgraphs, module tooling, and module patterns for eligibility, toggles, signer gates, and other extensions
Publishes open-source contracts and documentation, plus public repos for newer tooling such as MCP- and agent-adjacent services in the broader Hats ecosystem
Key claims:
Official docs describe Hats as a “full-stack solution for organizing onchain” and say roles are rich ERC-1155 objects bundling responsibilities, permissions, and incentives
Permissions docs explicitly frame Hats as infrastructure for managing permissions for human and AI agents across the open internet, spanning accounts/resources, communications, governance, and workspaces
The docs show Hats integrating not just with crypto-native systems but with offchain coordination surfaces like Discord, Telegram, Google Workspace, and Fileverse, which makes it better understood as a cross-context permissioning layer rather than only a DAO badge system
Developer docs position modules as the “lifeblood” of the protocol, with eligibility, toggle, and hatter contracts serving as the main customization and automation surface
Hats Signer Gate v2 docs show a concrete Safe/Zodiac integration that can dynamically grant and revoke multisig signing rights based on current hat-wearing status and automatically manage signer thresholds
Public GitHub materials show core contracts, docs, modules, APIs, and newer ecosystem repos such as hats-mcp-server, aligned-agent, and voting-services-mcp, which suggests active experimentation with agent-facing organizational tooling
The core protocol repo states Hats Protocol is for DAO-native roles and credentials supporting revocable delegation of authority and responsibility, and it includes public audit references
Whitepaper: No classic whitepaper or litepaper was found during this pass. The strongest primary materials were Hats Protocol’s website, docs intro, permissions/integrations pages, protocol-spec and module docs, Signer Gate docs, GitHub organization, and core-contracts repository; see ../whitepapers/hats-protocol-primary-sources-2026-04-25.md.