> For the complete documentation index, see [llms.txt](https://docs.pulse.domains/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pulse.domains/contract-api-reference/name-wrapper/wrapped-states.md).

# Wrapped States

Taking the Name Wrapper into account, an PNS name can be in one of these possible states:

**Unregistered:** The name has not even been registered/created yet, or it has expired.

**Unwrapped:** The name exists and has not expired (in the case of .pls second-level names). The Name Wrapper contract does not have ownership over the name. You own the name in the registry and/or .pls registrar.

**Wrapped:** The Name Wrapper contract has ownership of the name (in the registry/registrar). You are issued an ERC-1155 NFT in return, which proves that you are the actual owner. You can unwrap the name at any time, which burns the ERC-1155 NFT, and returns ownership in the registry/registrar back to you. If your name is a subname like `sub.name.pls`, then the owner of `name.pls` can technically replace the subname and transfer it to a different owner. In addition, the parent owner can burn parent-controlled fuses on your name.

**Emancipated:** The owner of the parent name is no longer able to replace this name, or burn any additional fuses on it. All .pls second-level names (like `name.pls`) are automatically put into the Emancipated state when they are wrapped. The name can still be unwrapped and rewrapped by the owner.

**Locked:** The name can no longer be unwrapped. The owner can now burn owner-controlled fuses on the name. Fuses for subnames of this name can now be burned as well.

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pulse.domains/contract-api-reference/name-wrapper/wrapped-states.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.