Production Guidance
Sizing depends on network throughput and assertion complexity. Use these guidelines as a starting point and scale based on load testing:| Component | Guidance |
|---|---|
| CPU | High-core, modern server CPU |
| RAM | Sufficient memory for state caches and execution |
| Storage | Fast local SSD with headroom for growth |
| Network | Low-latency, high-bandwidth link to the block builder |
CPU
The sidecar requires significant compute for assertion execution. Use 32 physical cores with AMD Zen 3 performance equivalent or higher.Memory
Allocate enough RAM for state caches and execution overhead. Exact requirements vary by chain size and assertion complexity.Storage
Use fast local (not networked) SSDs to keep I/O latency low. Budget for sustained IOPS and headroom for state growth.Networking
Keep round-trip time (RTT) to the block builder low by colocating in the same availability zone or cluster. Co-scheduling on the same Kubernetes node or pod is ideal. Key requirements:- Low-latency, high-bandwidth link between block builder and sidecar
- Prefer private networking; avoid routing over the public internet
- Stable egress to chain RPC and assertion data endpoints