# Revenue

Chains earn more revenue on NodeKit. Chains earn all sequencing revenue, share in the cross-chain transaction fees originating from or going to their chain, and can elect to earn through MEV, though protective measures can be taken to prevent MEV. It is a core value of NodeKit that chains retain all prior revenue sources while unlocking the ability to earn more through MEV and cross-chain transactions in order to ensure sovereignty.

Chains can monetize on MEV by selling the right to build blocks for their chain. This is done through a similar mechanism to proposer-builder separation (PBS). On Ethereum, the builder includes a payment to the validator in the block and changes the fee recipient to their own address which is where the builder makes their profit. A similar mechanism is used to distribute the rewards for the cross-chain top-of-block fees across participating chains.

Fees generated by cross-chain interactions are distributed pro-rata to the involved chains. This mechanism allows chains to be fairly compensated for the revenue they generate through cross-chain activity generated on their chain, rather than leaking that value out to bridges.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXevA6bc0ozwW7ea3bUFbmgfFdcSpBtA8UckU44Yo6TmiyKhXInabkPm2dFMoCoCNVbbIRGgBczu69r9n-BC0iNfH-A46uZkT3qaMKSSQiwtqT63RVWfT0B9txlQy02g_6IXTqgh?key=mcWQm1Amijc8vua1uSfrnrz1" alt=""><figcaption></figcaption></figure>


---

# 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://nodekit.gitbook.io/nodekit-documentation/core-advantages/revenue.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.