Skip to content

docs: tw711-bold-tuning - #3501

Open
pete-vielhaber wants to merge 15 commits into
masterfrom
tw711
Open

docs: tw711-bold-tuning#3501
pete-vielhaber wants to merge 15 commits into
masterfrom
tw711

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

  • This encapsulates work from TW-711, TW-712, TW-715. All around BoLD tuning, config, 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

Additional Notes

pete-vielhaber and others added 12 commits July 29, 2026 11:28
Covers the four outstanding audit gaps: test chain configuration
(TW-712 plus testnet parameters), txpool and eth_getLogs RPC coverage
(TW-713), the chain-operator error index (TW-715), and RollupCreator to
TokenBridgeCreator sequencing.

Parameter values are grounded in OffchainLabs/nitro at a618155 rather
than inferred. Two findings corrected the original audit framing: Nitro
imposes no eth_getLogs block-range cap of its own, and
EnableFastConfirmation is the Safe-multisig fast-withdrawals feature
rather than a test speedup.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The nitro-sourced value tables need SME confirmation before merge.
Carry that flag as an HTML comment above each affected table rather than
only in the PR description, so it survives merge and is visible to
anyone editing the file.

Uses the HTML comment form to match existing convention in this repo
rather than the JSX form; both parse in MDX.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The error index links to 36 error headings. Docusaurus auto-slugs several
of them past 100 characters, and onBrokenAnchors is 'warn', so a reworded
heading would break the index silently. Explicit IDs keep those links
short and stable.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Routes 36 error and log messages to the guides that already explain
them, grouped by component. Carries no resolution steps of its own so it
cannot drift out of step with those guides.

Scoped to batch poster and validator errors. Stylus, node running, and
bridging are linked out to rather than duplicated.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Covers shortening assertion confirmation on non-production chains and
which parameters differ on testnets. Values read from OffchainLabs/nitro
at a618155 and flagged inline for SME confirmation.

Distinguishes this from fast withdrawals, which uses a similarly named
flag but is a production trust assumption rather than a test speedup.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
txpool is absent from Nitro's default HTTP namespaces, so txpool_contentFrom
needs --http.api to include it, and pool semantics differ under a sequencer.

Nitro imposes no eth_getLogs range cap; observed limits are provider-imposed.
The 499 and 5000 figures in Nitro are its own client-side chunking against
parent chain endpoints, not limits on callers.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Both factories were documented separately but nothing stated that they run
in order, that the token bridge depends on the inbox existing, or why the
custom gas token allowance is needed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
CLAUDE.md prefers "bond" over "stake" for proposing. Reworded to describe
what the flag actually controls, which avoids the term entirely.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Aug 3, 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 Aug 6, 2026 12:47pm

Request Review

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.

1 participant