From b3a5cd4d7560ccc88f7f6f8e44a12723ee23c3ea Mon Sep 17 00:00:00 2001 From: devorun <130918800+devorun@users.noreply.github.com> Date: Sat, 22 Aug 2026 02:00:00 +0300 Subject: [PATCH] docs: fix broken Flashblocks FAQ anchor links --- .../base-chain/api-reference/ethereum-json-rpc-api/eth_call.mdx | 2 +- .../api-reference/flashblocks-api/flashblocks-api-overview.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/base-chain/api-reference/ethereum-json-rpc-api/eth_call.mdx b/docs/base-chain/api-reference/ethereum-json-rpc-api/eth_call.mdx index dfe2a16c8..ae5cf9be4 100644 --- a/docs/base-chain/api-reference/ethereum-json-rpc-api/eth_call.mdx +++ b/docs/base-chain/api-reference/ethereum-json-rpc-api/eth_call.mdx @@ -11,7 +11,7 @@ Executes a message call immediately without broadcasting a transaction to the ne -**`eth_call "pending"` block context on Flashblocks nodes:** Block-context properties (`block.number`, `block.timestamp`, `block.basefee`) may reflect a block several behind tip due to how nodes cache historical Flashblocks. See the [FAQ](/base-chain/flashblocks/faq#why-does-eth_call-pending-report-a-block-number-several-blocks-behind-tip) for details. +**`eth_call "pending"` block context on Flashblocks nodes:** Block-context properties (`block.number`, `block.timestamp`, `block.basefee`) may reflect a block several behind tip due to how nodes cache historical Flashblocks. See the [FAQ](/base-chain/flashblocks/faq#rpc) for details. ## Parameters diff --git a/docs/base-chain/api-reference/flashblocks-api/flashblocks-api-overview.mdx b/docs/base-chain/api-reference/flashblocks-api/flashblocks-api-overview.mdx index 9382125ea..a2edd0366 100644 --- a/docs/base-chain/api-reference/flashblocks-api/flashblocks-api-overview.mdx +++ b/docs/base-chain/api-reference/flashblocks-api/flashblocks-api-overview.mdx @@ -50,7 +50,7 @@ Unique identifier for the block being built. Remains consistent across all Flash -Flashblock index within the current block. Starts at 0 (system transactions only). User transactions begin at index 1. Typically reaches 9–10 per block, but [may exceed 10](/base-chain/flashblocks/faq#can-the-flashblock-index-exceed-10-is-that-a-bug) during sequencer timing drift. +Flashblock index within the current block. Starts at 0 (system transactions only). User transactions begin at index 1. Typically reaches 9–10 per block, but [may exceed 10](/base-chain/flashblocks/faq#websocket) during sequencer timing drift.