> For the complete documentation index, see [llms.txt](https://docs.fantom.foundation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fantom.foundation/funding/gas-monetization.md).

# Gas Monetization

{% hint style="info" %}
[Apply for your app to participate in Gas Monetization](https://forms.gle/xjSa13zT44iKQwAp8).
{% endhint %}

The [Gas Monetization program](https://earngas.fantom.network/) offers apps a 15% share of the gas fees they generate and aims to provide high-quality apps with a sustainable income, retain talented creators, and support network infrastructure.

With Gas Monetization, we seek to foster a thriving ecosystem for builders, similar to the ad-revenue model on traditional web platforms.

## Participate in Gas Monetization

Approval to the Gas Monetization program is at our discretion. [Apply to participate in Gas Monetization](https://forms.gle/xjSa13zT44iKQwAp8).

Upon approval to participate in the program, apps will begin to earn 15% of the gas fees they generate. The FTM earned through Gas Monetization can be used at the apps' discretion.

## Quarterly Bonus

Every quarter, the top 12 apps on Opera that generated the most gas will receive a bonus. These 12 projects are divided equally into four tiers that determine the amount of FTM they receive:

* Tier 1 (top three projects): 40% of FTM
* Tier 2 (next three projects): 30% of FTM
* Tier 3 (next three projects): 20% of FTM
* Tier 4 (final three projects): 10% of FTM

The quarterly bonus comes from the 15% deducted from transaction fees of apps not participating in Gas Monetization. While [15% of all transaction fees](/technology/transaction-fees.md) on Opera are allocated to the Gas Monetization program, the fees from non-participating apps are pooled and distributed as the quarterly bonus.

## Double-Spend Dilemma

In Gas Monetization, double counting is prevented by accurately tracking gas consumption within the EVM. The system traces all internal calls in a transaction and splits the reward based on the gas each sub-operation consumes.

This ensures that the sum of rewards across different projects never exceeds the total gas fee. An example is given below.

* A trade consumes 100,000 units of gas with a total GasM fee of 0.017 FTM.
* Inside this transaction, there are operations related to two projects: Project A and Project B.
* Project A, the DEX aggregator, is responsible for consuming 37,000 units of gas, while Project B, the liquidity pool on the DEX that the aggregator interacts with, uses 63,000 units of gas.
* The total reward is split based on the gas consumption:
  * Project A receives 37% of the fee (0.00629 FTM).
  * Project B receives 63% of the fee (0.01071 FTM).
* The total reward still adds up to 100% of the 0.017 FTM GasM fee, ensuring no over-distribution.

## Terms & Conditions

We reserve the right to suspend rewards to participating apps for any reason deemed necessary at its sole discretion, including fraudulent user activity or the overall well-being of the Opera ecosystem.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.fantom.foundation/funding/gas-monetization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.