# Child assets Child assets are tokenized gaming assets minted by a studio after receiving approval to reuse a parent asset. They represent the authorized use of an original asset inside another game and inherit the licensing rules and royalty settings defined by the parent asset. A child asset contains its own metadata and a reference to the parent asset it originates from. This creates an on-chain parent child connection that forms the basis of interoperability. The child asset may include game specific modifications, but it always maintains a verifiable link to the original parent asset. Only studios can mint child assets because only studios operate games. Creators cannot mint child assets, but they approve or reject reuse proposals for the parent assets they own. Once a proposal is approved, the studio gains permission to mint a child asset and integrate it within their game. Child assets **cannot be reused or listed for reuse**. They cannot serve as parent assets for new proposals, and no studio can mint another child asset based on an existing child asset. All reuse must originate from the original parent asset, ensuring a clear and verifiable lineage. Any economic activity related to the child asset, such as paid mints or secondary trades, activates the royalty rules defined in the parent asset. Royalties are automatically routed to the parent asset owner and the integrating studio according to the predefined distribution. Child assets allow content to expand across multiple games while maintaining attribution, ownership, and commercial rights for the original creator or studio. --- # Agent Instructions: 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: ``` GET https://infinity-games.gitbook.io/infinity-games-docs/interoperable-asset-store/key-concepts/child-assets.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.