> For the complete documentation index, see [llms.txt](https://docs.saga.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saga.xyz/introduction/saga-overview/partnership-models.md).

# Partnership Models

Saga’s unique and flexible product design enables partnership models with other ecosystems that allow for accrual of value to these ecosystems’ tokens and communities even when Saga serves as the base chain.

First, Saga could partner with various other layer one blockchain ecosystems to offer horizontal scalability solutions while keeping the economics of the respective tokens intact.

<figure><img src="https://2275213946-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVcvucDjYgfpsmWLerOCi%2Fuploads%2FCXF8dSnCsDO9phG7g2Fb%2FScreen%20Shot%202023-03-26%20at%2010.11.26%20PM.png?alt=media&amp;token=9780ac39-53f7-4b8c-8fd1-df13e06bcd60" alt=""><figcaption></figcaption></figure>

Imagine a scenario where a partner network is expecting a smart contract that will generate too much traffic in the partner network’s mainnet. To prevent their blockspace from being too congested, the partner network could deploy the smart contract on Saga instead. The partner network can post the Chainlet provisioning fee in Saga tokens to get the smart contract provisioned.

The Chainlet can be configured to demand end users to pay fees in the partner network tokens. This way, the end user’s interaction flow is identical to the case in which the smart contract is deployed on the partner mainnet. The fees paid by the end users follow our front-end token model and get distributed to an account owned by the partner network. A portion of these fees can be converted to Saga tokens to pay for the Chainlet subscription. The remaining balance can be configured to be distributed back to the partner’s validators and stakers in the same method as smart contracts deployed on the partner’s mainnet.

<figure><img src="https://2275213946-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVcvucDjYgfpsmWLerOCi%2Fuploads%2FEmPGVufjSDCFOBXlQPdL%2FScreen%20Shot%202023-03-26%20at%2010.11.33%20PM.png?alt=media&amp;token=7fc6f534-5969-4945-912f-c8998c570a26" alt=""><figcaption></figcaption></figure>

Saga’s token mechanism allows for accumulated transaction fees (net of Saga Chainlet fees) to accrue value to partner stakeholders. The partner also keeps their developer and end user pipeline, maintaining brand loyalty while scaling through Saga.

A second method of partnership is a revenue share between the Saga Mainnet and technology teams across the ecosystem. This structure covers cases in which developers are coming directly to Saga to build their applications. Saga is meant to be a VM agnostic chain, and numerous VM options will be available to developers who come to Saga looking for an environment to build their application in. Therefore, Saga will want strong technology partners to support and develop VM technologies on Saga. Saga can always use its Protocol Controlled Reserve to pay and incentivize these developers to continue to maintain and support their respective VM options for Saga.&#x20;

More specifically, the developer chooses a VM environment and deploys a smart contract on Saga. They then post the fee deposit that is needed to provision and maintain the Chainlet. Saga will provision a Chainlet for the developer that uses the native token of the VM for transaction fees.

<figure><img src="https://2275213946-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVcvucDjYgfpsmWLerOCi%2Fuploads%2FgwB4eB7WJiuoqd64J65V%2FScreen%20Shot%202023-03-26%20at%2010.11.38%20PM.png?alt=media&amp;token=880ecdec-efd7-470b-a123-a704101c57ec" alt=""><figcaption></figcaption></figure>

When an end user uses the application, they call the smart contract directly on the Chainlet and pay transaction fees in the native token of the VM. These fees accumulate in a wallet controlled by the developer. The developer can convert part of the fees to pay for the required bond needed to provision the Chainlet or however they see fit. Saga can also take a portion of the fees and send them to the network affiliated with the VM technology partner as a revenue share, incentivizing value accrual for the partners’ tokens.

<figure><img src="https://2275213946-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVcvucDjYgfpsmWLerOCi%2Fuploads%2Fo4CusNNRnAexQGxBwVOX%2FScreen%20Shot%202023-03-26%20at%2010.11.43%20PM.png?alt=media&amp;token=7c0b5b0f-c283-48be-8ce6-544524793e1e" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.saga.xyz/introduction/saga-overview/partnership-models.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.