> For the complete documentation index, see [llms.txt](https://docs.os.codes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.os.codes/overview/roadmap/osfork-tokenized-code-assets.md).

# osFork - Tokenized Code Assets

osFork enables developers to tokenize repositories as tradeable NFTs, creating liquid markets for code ownership while maintaining open-source accessibility.

### How It Works

#### Tokenization Process

1. **Repository Selection** - Choose any OpenSource repository
2. **NFT Minting** - Create ERC-721 token representing ownership
3. **Fractional Shares** - Optional ERC-1155 for partial ownership
4. **Automatic Royalties** - Smart contracts distribute fork revenues

#### Revenue Streams

```
Fork Revenue = Usage Fees + Integration Licenses + Derivative Works
```

* **Usage Fees**: Projects pay to integrate tokenized code
* **Fork Royalties**: Original authors earn from all derivatives
* **Trading Fees**: 2.5% on secondary market transactions

### Token Economics

#### Value Drivers

* **Code Quality Score** - AI-assessed functionality and security
* **Usage Metrics** - Downloads, forks, and integrations
* **Community Ratings** - Developer endorsements
* **Revenue History** - Proven earning potential

#### Pricing Model

* Initial price set by creator
* Dynamic AMM for liquid trading
* Bonding curves for popular repositories
* Floor price guaranteed by treasury

### Use Cases

* **Open Source Sustainability** - Maintainers earn from their work
* **Code Investment** - Trade promising repositories like assets
* **Corporate Compliance** - Clear licensing and payment trails
* **Innovation Incentives** - Rewards flow to original creators


---

# 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://docs.os.codes/overview/roadmap/osfork-tokenized-code-assets.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.