> 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/mon/vault-and-feed/a-complete-feed-example.md).

# A complete Feed example

This example follows one easy round from received WETH to one Genesis Stockmon. The numbers are teaching values, not a live balance or price quote.

## The example

Assume the Stockmon Vault receives exactly **0.0232 WETH** of distributable revenue for one Feed round.

| Round allocation                 | Exact amount |
| -------------------------------- | -----------: |
| WETH received by the Vault       |  0.0232 WETH |
| Genesis Stock Token budget — 50% |  0.0116 WETH |
| Project-treasury share — 50%     |  0.0116 WETH |

The two halves are tracked separately. The project-treasury share never becomes part of a Genesis basket.

## Divide the Genesis budget equally

All 116 living Genesis IDs receive an equal value share before DNA is applied.

```
0.0116 WETH ÷ 116 living IDs = 0.0001 WETH per Genesis ID
```

Mint timing does not change this step. Available-unminted and wallet-owned Genesis IDs both count as living until permanent burn.

## Apply one creature’s DNA

Now use a teaching Stockmon with this permanent DNA:

| Lineage   | DNA weight | WETH assigned from its 0.0001 WETH share |
| --------- | ---------: | ---------------------------------------: |
| Lineage A |        60% |                            0.000060 WETH |
| Lineage B |        25% |                            0.000025 WETH |
| Lineage C |        15% |                            0.000015 WETH |
| **Total** |   **100%** |                        **0.000100 WETH** |

DNA divides the equal Genesis share. It does not change the size of that share.

## Settled versus pending

Each lineage follows one of two outcomes:

### The route settles

The Vault verifies the Stock Token output and records the resulting token units for that Genesis ID and lineage.

### The route does not settle

The assigned WETH stays pending for that same Genesis ID and lineage. It is not moved to another creature or swept into Treasury.

One failed lineage does not erase successful lineages. The ledger keeps each result separate.

## What Markets displays

Markets reads the exact settled Stock Token units and pending WETH from the token-level ledger. When complete fresh prices are available, it applies them to show a timestamped USD estimate.

The estimate can change with prices. The onchain atoms do not change because a display price moved.

![Feed flow from received WETH through the 50/50 split, equal Genesis shares, DNA allocation, and settled or pending token-level accounting](https://164480815-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0r3IgolbVPO14VcUCkOG%2Fuploads%2Fpz71GykpH9BpOGiFvmJS%2Fvault-feed-v2.svg?alt=media)

Next: [Your first 10 minutes with Genesis](/stockmon/start-here/your-first-10-minutes-with-genesis.md), or explore [Markets](/stockmon/markets.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/mon/vault-and-feed/a-complete-feed-example.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.