> For the complete documentation index, see [llms.txt](https://docs.xchandles.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xchandles.com/techincal-manual/xchandles/the-expire-action.md). # The Expire Action *Note*: The expire action code be found [here](https://github.com/Yakuhito/slot-machine/blob/master/rue-puzzles/actions/xchandles/expire.rue) ([Chialisp](https://github.com/Yakuhito/slot-machine/blob/master/puzzles/actions/xchandles/expire.clsp)). When handles expire, they're auctioned off by using a second pricing puzzle. Usually (and by default), the other pricing puzzle will use the time when the handle expired and the registration time to calculate a premium, which is added to the base price. The premium decreases (exponentially in the puzzle used at launch) as more time passes - essentially creating a public 'auction' where it's in the potential owners' best interest to pay their maximum price for the handle to secure it. Because the handle is changing owners, precommitment coins are used to solve the concern of potential mempool snipers (malicious farmers). The value of a precommitment coin will be the same as that for registrations. Note that the pricing puzzle will now describe the auction puzzle, not the 'standard one.' At expiration, the owner and resolved singleton(s) need to send messages to the registry to confirm the user owns them. The action also creates a puzzle announcement that be asserted to ensure the dApp singleton is running the right action with the right parameters. For the extend action, the announcement prefix, `x`, is concatenated to the precommit coin's full puzzle hash. *Written by* [*yakuhito*](https://x.com/yakuhito) *from* [*FireAcademy.io*](https://fireacademy.io/) *on Feb 15th, 2025.* --- # 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.xchandles.com/techincal-manual/xchandles/the-expire-action.md?ask=&goal= ``` `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.