Skip to content

docs: tw919-batch-poster-recovery-and-troubleshooting#3415

Open
pete-vielhaber wants to merge 9 commits into
masterfrom
tw790
Open

docs: tw919-batch-poster-recovery-and-troubleshooting#3415
pete-vielhaber wants to merge 9 commits into
masterfrom
tw790

Conversation

@pete-vielhaber

Copy link
Copy Markdown
Contributor

Thank you for contributing to our docs!

Please fill out the form below to ensure your doc gets quickly approved and merged.

Description

  • Adding batch poster operations: recovery
  • Expanding batch poster troubleshooting

Document type

  • Gentle introduction
  • Quickstart
  • How-to
  • Concept
  • FAQ
  • Troubleshooting
  • Reference
  • Third-party content
  • Codebase changes
  • Not applicable

Checklist

  • I have read the CONTRIBUTE.md guidelines
  • My changes follow the style conventions outlined in CONTRIBUTE.md
  • I have used sentence-case for titles and headers
  • I have used descriptive link text (not "here" or "this")
  • I have separated procedural from conceptual content where appropriate
  • I have tested my changes locally with yarn start or yarn build
  • My code follows the existing code style and conventions
  • I have added/updated frontmatter for new documents
  • I have checked for broken links
  • I have verified that my changes don't break the build
  • Third-party docs only: Do you agree to the third-party content policy outlined within CONTRIBUTE.md?
    • Yes
    • Not applicable

@vercel

vercel Bot commented Jun 26, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
arbitrum-docs Ready Ready Preview Jun 29, 2026 2:32pm

Request Review


#### `error getting max time variation on L1 bound block; falling back on latest block`

- [WARN]—`unknown L2 block bound config value; falling back on using finalized`

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 change
- [WARN]`unknown L2 block bound config value; falling back on using finalized`
- [ERROR]`unknown L1 block bound config value; falling back on using finalized`


In short: _queue intact → resume in-flight; queue gone → rebuild cleanly from L1_.

## Storage backends and what survives a restart

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.

There is a Queued transaction database selection section in batch-poster.mdx, there should be some overlap, should we delete one?


- **Parent-chain reorg, revert polling**: if the chain went backward (`nextRevertCheckBlock > blockNum`) it resets to re-check; the >100-block gap warning fast-forwards and skips.
- **Mempool nonce-gap avoidance**: before sending a transaction of a different type than its predecessor (or whose predecessor isn't yet reorg-resistant), it checks `NonceRbfSoftConfs` deep and, if the nonce exceeds the reorg-resistant count, leaves the transaction queued—`"DataPoster is avoiding creating a mempool nonce gap"`—rather than risk a gap a reorg would expose.
- **`l1-block-bound`** (`safe`/`finalized`/`latest`/`ignore`) and **`reorg-resistance-margin`** (default 10m) keep batches from referencing L1 blocks that could reorg out (see `posting-cadence-and-lifecycle.md` and `config-flags.md`).

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.

I don't find those 2 files, are them still pending?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants