> For the complete documentation index, see [llms.txt](https://colorverse.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://colorverse.gitbook.io/whitepaper/revenue-streams.md).

# Revenue Streams

Colorverse will be run using a Platform-as-a-Service model where new features will be introduced over time. Colorverse earns revenue from transactions occur within the ecosystem. Additionally, there will be incurred fees whenever creators wish to leverage Colorverse’s platform to launch their NFTs or utilizing our metaverse facilities.

**The Treasury will begin to accumulate revenue once the platform is launched. Revenue generated by Colorverse will be placed in the Treasury to be used for future developments, maintenance, and marketing purposes. Revenue collected via fiat will be used for Popcorn tokens buyback and deposited into the Treasury.**

For now, these are the primary fees in Colorverse platform -

* NFT Launchpad - 20% from NFT Sales
* Transaction - 20% from various transactions such as subscriptions and tipping
* Advertising - the brand pay by our token. Watching advertisement will be treated as kind of rewarding action
* Fixed Popcorn token charges to unlock additional features such as private chatroom creation, metaverse event creation, priority placement in Discover page. (Rates to be adjusted according to the present token value)


---

# 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:

```
GET https://colorverse.gitbook.io/whitepaper/revenue-streams.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.