# Revenue Flows

#### 1. Dual-Token System

* Origin NFT (ERC721): Legal IP ownership minted by Camp Network's Origin Protocol
* RoyaltyVault Tokens (ERC20): Fractional revenue rights minted by Zync (1B per video)

#### 2. Token Minting Process

* Step 1: Origin Protocol registers IP and mints NFT with provenance
* Step 2: Zync deploys RoyaltyVault contract linked to Origin NFT
* Step 3: 700M tokens to creator, 300M for public sale

#### 3. Revenue Distribution

Clear mermaid diagram showing: Content Purchase → Origin Protocol → RoyaltyVault → Token Holders

#### 4. Economic Example

* 1 billion tokens total supply
* Initial price: 0.0001 CAMP per token
* Launch market cap: 100,000 CAMP (\~$100,000)
* Revenue split: 95% to token holders, 5% platform fee

#### 5. Token Utility & Rights

* Revenue Rights: Proportional dividends from all licensing
* Governance Rights: Future voting on licensing terms (planned)
* Trading Rights: Immediate liquidity on SummitX AMM

### 💡 Key Value Proposition:

This architecture separates IP ownership (stays with creator via Origin NFT) from revenue sharing (distributed via tradeable tokens). This means:

* ✅ Creators maintain legal ownership of their content
* ✅ Supporters can invest in creator success through tokens
* ✅ Automatic revenue distribution via smart contracts
* ✅ Immediate liquidity for position trading
* ✅ Transparent on-chain revenue tracking

The dual-token system enables PE-style revenue sharing deals that were previously only available to well-connected creators, now democratized for anyone through Zync's platform.


---

# 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://zync-1.gitbook.io/zync-docs/revenue-flows.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.