Skip to content

Commit

Permalink
Update wording in opening description
Browse files Browse the repository at this point in the history
  • Loading branch information
franklywatson authored Dec 11, 2024
1 parent 4733bed commit 02e435e
Showing 1 changed file with 1 addition and 4 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -11,10 +11,7 @@ This guide is for running the [EVM Gateway](https://github.com/onflow/flow-evm-g
[Ethereum JSON-RPC specification](https://ethereum.org/en/developers/docs/apis/json-rpc/) and is the only node type which accepts EVM
client connections.

The EVM Gateway is an unstaked, non-participating edge node which consumes Flow protocol state from the configured Flow Access Node
and persists the indexed EVM state locally to service EVM client requests. It submits EVM transactions it receives into the Flow
network, wrapped in a Cadence transaction, and mutating EVM state when executed. Non-mutating RPC methods only query the local state
index of the gateway and are never forwarded to Access Nodes.
The EVM Gateway consumes Flow protocol state from the configured Flow Access Node and persists the indexed EVM state locally to service EVM client requests. It submits EVM transactions it receives into the Flow network, wrapped in a Cadence transaction, and mutating EVM state when executed. Non-mutating RPC methods only query the local state index of the gateway and are never forwarded to Access Nodes. It does not participate in the block production process and requires no stake.

## Who Should Run an EVM Gateway

Expand Down

0 comments on commit 02e435e

Please sign in to comment.