Loading…
Loading…
Probable cause web3signer-l2
web3signer signs for the sequencer (liveness txs), the coordinator (blob and finalization submissions) and the postman. It loads its 4 keys from Vault at start. If Vault was not reachable when it started (after a node restart Vault starts later and needs unsealing), it runs with fewer keys and never reloads them (INC-11 A12).kubectl -n vault exec vault-0 -- vault statuskubectl -n lineth-l2 rollout restart deployment web3signerKeys loaded by the L2 web3signer:
max(signing_signers_loaded_count{job="l2-web3signer"})Is the L2 still producing blocks:
increase(ethereum_blockchain_height{job="l2-sequencer"}[3m])Web3signer key loading:
{namespace="lineth-l2", pod=~"web3signer-.*"} |~ "(?i)vault|key|loaded|error"If Vault is sealed and cannot be unsealed, page the IC: signing for the whole L2 depends on it. The unseal keys are in the break-glass procedure, not in this runbook.
Seen in INC-2026-10-11-11 · SLOs block-production, settlement-freshness · owner s1ns3nz0