> For the complete documentation index, see [llms.txt](https://docs.ariaprotocol.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ariaprotocol.xyz/technical-docs/remixing.md).

# Remixing

When an asset is **remixed**, a process where a derivative work is made of an IP asset, an on chain asset is tokenized for this and will be distributed to the derivative work creator, the original IP's token stakers, and sold to the public on DEX's.

Assets can either be **parents assets** or **child assets**. A Parent asset is an original work, not remixed from any other asset, while a child asset is derived from a parent token — an original work.

The distribution of liquidity for child tokens is:

* 25% retained by the parent work creator
* 50% airdropped to stakers of the original IP
* 25% sold to the public on DEX's

When an asset is remixed, the royalties will remain completely with the parent asset — there is no splitting up of royalty revenue from the parent asset among child assets. All royalty for the child asset will come from revenue generated by the child asset.


---

# 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.ariaprotocol.xyz/technical-docs/remixing.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.