Skip to content

WIP: Network/Evm-node: recommended practices #320

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.

Sign up for GitHub

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

Open
phink wants to merge 1 commit into
base: main
Choose a base branch
from
Open

WIP: Network/Evm-node: recommended practices #320

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 25 additions & 1 deletion docs/network/evm-nodes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -332,4 +332,28 @@ curl -X POST -H 'Content-Type: application/json' --data '{"jsonrpc":"2.0","metho

## Stopping the node

The EVM node respects SIGTERM and exits cleanly when stopped, so you can stop it in any way that you would ordinarily stop a program on your system.
The EVM node respects SIGTERM and exits cleanly when stopped, so you can stop it in any way that you would ordinarily stop a program on your system.

## Recommended practice

### Default Restart Policy

We recommend applying default restart policy for each service with
automatic recovery scenarios in case of failure.

### Health checks

Based on Etherlink architecture, the following health checks should be performed:

##### Smart Rollup Node Health Checks

1. **RPC Endpoint Health**
- **Endpoint**: `/health`
- **Purpose**: Returns health status information for the rollup node

##### EVM Node Health Checks

1. **RPC Endpoint Health**
- **Method**: `eth_blockNumber`
- **Purpose**: Verify EVM node is operational
- **Expected**: Returns current block number