> For the complete documentation index, see [llms.txt](https://flexecosystem.gitbook.io/flex-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://flexecosystem.gitbook.io/flex-docs/protocol/flex-commons/code-tokenization.md).

# Code Tokenization

The IP Commons utilizes the ERC-721 and ERC-1155 token standards to represent code assets as unique or semi-fungible tokens. These code NFTs contain metadata such as the code's functionality, dependencies, authorship, version, and licensing terms, stored in decentralized storage systems like IPFS or Arweave.

The tokenization of code assets enables fractional ownership, composability, and tradability of code, allowing multiple developers to collaborate on and derive value from the same codebase. The use of NFTs also provides a tamper-proof and auditable record of the code's provenance and lifecycle on the Flex blockchain.

{% hint style="info" %}
Developers can mint new code NFTs using the IP Commons' smart contracts, which enforce a standardized metadata schema and ensure the uniqueness and authenticity of each token. The minting process may require staking FLEXE tokens as collateral to prevent spam and low-quality submissions.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://flexecosystem.gitbook.io/flex-docs/protocol/flex-commons/code-tokenization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.