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

# Aetheryn descendants

A separate descendant collection with its own DNA, ancestry, Birth Vault and Hunt history.

> **Genesis begins the family. Aetheryn carries it forward.**

![Four zoomed-out Aetheryn creature studies showing complete auric, reactor-petal, lattice, and crimson inherited anatomy](https://164480815-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0r3IgolbVPO14VcUCkOG%2Fuploads%2F3MhtxEJ122JeLr0gUWmq%2Faetheryn-team-lab-showcase-v2.webp?alt=media)

Aetheryn is Stockmon’s coming-soon descendant collection: a separate world for incubation, hidden outcomes, permanent ancestry, and creatures born from the Genesis family tree.

{% hint style="warning" %}
**Release status · 17 September 2026.** The successor Egg, Aetheryn and Hunt contracts have been deployed and configured. Controlled activation and public opening remain pending. These pages describe the successor flow; a deployed address alone does not mean a feature is available. Simulated previews remain labeled as simulated.
{% endhint %}

## Genesis and Aetheryn are different collections

The **116 Genesis Stockmons never expand or get renumbered**. Aetheryn descendants live in their own collection and supply domain.

| Genesis                           | Aetheryn                                                             |
| --------------------------------- | -------------------------------------------------------------------- |
| Fixed 116: 100 Hybrids + 16 Pures | Separate descendant collection, capped at 100,000 successful hatches |
| Original permanent DNA            | Inherited permanent DNA; descendants are never Pure                  |
| Seven lifetime fertility uses     | Three lifetime fertility uses per descendant                         |
| Can be the single parent for G1   | G2+ uses two distinct compatible Aetheryn parents                    |
| Must earn seven Readiness Marks   | Starts with zero marks and must earn seven of its own                |

## The incubation loop

1. A Genesis or every participating Aetheryn parent has seven finalized Readiness Marks, available fertility, and no active cooldown.
2. G2+ parents pass the same-wallet and kinship compatibility checks.
3. The interface discloses the complete DNA catalog, exact probabilities, and exact MON quote before payment.
4. One accepted payment seals a transferable Egg with a single hidden outcome and **zero rerolls**.
5. Participating parents enter a fixed **24-hour cooldown** while the Egg incubates.
6. After maturity and artwork approval, the current Egg owner hatches the exact committed child.

No child token ID is assigned at payment. A successful Hatch burns the Egg and consumes the next lifetime-unique Aetheryn ID. If artwork or reveal service is delayed, the same Egg remains pending and transferable—there is no artless child mint, timeout refund, cancellation, or redraw.

## Readiness, fertility, and family rules

Each finalized, qualifying normal Hunt lasts at least **6 hours 30 minutes (23,400 seconds)** and earns one permanent Readiness Mark. Early return, rescue and transfer-triggered close earn zero. The first **seven marks unlock that parent’s readiness**. Marks follow the NFT through transfers and are not spent on a birth: seven new Hunts are not required before each subsequent birth.

Genesis has seven lifetime fertility uses; revealed Aetheryn has three. A G1 Egg uses one Genesis parent. A G2+ Egg uses two distinct Aetheryn owned by the same wallet. Self-pairs, ancestors and descendants, full siblings, and half siblings are incompatible; cousins are allowed.

See Breeding rules and Aetheryn Eggs for the complete owner rulebook.

## How `$MON` fuels a birth

One incubation costs **$15 USD-equivalent of `$MON` at payment**. The received MON splits once:

| Bucket                | Share | 60 MON example |
| --------------------- | ----: | -------------: |
| Egg-bound birth vault | 87.5% |       52.5 MON |
| Treasury              | 12.5% |        7.5 MON |

These are the only two buckets. The 87.5% share belongs to the sealed Egg’s birth vault. It is not a liquid wallet balance and does not promise market value or yield.

The MON quote remains valid for five minutes and accepts at most 10% price drift. The current Egg owner—not necessarily the payer or parent owner—receives the child and its Birth Vault entitlement at Hatch.

## The lineage universe

Aetheryn DNA draws from an append-only registry of **196 visual identities**. Every one of those 196 lineages can shape an Aetheryn image through anatomy, silhouette, materials, color, eyes, energy, lighting, and personality.

Indices `0..193` preserve the original market registry exactly. ETH and CASHCAT are the final two visual lineages at indices `194` and `195`; they extend the registry without renumbering or changing earlier DNA. They are not the only lineages used for creature imagery.

The Aetheryn collection is capped at **100,000 lifetime successful descendants**. Burns never reopen capacity or restore parent fertility.

### One creature, its own DNA and value

Every revealed Aetheryn has its own authenticated DNA and ancestry. Hunt admission checks that original record. A child starts with zero Readiness Marks and its own empty Field basket; it does not copy a parent’s balances, marks or financial history. Genesis artwork and DNA remain unchanged.

#### Birth Vault and Field value stay distinct

The **Birth Vault** holds the child’s MON entitlement from sealing its Egg. The **Field basket** records eligible assets earned through that creature’s Hunts. Hunt principal, a parent’s existing Genesis Feed basket and the child’s Birth Vault are separate records.

Field value stays attached to the NFT while it exists. Transferring the creature transfers its attached entitlement. Completing the supported burn/redemption flow fixes the beneficiary; that beneficiary can then claim settled Field stock and any backed, unconverted Field USDG. Later settled credits remain claimable by the same beneficiary. Burning is permanent and does not restore fertility or collection capacity.

Pending USDG is shown as USDG. Conversion can use only compatible routes fixed in the launch catalog; an unavailable route does not create stock or a guaranteed future conversion. Automated feeding conversions are not promised at launch.

Read [Hunt](https://raretyperesearch.gitbook.io/stockmon/hunt) for principal, Field and Camp accounting, and [Breeding rules and Aetheryn Eggs](https://raretyperesearch.gitbook.io/stockmon/hunt/breeding) before sealing an Egg. The [contract map](https://raretyperesearch.gitbook.io/stockmon/status-and-risks/hunt-and-aetheryn-contract-map) shows how the successor collections and services connect.

Next: Get your Stockmon Breeding-ready, then [meet all 196 lineages](/stockmon/aetheryn/196-lineages.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/aetheryn.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.
