# Glossary

**Interoperable Asset Store (IAS)**\
The protocol that enables tokenized gaming assets to be reused across multiple games through permissioned approvals, parent–child connections, and immutable royalty logic.

**Studio**\
A registered game development team that can tokenize assets, list them for reuse, submit reuse proposals, and mint child assets for integration in their games.

**Creator**\
A freelancer or independent artist who can tokenize and list original assets, approve reuse proposals, and earn royalties, but cannot mint child assets because they do not operate a game.

**Collection**\
A namespace that contains all tokenized assets owned by a studio or creator. Collections may be created directly in the IAS or imported from existing on-chain collections.

**Listing an asset on the Interoperable Asset Store**\
The process of registering a tokenized gaming asset inside the IAS by uploading its encrypted source files to IPFS and entering technical details such as engine compatibility, polygon count, animations, and other specifications. Listing an asset makes it available for reuse proposals.

**Parent asset**\
An original tokenized asset containing on-chain metadata and encrypted IPFS files. Parent assets can be listed for reuse and form the source for all child assets derived from them.

**Child asset**\
An NFT minted by a studio after a reuse proposal is approved. It references a parent asset, inherits its royalty configuration, and represents an authorized version used in another game.

**Reuse proposal**\
A permissioned request sent by a studio to the owner of a parent asset, asking for approval to integrate that asset into their game and mint a child asset.

**Parent–child connection**\
A permanent on-chain link that records which child asset was derived from which parent asset, ensuring clear lineage and royalty enforcement.

**Royalty schema**\
The predefined royalty configuration of a parent asset that determines how revenue from child asset activity is split between creator, studio, and the ecosystem.

**5 percent protocol fee**\
A fee collected by the IAS on every economic event derived from a reused (child) asset, including paid mints and secondary trades.

**Encrypted asset files**\
The original 3D models, textures, animations, or other files linked to a parent asset and stored on IPFS. File access is granted only after reuse approval.

**Prometheus Marketplace**\
The native marketplace of the Infinity Games ecosystem where all IAS-connected collections are listed, allowing users to browse, mint, and trade assets.

**Listing a collection on Prometheus**\
The appearance of any IAS-connected collection on the Prometheus Marketplace. When a collection interacts with the IAS (either by listing assets or by reusing assets), it becomes visible on Prometheus together with all its assets. This enables users to browse, mint, and trade NFTs.

**Infinity Games token (INFY)**\
The utility token of the ecosystem used for marketplace fees, protocol fees, governance participation, and gameplay-driven reward loops.

**Lineage tracking**\
The protocol’s system for storing and verifying historical asset relationships, ensuring transparency in cross-game reuse.

**Game integration**\
The process by which a studio incorporates parent or child assets into their game after receiving reuse approval and decrypting the relevant files.


---

# 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/support-resources/glossary.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.