From dc769ddc44984d5fd56003a30edb38d44851f242 Mon Sep 17 00:00:00 2001 From: Paul Laforgue Date: Wed, 11 Jun 2025 15:53:46 +0200 Subject: [PATCH] Network/Evm-node: recommended practices --- docs/network/evm-nodes.md | 26 +++++++++++++++++++++++++- 1 file changed, 25 insertions(+), 1 deletion(-) diff --git a/docs/network/evm-nodes.md b/docs/network/evm-nodes.md index 57a89733..7447ea01 100644 --- a/docs/network/evm-nodes.md +++ b/docs/network/evm-nodes.md @@ -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. \ No newline at end of file +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