-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add EVM Gateway node ops section and main page #1035
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@nialexsan - at some point could you please push this to a temporary vercel instance so we can review if the nav structure came out ok. Thanks |
Yes thanks @nialexsan ! |
[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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do you say its non-participating
? IMO, it participates by sending transactions. It doesn't participate in block production directly but does so indirectly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll correct it to say it isn't a participant in block production, would that work?
docs/networks/node-ops/access-onchain-data/evm-gateway/evm-gateway-setup.md
Outdated
Show resolved
Hide resolved
…eway-setup.md Co-authored-by: Vishal <[email protected]>
Adds a new section to the Node Operations section of public docs covering EVM Gateway. This consolidates disparate EVM gateway doc info that was variously provided at: