# Reveel Protocol - Introduction

Reveel is a trustless & composable protocol for sharing revenue. It helps creators distribute revenue in the most gas-optimal fashion with collaborators. Every revenue path in Reveel is created as an independent entity, which requires no external maintenance to operate.

Revenue Paths are the independent instances that receive funds and help the distribution process for a team. All ETH & ERC20 received in a revenue path will be distributed according to the [tier](https://docs.r3vl.xyz/reveel-protocol-v2-documentation/protocol-concepts/tiers) specifications.

<figure><img src="https://4079526816-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJwh6MK13vcqYXMt9EAC2%2Fuploads%2FDDXNsGzYZWkRT3xAxPzs%2FUntitled%201.png?alt=media&#x26;token=869323f0-6ff7-4bc5-985b-c3a477786472" alt=""><figcaption></figcaption></figure>

In our Getting Started section, we will walk you through how to create and use a Reveel Revenue Path.

### Key Features

* Distribute funds automatically & trustlessly between collaborators.
* Introduce complex distribution strategy using tiers.
* Withdraw funds from a single or across multiple Revenue Paths together.
* On-chain data management - no 3rd party service is used to maintain revenue information. This establishes the autonomous nature of each Revenue Path.

### Differentiators

* **Product:** Reveel enables complex revenue sharing (recoupments, evolving splits, revenue milestones...) in a single contract. Other solutions (0xSplits, OpenZeplin payment splitter...) require multiple contracts, which becomes costly from a gas perspective.
* **Architecture:** Reveel is fully decentralized. Funds never flow through a Reveel owned contract. Other solutions (0xSplits) force funds to flow through a centralized contract (not user owned).
* **Services:** Reveel offers products & services at the edge of the protocol to simplify the UX and "abstract" the tech. User Accounts (user onboarding, wallet creation & abstraction), Gas-less Revenue Paths (option to subsidize gas with a fee), and more coming.


---

# 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.r3vl.xyz/reveel-protocol-v2-documentation/reveel-protocol-introduction.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.