# Parent–child linkage

Parent–child linkage is the core mechanism that enables asset interoperability across multiple games. It defines how an original tokenized gaming asset, the parent asset, becomes available for approved reuse, and how studios mint connected versions of that asset, the child assets, inside their own collections. This linkage ensures that every reused asset remains permanently tied to its original creator, its licensing terms, and its royalty configuration.

### **How the linkage works**

#### **1. Parent asset creation**

A creator or studio tokenizes an original gaming asset by uploading encrypted files to IPFS and storing the metadata on-chain. This parent asset serves as the authoritative source for all future reuse.

#### **2. Reuse proposal**

When another studio wants to integrate the asset into one of its games, it submits a reuse proposal through the Interoperable Asset Store. The proposal identifies the parent asset and requests permission to mint a linked child asset.

#### **3. User approval**

Only the owner of the parent asset can approve or reject the proposal. Once approved, the protocol grants the integrating studio permission to decrypt the asset files for use inside its game.

#### **4. Child asset minting**

The integrating studio mints a child asset in its own collection. The child asset references the parent asset, inherits immutable royalty rules, does not contain its own file set, and represents the approved reuse of the parent asset inside another game.

#### **5. Permanent relationship**

Once minted, the parent–child connection becomes permanent and visible on-chain. This includes the origin of the asset, the link between parent and child tokens, the royalty routing rules, and the licensing terms enforced automatically by the protocol. Child assets cannot be reused again through the protocol.

### **Why parent–child linkage matters**

* Guaranteed original creator attribution
* Immutable royalty flow
* Secure file permissions
* Consistent and predictable interoperability


---

# 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/architecture/parent-child-linkage.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.