Skip to content

docs(finality): align flashblock reorg rate with <0.1% target - #2121

Open
youssefea wants to merge 5 commits into
masterfrom
docs/devrel-859-flashblock-reorg-rate-docs-disagree-vs
Open

youssefea wants to merge 5 commits into
masterfrom
docs/devrel-859-flashblock-reorg-rate-docs-disagree-vs

Conversation

@youssefea

Copy link
Copy Markdown
Contributor

What changed? Why?

Closes Base Knowledge Base gap gap-20260924-flashblock-reorg-rate-docs-disagree-vs: "What is the current Flashblock (preconfirmation) reorg rate on Base Mainnet: <0.1% or <0.001%?" (gaps log, DEVREL-859).

Transaction Finality said Flashblocks reorg "less than 0.001% of the time". Throughput and Limits lists the reorg rate as < 0.1%, and the Flashblocks FAQ calls < 0.1% a target. This PR changes the Flashblock Inclusion step in docs/specifications/transactions/transaction-finality.mdx to call < 0.1% a target and link to Throughput and Limits. It does not state an observed Mainnet rate.

Notes to reviewers

  • Primary sources (this repo, master):
    • docs/specifications/transactions/throughput-and-limits.mdx, Flashblock Performance table: "Reorg rate | < 0.1%"
    • docs/specifications/flashblocks.mdx, FAQ "How Frequently Do Flashblock Reorgs Happen?": "Base targets a Flashblock reorg rate of < 0.1%"
  • Owner confirmation needed before merge (Base Flashblocks/protocol team): please confirm that < 0.1% is the right public figure to present as a target. Also confirm whether the earlier < 0.001% was a measured Mainnet rate that should be published separately, with its definition and measurement window.
  • This replaces the Transaction Finality reorg-rate part of docs: sync upgrade, RPC, and node operator pages after Cobalt #2092, which is unmerged. This PR does not include the other changes in docs: sync upgrade, RPC, and node operator pages after Cobalt #2092.

How has it been tested?

  • node scripts/lint-mdx.js --files-from=<changed files>: 0 errors, 0 warnings
  • node scripts/validate-docs-structure.js: fails only because of a redirect that was already broken (/upgrades/denim/eip-8130 -> missing /specifications/native-account-abstraction). This PR does not cause it.
  • The new internal link /specifications/transactions/throughput-and-limits#flashblock-performance resolves: the page is in docs/docs.json and has a ## Flashblock Performance heading.

Screenshots

N/A (text-only change)

Generated with Toshi

@mintlify

mintlify Bot commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
base 🟢 Ready View Preview Oct 19, 2026, 8:42 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@cb-heimdall

Copy link
Copy Markdown
Collaborator

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 0
Sum 1

@linear

linear Bot commented Oct 14, 2026

Copy link
Copy Markdown

DEVREL-859

@youssefea youssefea added the BKB Base Knowledge Base gap fix label Oct 19, 2026
@soheimam
soheimam marked this pull request as draft October 19, 2026 20:12
@soheimam
soheimam marked this pull request as ready for review October 19, 2026 20:12
@github-actions

github-actions Bot commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

Docs review

Risk: Low (one AI review) · risk: low · shadow mode, not enforced

  • small change with no risk signals

Verdict: Fits, with changes · reviewed 65c20d0 with gpt-6-luna

This updates the Flashblock inclusion note on the live Transaction Finality page, which is an appropriate place for the information. The wording presents the figure as a target rather than an observed Mainnet rate, consistent with the supplied facts; add terminal punctuation to the changed sentence.

Suggestions

  1. Add terminal punctuation (writing, docs/specifications/transactions/transaction-finality.mdx L28) — suggestion posted inline
    The changed sentence has no ending punctuation. Add a period to make the bullet read as a complete sentence.
    Evidence: The Base writing guidelines call for clear, direct sentences; the neighboring bullet on line 29 ends with a period.
What the reviewer checked
Page Placement Index section Neighbors read
docs/specifications/transactions/transaction-finality.mdx Live in navigation not in llms-full.txt 0

Links added: /specifications/transactions/throughput-and-limits#flashblock-performance (live)

Advisory review from the Docs PR review workflow (run). It does not approve, block, or edit this PR. Add the skip-ai-review label to turn it off for this PR.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested edits from the docs review. Each one is optional; apply it with "Commit suggestion" if you agree.

<Accordion title="Under 0.001% Probability of a Reorg.">
* Flashblocks reorg less than 0.001% of the time
<Accordion title="Target Reorg Rate Under 0.1%">
* Base targets a Flashblock reorg rate of less than 0.1%, as listed in [Throughput and Limits](/specifications/transactions/throughput-and-limits#flashblock-performance)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add terminal punctuation

The changed sentence has no ending punctuation. Add a period to make the bullet read as a complete sentence.

Suggested change
* Base targets a Flashblock reorg rate of less than 0.1%, as listed in [Throughput and Limits](/specifications/transactions/throughput-and-limits#flashblock-performance)
* Base targets a Flashblock reorg rate of less than 0.1%, as listed in [Throughput and Limits](/specifications/transactions/throughput-and-limits#flashblock-performance).

This branch was successfully deployed

1 active deployment
staging - docs — 65c20d09 Deployed Oct 19, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

BKB Base Knowledge Base gap fix risk: low small changes, easy to merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants