Hats-Protocol / Hats-Protocol/hats-protocol

Hat mutability research

Open
#3 6 comments 0 reactions 0 assignees View on GitHub
community feature idea
Dominant language
Solidity
Stars
98
Forks
29
PR merge metrics
No merged PRs in 30d

Description

Currently, hats are immutable in the sense that their properties -- ie max supply, details, imageURI, toggle, and eligibility -- cannot by changed once the hat is created.

This has the benefit of limiting the governance / attack surface for hats, but at the cost of flexibility for DAOs. For example, a DAO may want to add mechanistic eligibility logic to an existing hat after experimenting manually with several candidate approaches. Currently, this would require creating and minting a brand new hat.

This is a research issue, with the goal of exploring the following questions:
1. What is the design space for hats mutability? On what dimensions could mutability be introduced partially or with constraints?
2. What are the risks and trade-offs of the dimensions from (1)?
3. What is a recommended approach for hats mutability?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.