> For the complete documentation index, see [llms.txt](https://hotdogs-1.gitbook.io/upgradable-traits/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hotdogs-1.gitbook.io/upgradable-traits/first-step-general/usage-and-circulation.md).

# Usage and Circulation

**Each HotDog Recipe represents an upgradable trait that can interact with eligible Abstract Hotdogs NFTs, meaning all** [**Abstract Hotdogs NFTs**](https://opensea.io/collection/abstract-hotdogs-abstract) <mark style="background-color:$danger;">**except the first 26 NFT IDs.**</mark>

**These Recipes can be:**

* Fused into an eligible Abstract Hotdogs NFT to apply the related trait.
* Listed for sale on marketplaces.
* Kept in your wallet as collectible NFTs.
* Transferred to another wallet.

**When a HotDog Recipe is fused into an eligible Abstract Hotdogs NFT**, the **Recipe NFT** is burned and the related trait is permanently recorded on that NFT.

This process may change the NFT’s:

* Appearance <mark style="background-color:$success;">(Holder-controlled)</mark>
* Metadata <mark style="background-color:red;">(updated on-chain)</mark>
* Rarity value <mark style="background-color:red;">(updated on-chain)</mark>

Once a Recipe is fused, the NFT’s metadata and rarity remain in their updated state unless another Recipe is fused later. If no additional Recipe is used, those changes may remain indefinitely.

However, you can still manage the visual appearance of previously fused upgrades through the HotDog Wardrobe system. HotDog Wardrobe lets you equip or unequip supported visual traits, but this only affects how the NFT looks. Equipping or unequipping a trait does not change the NFT’s metadata or rarity.

## Marketplace and Secondary Circulation

<figure><img src="/files/4pi1xnWvgqNT72DTffjo" alt=""><figcaption></figcaption></figure>

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

Initially, [**HotDog Recipes**](https://opensea.io/collection/hotdogrecipes) can only be obtained through the official Upgradable Traits website while the case page is open for a limited time.

However, until a **HotDog Recipe** is fused into an eligible Abstract Hotdogs NFT and burned, the **Recipe NFT** can exist as its own NFT, be held, transferred, and listed on marketplaces.

**This system provides a way to trade Recipes you do not plan to use**, while also allowing traits that may be valuable to other users to circulate within the community.

A Recipe that feels unnecessary to you may be an important piece in someone else’s path toward their **Dream HotDog**.

This structure gives you an alternative path if you want to reduce reliance on case openings, while also supporting trading, sharing, competition, and participation within the community.


---

# 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://hotdogs-1.gitbook.io/upgradable-traits/first-step-general/usage-and-circulation.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.
