From 02e435e6d86e4526650053c34e99267fa8f337ab Mon Sep 17 00:00:00 2001 From: j pimmel Date: Wed, 11 Dec 2024 09:15:56 -0800 Subject: [PATCH] Update wording in opening description --- .../access-onchain-data/evm-gateway/evm-gateway-setup.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/docs/networks/node-ops/access-onchain-data/evm-gateway/evm-gateway-setup.md b/docs/networks/node-ops/access-onchain-data/evm-gateway/evm-gateway-setup.md index 92f4b26918..8e992337b0 100644 --- a/docs/networks/node-ops/access-onchain-data/evm-gateway/evm-gateway-setup.md +++ b/docs/networks/node-ops/access-onchain-data/evm-gateway/evm-gateway-setup.md @@ -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