# Bridging Gini to EVM chains: Seamless Integration into the Kalp Ecosystem

Once Gini tokens are minted on Kalp, they are bridged to the EVM networks using the Permissioned Kalp Bridge, ensuring smooth introduction of the Kalp ecosystem to a larger web3 audience.

## **Gini as Fuel for Kalp’s Subnetworks and DApps**

**Gini** is the **primary token used for transaction fees (gas) across all Kalp subnetworks, public network and applications on the Kalp network**. These fees are not only essential for the smooth operation of the network, but they also play a key role in incentivizing node operators and participants.

* **Distribution of Gas Fees**: All node owners maintaining the network’s infrastructure, whether they operate on specific subnetworks or the broader Kalp network, are rewarded proportionally based on the number of transactions processed on their subnets. This means that you earn Gini tokens based on the transaction volume your infrastructure/subnetwork supports.

  This fair and unbiased reward system ensures that both small-scale and large-scale participants in the network benefit from their contributions, creating a sustainable and incentivized ecosystem. As more transactions occur across Kalp’s diverse subnetworks, node operators receive consistent rewards, encouraging continued participation and maintaining the health and scalability of the network.


---

# 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://kalp-network.gitbook.io/whitepaper/a-permissioned-multi-chain-ecosystem-purpose-built-to-serve-as-regulatory-compliant-digital-public-i/introduction/kalp-a-unifying-solution/gini-the-utility-token-fueling-the-kalp-network/bridging-gini-to-evm-chains-seamless-integration-into-the-kalp-ecosystem.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.