# Storage layer The storage layer of the Interoperable Asset Store is responsible for securing and referencing the source files of every parent asset. It combines encrypted file handling with decentralized storage to ensure that creators retain full control over their work while allowing approved studios to integrate assets into their games. Parent asset files, such as textures, meshes, models, or animations, are encrypted locally before being uploaded to IPFS. This prevents anyone from accessing the raw files unless they have explicit permission. The encrypted file reference is stored as part of the parent asset’s on-chain metadata, creating a permanent link between the tokenized asset and its source files. When a reuse proposal is approved, the protocol grants the integrating studio permission to decrypt the IPFS files through wallet-based access. This permission is given only after explicit approval from the parent asset owner. Child assets do not store their own file sets; they remain linked to the parent asset and rely on the decrypted files for integration within the studio’s game. This approach ensures that asset files remain secure, access is permission based, and every integration is governed by verifiable on-chain events. --- # 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/storage-layer.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.