Evidence before numbers
If a result cannot be rerun, it is not a benchmark.
A useful execution measurement identifies the release, network, provider, test context and raw observations. Endpoint receipt, simulation success, inclusion, finality and economic outcome are different events. This page defines evidence requirements; it does not present a measured FRB-wide latency, inclusion rate or trading result. Simulation estimates behavior for specified inputs and state, not future results.
What would be required to publish a metric
| Metric | Minimum evidence | FRB evidence status |
|---|---|---|
| RPC/WSS latency | Endpoint, region, transport, clock, sample count, percentiles, raw observations and test time | No FRB-wide benchmark published |
| Bundle inclusion | Provider, network, target rules, observation window, accepted and landed definitions, and raw status records | No FRB-wide benchmark published |
| Simulation agreement | Fork source, block, state assumptions, transaction set, exclusions and final receipts | No FRB-wide benchmark published |
| Strategy outcome | Reproducible strategy definition, all costs, failed paths, market window, sample selection and raw data | Not presented as a product performance claim |
Reproducible measurement protocol
- Freeze the FRB release, configuration, dependency versions and checksum.
- Define the network, endpoint, region, transport, hardware and clock source.
- Publish the request or transaction shape and all inclusion or exclusion rules.
- Retain raw observations before aggregation; remove wallet and user identifiers before sharing.
- Report sample count, observation window, failures and percentile methodology.
- Separate endpoint receipt, simulation success, inclusion, finality and economic outcome.
- Publish limitations and enough non-sensitive inputs for an independent rerun.
Claims this page does not establish
- Expected profit or monthly income
- Product-wide win or success rates
- Inclusion figures without provider status data
- Latency figures without location and transport context
- Competitor rankings without a common test method
Provider documentation
Provider APIs define receipt and status semantics. Their documentation is not an FRB-wide performance measurement.
Measure your own endpoint context
The WSS tool reports observations from the selected test context. Record endpoint, region, time, transport and sample definition before comparing results.
Open the WSS measurement tool