Skip to content

Commit 7d71837

Browse files
Document block difference between go-ethereum and Flow (#1177)
* Add block difference info * Add GH issue * Tidyup * Tidyup * Add missing endpoint
1 parent ba10ae1 commit 7d71837

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

docs/evm/how-it-works.md

+5
Original file line numberDiff line numberDiff line change
@@ -66,6 +66,11 @@ For extra protection on the EVM side, the gateway software is designed to be ful
6666

6767
[EIP-1559](https://eips.ethereum.org/EIPS/eip-1559) is supported by the Flow EVM and Gateway nodes can decide on the inclusion of the transactions based on the tips or gas fees. The parameters for the EIP 1559 are adjustable by the Flow network. Currently, the base fee is set to zero, as EVM transactions are wrapped by the Flow transactions.
6868

69+
## Block hash calculation difference
70+
71+
Developers using the GoLang Ethereum client to integrate with Flow will find that the block hash calculated by the Flow EVM RPC endpoints `eth_getBlockByNumber` and `eth_getBlockByHash` differ from the hash calculated locally by `go-ethereum`. This is due to underlying
72+
differences in the `Block` implementation to support EVM on Flow. For more information see https://github.com/onflow/flow-evm-gateway/issues/719.
73+
6974
## Opcodes
7075

7176
Flow EVM supports opcodes listed [here](https://www.evm.codes/?fork=cancun), except for the following changes.

0 commit comments

Comments
 (0)