Description
For testing and debugging purposes, we need the ability to halt the blockchain on the devnet setup across all nodes without completely shutting down the failed skaled instance.
Currently, when a node fails, it exits with a 200 status code, which tears down the container/process and terminates the RPC server. This prevents us from inspecting the node's state and comparing block information via RPC.
We need a "Freeze" mode where the blockchain stops processing new blocks, but the skaled process remains alive, and its RPC server stays accessible in Read-Only mode.
Expected Behavior
- The blockchain consensus/block production stops across all devnet nodes
- The failed skaled node does not exit (no shutdown, no container stop)
- The RPC server on the failed node remains up and running
- The RPC server rejects state-changing transactions but successfully responds to read requests (e.g., eth_getBlockByNumber, eth_getTransactionReceipt, etc.), allowing block info comparison
Technical Requirements
- skaled/consensus changes
- node config changes for ENV_TYPE= devne/qanet
Description
For testing and debugging purposes, we need the ability to halt the blockchain on the devnet setup across all nodes without completely shutting down the failed skaled instance.
Currently, when a node fails, it exits with a 200 status code, which tears down the container/process and terminates the RPC server. This prevents us from inspecting the node's state and comparing block information via RPC.
We need a "Freeze" mode where the blockchain stops processing new blocks, but the skaled process remains alive, and its RPC server stays accessible in Read-Only mode.
Expected Behavior
Technical Requirements