> 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/expiry.md).

# Expiry

In order to burn any fuses on a name, you must also set an **expiry** on it. If the name is a .pls 2LD, then the expiry will automatically be set to the same expiry in the .pls Registrar. But for all other names, the parent can choose what expiry to set for a child name.

The expiry for a name can only be at **max** the same as the parent expiry, it cannot expire after the parent name. So if the parent expires in 2 years, then you can only set the expiry of the child name up to a max of 2 years (though you could also choose to set it to something less like 1 year).

When you renew a wrapped .pls 2LD, the expiry is automatically updated in the Name Wrapper as well.

For all other names:

* The parent owner can always extend the expiry for a child name.
* If the **CAN\_EXTEND\_EXPIRY** fuse is burned, then the owner of the name can extend their own expiry as well.

When a name is merely **Wrapped** but not **Emancipated** or **Locked**, parent-controlled fuses can still be burned. This means that the parent can burn a custom fuse for a limited amount of time. When the expiry is reached, all fuses will be reset, but the name will otherwise be unaffected.

When a name is **Emancipated** or **Locked**, the expiry has an important additional effect. In this scenario, when the expiry has been reached, **the name itself will expire**, and the owner **loses ownership** of the name.


---

# 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/expiry.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.