# Gas

Gas costs are calculated dynamically based on operation complexity. More complex operations (multiple recipients, ranges, etc.) consume more gas.

For detailed gas calculations and optimization strategies, see the implementation in the [precompile code](https://github.com/BitBadges/bitbadgeschain/tree/evm-poc/x/tokenization/precompile).

## General Principles

* **Base costs** apply to all operations
* **Per-element costs** for arrays (recipients, ranges, etc.)
* **Query operations** are generally cheaper than transactions
* **Batch operations** are more gas-efficient than multiple individual calls

## Utility Method Gas Costs

Utility helper methods have low fixed gas costs:

| Method                      | Gas Cost | Description                      |
| --------------------------- | -------- | -------------------------------- |
| `convertEvmAddressToBech32` | 100      | Convert EVM to bech32 address    |
| `convertBech32ToEvmAddress` | 100      | Convert bech32 to EVM address    |
| `rangeContains`             | 200      | Check if value is in range       |
| `rangesOverlap`             | 200      | Check if two ranges overlap      |
| `searchInRanges`            | 500      | Search value in JSON range array |
| `getBalanceForIdAndTime`    | 500      | Get balance from JSON balances   |
| `getReservedListId`         | 300      | Get reserved list ID for address |

## Optimization Tips

* Minimize the number of recipients when transferring
* Consolidate token ID and ownership time ranges when possible
* Use direct return methods (`getBalanceAmount`, `getTotalSupply`) instead of protobuf-encoded methods when you only need amounts
* Batch multiple operations in a single transaction when possible
* Use utility helper methods (`rangeContains`, `searchInRanges`) for on-chain validation instead of implementing range logic in Solidity