# Revenue Sharing

$RSNA is more than a governance token; it is the friction-reducing currency that powers every transaction within the Resona ecosystem.

**1. Core Utility Pillars**

* **Currency of Culture:** All DeArt acquisitions, fractional RWA trades, and IP licensing fees within the Resona marketplace are settled in $RSNA.
* **AI Fuel (Neon Activation):** Users must stake or spend $RSNA to activate, upgrade, and customize their Neon Agents. Higher $RSNA tiers unlock more advanced algorithmic curation tools.
* **Sovereign Governance:** $RSNA holders dictate the evolution of the protocol. They vote on which physical RWA assets are "whitelisted" for onboarding and manage the IProtocol copyright registry.
* **Economic Advantage:** Holding $RSNA provides tiered discounts on all on-chain trading and minting fees.

**2. The Revenue Sharing Model**

Resona operates as a circular economy. All protocol fees (from auctions, licensing, and marketplace trades) are distributed as follows:

* **40% - Protocol Infrastructure:** Allocated to maintaining high-speed Solana server clusters, developing the RWA-Oracle, and covering legal/custodial costs for physical assets.
* **30% - Creator Pool:** Rewarded to the artists and IP holders whose assets achieve the highest Resonance Score, incentivizing the onboarding of world-class culture.
* **30% - $RSNA Stakers:** Distributed directly to long-term stakers as yield. This aligns the community with the "GDP" of the entire Resona ecosystem.

**Economic Goal:** As cultural resonance increases and more IP is tokenized, the demand for $RSNA as "Fuel" and "Governance" grows, while the fixed supply and staking locks reduce circulating liquidity.


---

# 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://docs.rsnatoken.xyz/4.-tokenomics/revenue-sharing.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.