Pre-execution intent and post-execution metadata are not the same stream. This run measures both on the same host, same filter, and same public TLS path so the lifecycle gap is visible in numbers instead of slides.
The experiment in one screen
| Field | Value |
|---|---|
| Arms | SubscribeDeshred vs Processed gRPC |
| Method | signature race |
| Window | 5m 18s |
| Captured | 2026-07-11 · 07:56 UTC |
| Route | rpc edge public TLS · Frankfurt |
| Matched signatures | 55,424 |
| Target | 50,000 |
| Profile | Pump AMM transactions |
Operator-host lifecycle measurement, not a neutral provider ranking. Both streams used the same Pump AMM filter and public rpc edge TLS endpoint. Client monotonic receipt time is authoritative.
Full tables: benchmark report.
Who saw the signature first
| Stream | First detections | First rate | p50 lag | p95 lag | p99 lag |
|---|---|---|---|---|---|
| SubscribeDeshred | 55,382 | 99.92% | 0.0 ms | 0.0 ms | 0.0 ms |
| Processed gRPC | 42 | 0.08% | 4.64 ms | 16.42 ms | 33.10 ms |
Latency for each stream is the non-negative arrival lag from the first stream observed for that signature. Deshred almost always wins first detection; processed lag is how far behind post-execution metadata sits in this window.
Signed lifecycle delta
The signed delta preserves how much earlier deshred arrived (negative means deshred first):
| Percentile | Signed delta (ms) |
|---|---|
| p50 | -4.64 |
| p90 | -1.94 |
| p95 | -1.62 |
| p99 | -1.09 |
| p99.9 | -0.12 |
How to read without over-claiming
- Deshred is pre-execution intent - no logs, no account writes, no final status.
- Processed gRPC is post-execution metadata - use it to confirm and enrich.
- This is one host, one filter, one window. Reproduce with the open tools if you need your own filter set.
- Methodology: stream methodology.
Harness: solbench.
Next
Open the full report and the reproduce guide.
All runs: /benchmarks.
To stream both surfaces in production, get started or request self-serve on app..