> For the complete documentation index, see [llms.txt](https://raretyperesearch.gitbook.io/stockmon/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://raretyperesearch.gitbook.io/stockmon/nft-lifecycle.md).

# The NFT lifecycle

A Genesis Stockmon is an ERC-721 NFT whose token ID is the durable link between its creature identity, permanent DNA, ownership, and sealed Vault accounting.

![Lifecycle from a visible Genesis ID through ownership and transfer to permanent burn and independent post-burn claims](https://164480815-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0r3IgolbVPO14VcUCkOG%2Fuploads%2FQ6HIONEvjlQU2lNA1Ab1%2Fnft-lifecycle-v2.svg?alt=media)

## Before mint

All 116 Genesis creatures are visible. An available ID is still living for Feed accounting, even though no wallet owns it yet.

When mint is available, the confirmation shows the exact token, contract, and network. A free mint can still require network gas.

## While owned and living

The current owner can hold or transfer the NFT. Feed entitlement remains keyed to the token ID—not to the wallet that happened to own it during an earlier round.

This means:

* ownership changes do not reset DNA;
* ownership changes do not reset Feed history;
* the sealed basket follows the NFT; and
* no one can withdraw the living basket one ticker at a time.

## Marketplace transfer

A successful NFT sale changes the onchain owner. The buyer receives the living token ID with its existing sealed accounting. The seller does not keep a hidden claim on the living basket.

Always verify the current owner, approval state, order status, chain, collection contract, token ID, currency, fee, and final wallet request before signing.

## Permanent redemption

Redemption is the one-way exit from the living system:

1. Required Feed rounds and fallback conditions must be satisfied.
2. The NFT is marked extinct and burned.
3. The burner becomes the immutable redemption beneficiary.
4. Future Feed snapshots exclude the token ID.
5. Matured WETH and settled Stock Token claims are released independently.

Claims are separate. One paused or reverting ticker does not block another supported ticker or matured WETH claim.

{% hint style="danger" %}
Burning destroys the NFT permanently. It cannot be reminted, transferred, or returned to the living supply. Failed or still-pending claims may remain retryable after burn, so “burned” does not always mean “fully paid.”
{% endhint %}

## Four useful states

| State                   | Meaning                                                                   |
| ----------------------- | ------------------------------------------------------------------------- |
| Available unminted      | Visible, living, not yet wallet-owned                                     |
| Owned living            | Wallet-owned, transferable, continues receiving eligible Feed allocations |
| Burned with open claims | Extinct; beneficiary fixed; one or more claims remain                     |
| Burned extinct          | Extinct with no remaining protocol claims                                 |

Next: [Your first 10 minutes with Genesis](/stockmon/start-here/your-first-10-minutes-with-genesis.md), then [Marketplace and Den](/stockmon/nft-lifecycle/marketplace-and-den.md).


---

# 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://raretyperesearch.gitbook.io/stockmon/nft-lifecycle.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.