A clear numerator
Committed signed transactions are distinct from requests received, synthetic counter increments, rejected transactions, or dropped work.
Understand Sigil’s committed-throughput measurements, the workload behind them, and the difference between a benchmark and current network health.
Illustrated coordination. No live network activity.
Ingress counters can make a system look fast before it has completed the work. Sigil’s Velocity measurement model counts signed user transactions that execute into lane receipts and roots, with the environment and observation window kept alongside the result.
Committed signed transactions are distinct from requests received, synthetic counter increments, rejected transactions, or dropped work.
The worker count, lane count, slot configuration, and commitment hierarchy describe the resources that produced a result.
Slot latency, block interval, and end-to-end finality are different measurements. Each should name its start, finish, percentile, and observation window.
Invalid, dropped, and lagging work affect the interpretation. A performance summary should expose those outcomes rather than count only the successful path.
The same historical report distinguished functional runtime performance from incomplete public-launch and independent-operator evidence. Throughput alone does not establish either.
No. It describes a particular workload and deployment. Contract execution, contended state, different hardware, and different network conditions need their own measurements.
Use the network status surface for current observations. Treat stale or unavailable telemetry as unknown rather than replacing it with a historical benchmark.