Multi-Endpoint Comparison
This guide configures one suite to compare multiple endpoints on the same chain.
Use cases
Section titled “Use cases”Multi-endpoint comparison is useful when you need to:
- compare self-hosted client vs managed provider
- compare different client implementations
- compare canary endpoint vs stable production endpoint
Prerequisites
Section titled “Prerequisites”Before setting up comparisons, you need a chain with at least two endpoints.
- chain exists
- at least two endpoints added
- one endpoint selected as reference
See Create a Chain and Add Endpoints.
Step 1: Prepare endpoints
Section titled “Step 1: Prepare endpoints”Start by ensuring your endpoints are properly tagged so you can tell results apart.
referencecandidateclient:reth,client:nethermindenv:prod
Step 2: Create comparison suite
Section titled “Step 2: Create comparison suite”Now create a suite that tests all endpoints and compares their outputs.
- Go to Test Suites and click Add Suite .
- Choose a comparison-capable template.
- Select reference endpoint.
- Select candidate endpoints.
- Set interval schedule (for example 300s).
- Save.
Step 3: Run and inspect verdict
Section titled “Step 3: Run and inspect verdict”Trigger a run and look at the comparison verdict to see how endpoints stack up.
Interpret verdict:
pass: expected paritywarn: inspect driftfail: investigate mismatch immediately
Operational checklist
Section titled “Operational checklist”A few practices that keep comparisons useful over time.
- keep reference endpoint stable and trusted
- limit candidate count per suite for faster isolation
- separate correctness and performance-focused suites
- document threshold rationale in your repo