> For the complete documentation index, see [llms.txt](https://docs.hatsprotocol.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hatsprotocol.xyz/using-hats/glossary-and-faq.md).

# Glossary & FAQ

*NOTE: This is an unofficial Hats glossary & FAQ created by the Hats community.*

## **Questions?**

[You can use this form to submit Hats-related terms and questions that you'd like more clarity on. ](https://docs.google.com/forms/d/e/1FAIpQLSc9v4xvkFNflih6tiasB3-NO5zQqE8OMbHYPz5HwLqCfPrqTA/viewform)This can be anything from the general to the specific, the technical to the non-technical, the bland to the spicy 🌶️ . No submissions are off limits. 

All questions are optional. Responses are anonymous by default. Submissions are captured on this [sheet](https://docs.google.com/spreadsheets/d/1jJMgLHejxah4sWWpseIWWKNA6RloFCC8rlEGai3fnTg/edit?resourcekey#gid=2071491320). Once captured, Hats community members collaborate to define terms and answer questions. Once consensus is reached, the information is added to the [Hats Protocol Docs ](https://docs.hatsprotocol.xyz/)Glossary and FAQ sections.

## Glossary

{% embed url="<https://docs.google.com/spreadsheets/d/1Us0xClfM1IGBRhKt0cn5XNaqNbouxQ1pzsHN7cB8dyM/edit?usp=sharing>" %}

## FAQ

*This FAQ will be continuously updated as questions are received* [*through this submission form*](https://docs.google.com/forms/d/e/1FAIpQLSc9v4xvkFNflih6tiasB3-NO5zQqE8OMbHYPz5HwLqCfPrqTA/viewform)*.*

**What is the difference between Hats vs Hats Protocol vs Hats App?**

* Hats: the meme 🧢
* [Hats Protocol](https://github.com/Hats-Protocol/hats-protocol): the open-source roles protocol upon which many different apps and integrations will be developed
* [Hats App](https://app.hatsprotocol.xyz/): a front-end app developed to make it easy for anyone to use the protocol

**How are Hats different from membership NFTs?**

Hats are like membership NFTs in that they are nontransferable, revocable, and grant access to a group of some kind. But they are also highly programmable, automatable, boosted by a wide range of eligibility modules and integrations that are being created, and nested with deterministic IDs to enable flexible governance structures for almost any need you can imagine.

**Can I "claim" my hat or does it have to be granted by someone else?**

Both are possible! Hats can be [granted (aka "minted")](/using-hats/adding-wearers.md) to new wearers by wearers of any existing [admin hat](/using-hats/admins-creating-issuing-and-revising-hats.md), OR hats can be claimed by eligible wearers [provided the hat has been made claimable](/hats-integrations/hatter-modules/making-hats-claimable.md).&#x20;

**Can I renounce a hat if I no longer want to be part of the DAO?**

Yes! Any hat can be renounced by any wearer at any time. To renounce a hat you are wearing: select the hat in the Hats app, find your address under "Hat Wearers", select the three dots next to your address, and select "Renounce".

<figure><img src="/files/jFGqPl8qCkgggbI4xzKZ" alt=""><figcaption></figcaption></figure>

**What will happen with my Hats if I change my wallet address for whatever reason?**

Your hats will stay with the wallet address they were originally minted to. However, you can request to transfer your hats to a new address, as any admin can transfer a hat from one address to another using the "Transfer" function seen in the image above.

**How are responsibilities different than authorities?**&#x20;

* Responsibilities are the things a given hat wearer is expected to do as part of their role (e.g., a responsibility of the product workstream facilitator is to set the agenda for each product workstream meeting)
* Authorities are the permissions granted to the hat wearer (e.g., read/write access to specific communication channels or workspaces).