Methods · Safety · Documentation
FRB research methods and reference materials
Use this page as the official index for FRB measurement methods, reusable templates, public policies, and technical guides. It does not publish a product-wide performance dataset or a universal provider ranking.
Linkable summary
What FRB publishes
FRB publishes versioned measurement methods, security and simulation templates, and public product boundaries that researchers can inspect and reproduce without relying on unsupported performance claims.
Downloadable research resources
These resources include blank methods and templates plus a small dated observation. They are not user results or a product performance record.
Dated observation · 19 August 2026
First public RPC/WSS observation
This small window validates the collection format across documented public Ethereum endpoints. HTTP and WSS phases are reported separately, and the raw rows remain downloadable.
This is one observation from one development host. It is not a universal provider ranking, an FRB product benchmark, or evidence of transaction inclusion, protection, or profitability.
- Run ID
- 2026-08-19T105333457Z
- Client environment
- Windows 10 x64 · Node v24.14.1
- Network egress
- Region not independently verified
HTTP eth_blockNumber observations
| Provider | Successful / attempts | Median | Observed p95 | Maximum observed head lag (blocks) |
|---|---|---|---|---|
| dRPC public | 5 / 5 | 106.50 ms | 121.60 ms | 0 |
| PublicNode | 5 / 5 | 107.03 ms | 113.96 ms | 0 |
| 1RPC public | 5 / 5 | 247.66 ms | 438.19 ms | 1 |
WSS newHeads observations
| Provider | Connection open | Subscription ack from start | Events received / requested |
|---|---|---|---|
| dRPC public | 171.09 ms | 247.30 ms | 2 / 2 |
| PublicNode | 163.03 ms | 242.94 ms | 2 / 2 |
Five HTTP samples and two WSS events per eligible endpoint are enough to validate the harness, not to establish a durable percentile or trend. Provider routing, chain conditions, connection reuse, and public endpoint policies can change after this window.
Second independent collection window
A second low-rate window was collected about seven hours later with the same harness and settings. Its raw rows are published separately so developers can inspect failures and reproduce the method.
Both windows were collected on the same date from the same host. They validate repeatability of the collection workflow, not a multi-day trend, provider ranking, uptime claim, or product benchmark.
2026-08-19T175556292Z
Independent follow-up · 29 August 2026
The same low-rate harness and settings were used again ten days after the first windows. Successful and failed raw rows are published separately so developers can compare dates and reproduce the method.
This different-date window adds a time-separated observation, but all three small windows still come from one development host. They do not establish a durable trend, provider ranking, uptime claim, or product benchmark.
- Run ID
- 2026-08-29T124945760Z
- Client environment
- Windows 10 x64 · Node v24.14.1
HTTP eth_blockNumber observations
| Provider | Successful / attempts | Median | Observed p95 | Maximum observed head lag (blocks) |
|---|---|---|---|---|
| dRPC public | 5 / 5 | 100.72 ms | 106.88 ms | 0 |
| PublicNode | 5 / 5 | 89.81 ms | 107.09 ms | 0 |
| 1RPC public | 3 / 5 | 321.23 ms | 359.28 ms | 1 |
WSS newHeads observations
| Provider | Connection open | Subscription ack from start | Events received / requested |
|---|---|---|---|
| dRPC public | 138.92 ms | 216.38 ms | 2 / 2 |
| PublicNode | 147.06 ms | 228.63 ms | 2 / 2 |
Reproducible methods
Versioned WSS/RPC and provider-comparison methods with reusable observation templates and explicit limitations.
Public trust references
Published telemetry, security, fee, refund, release, and incident-response boundaries with clear contact routes.
Neutral education
Technical explainers that distinguish documented facts, local measurements, simulations, and economic outcomes.
Methods for researchers
Use the published methodology and templates to collect observations in your own environment. FRB does not claim that one provider is universally faster or that endpoint acceptance predicts inclusion or profit.
- Review the Flashbots measurement method with the Polygon and BNB measurement pages before defining a comparable test.
- Reference our WSS latency test and gas calculator when citing infrastructure assumptions.
- Use the measurement framework with the downloadable templates above to retain your own raw evidence.
FRB reference layers and external evidence
| Topic | FRB contribution | Other ecosystem references |
|---|---|---|
| Measurement methods | Versioned methodology, a raw-observation CSV template, and a browser-side WSS test. No universal provider ranking is published. | Official provider documentation and independently reproduced observations. |
| Policy transparency | Telemetry, security, fees, refunds, releases, risk, and vulnerability reporting are documented publicly. | Official policy, security, status, and release documentation from each provider. |
| Education and playbooks | MEV 101, simulation, private routing, chain guides, and due-diligence checklists with stated limitations. | Primary protocol documentation, research papers, and maintained developer guides. |
| Reusable templates | WSS/RPC observations, simulation review, security permissions, and provider-comparison templates. | Operator-owned raw data and reproducible aggregation code. |
For comparisons, verify every provider against its current official documentation and keep local observations separate from documented facts.
Reference statements and limits
The statements below summarize the linked public materials. Editors should verify the source and review date before publication.
- FRB publishes a versioned WSS/RPC measurement method and raw-observation template so operators can reproduce tests in their own environment.
- FRB documents telemetry, security, fees, releases, refunds, and risk boundaries on public pages.
- FRB simulation and security templates separate pre-execution checks from claims about inclusion or economic outcomes.
Where to link next
- Need a measurement method? Start with the MEV measurement hub and use the raw-observation template above.
- Writing about policy? Pair this page with the telemetry policy, security overview, and responsible disclosure.
- Comparing tooling vendors? Use the MEV bot comparison and chain-specific guides such as Polygon MEV or BNB MEV.
- For implementation context, use the Knowledge Base and Docs pages rather than unpublished outreach material.
Review FRB reference materials
Linking to this page gives readers a source index and explicit limitations; it is not evidence of performance, inclusion, protection, or profitability.
If you need quotes or fact checks, email support@ai-frb.com and mention "ecosystem research".