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

# Gas fee

The gas fee on Goshen comprise of:

1. **Transaction execution**: same as the L1 gas fee which covers computation and storage consumed when executing smart contracts. The EVM opcode gas costs are the same as on Ethereum (Istanbul hard fork).
2. **Data publishing**: Transactions are collected by the Sequencer and published to L1 in batches. The fee generated in this process must be paid by users who initiate the transactions.

We aim to lower the transaction execution fee a 100 times compared to what it is on Ethereum. The Sequencer only accept transactions with gas prices more than 1/100 of Ethereum gas price.

On Ethereum, the "intrinsic gas" already includes the transaction data fee. Hence on Goshen, data fee is charged 100 times as much to cover the cost for data publishing on Ethereum. Therefore, the gas fee mechanism remains the same as that of Ethereum, only with some tuned parameters that adjust the weight of different factors. The web3 APIs are still compatible with Ethereum, you can call `eth_estimateGas` and `eth_gasPrice` to estimate the gas consumption and price for a transaction.

With other words; execution fee is 100 times lower than Ethereum, but data fee remains the same.

## Enqueue transaction fee

Transactions sent directly from Ethereum to L2 do not need the Sequencer to publish original data, so there's no data publishing fee for this. Currently the default gas price is 1 Gwei.


---

# 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.goshen.network/dev-docs/gas-fee.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.