# Submitting a reuse proposal

When a studio wants to reuse a tokenized gaming asset from another collection, the process begins by sending a reuse proposal. This proposal notifies the original creator and allows them to approve or reject the request before any integration or child-asset minting can take place.

Only studios can mint child assets, but both studios and creators can receive reuse proposals for their parent assets.

#### **1. Compatibility requirements**

Collections created through the Interoperable Asset Store are automatically compatible with asset integrations.\
Collections created outside the Asset Store are not automatically compatible, because the protocol must enforce immutable royalty logic. For protection and integrity, external collections must be upgraded before they can mint child assets.

Upgrading requires importing the **AbstractGamingStudioAsset** contract and adding the integration logic to ensure that royalty functions cannot be modified or bypassed. The next chapters will explain this process in detail.

#### **2. Opening the proposal modal**

To propose an integration:

1. Navigate to the asset page of the parent asset you want to reuse.
2. Click the **Propose** button.
3. This opens the proposal modal (shown in the screenshot), displaying:
   * Platform fee
   * Creator royalty fee
   * Royalty recipient
   * Dropdown list of your collections

The studio must select the collection where the child asset will be minted **after approval**.

<figure><img src="/files/nV1GV1UKZc1DCe1Y5Vgm" alt=""><figcaption></figcaption></figure>

#### **3. Review the integration requirements**

Inside the modal, developers will see instructions for ensuring their selected collection is compatible with the Interoperable Asset Store. This includes:

* Installing required NPM packages
* Importing the `AbstractGamingStudioAsset` contract
* Initializing it within the upgradeable collection
* Ensuring the correct royalty logic and origin validation

These steps ensure the collection inherits immutable royalty distribution and parent-child linking functionality.

#### **4. Sending the proposal**

Once a compatible collection is selected:

1. Click **Submit**.
2. The proposal is sent to the asset owner (creator or studio).
3. The proposal appears under the *Proposals* section on the asset page.

The original asset owner will then approve or reject the request. A **child asset is automatically minted** as soon as the reuse proposal is approved.


---

# 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/using-the-interoperable-asset-store/submitting-a-reuse-proposal.md?ask=<question>
```

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.