Skip to content

Update PathDB docs (mar2026)#3184

Merged
leeederek merged 13 commits intomasterfrom
derek/clarify-pathdb
Apr 2, 2026
Merged

Update PathDB docs (mar2026)#3184
leeederek merged 13 commits intomasterfrom
derek/clarify-pathdb

Conversation

@leeederek
Copy link
Copy Markdown
Member

Thank you for contributing to our docs!

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

Description

This PR:

  • Clarifies that PathDB is our recommendation for archive nodes
  • Adds details around the state of PathDB snapshots for full nodes
  • Clarifies the pruning modes and what they do, including a key difference in that PathDB only retains the last 24hrs worth of state by default (and online, auto prunes everything outside that window)
  • Clarifies that our pruning instructions only apply to HashDB
  • Adds 3 more pathDB relevant flags for node operators to be aware of: --execution.caching.state-history, --execution.caching.state-scheme, and --execution.caching.pathdb-max-diff-layers, alongside defaults and assumptions
  • Updated the minimum hardware requirements for archive nodes to match what we have in the full nodes section
  • Removed mentions of Nova storage growth rate estimates
  • Updated our Arbitrum One storage growth rate estimates (using internal metrics)
  • Emphasized the fact that PathDB snapshot auto-download with --init.latest is not yet supported in the database snapshots page
  • Did some minor formatting/grammar fixes for how we refer to PathDB enabled archive nodes and capitalization of certain words

Document type

  • Gentle introduction
  • Quickstart
  • How-to
  • Concept
  • FAQ
  • Troubleshooting
  • Reference
  • Third-party content
  • 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

@vercel
Copy link
Copy Markdown

vercel bot commented Mar 31, 2026

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

Project Deployment Actions Updated (UTC)
arbitrum-docs Ready Ready Preview Apr 1, 2026 11:10pm

Request Review

Co-authored-by: Gaël Blanchemain <anegg0@users.noreply.github.com>
Copy link
Copy Markdown
Contributor

@anegg0 anegg0 left a comment

Choose a reason for hiding this comment

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

A few edits, some of them lending toward a more colloquial tone to follow the pattern guide.

Co-authored-by: Gaël Blanchemain <anegg0@users.noreply.github.com>
Updated descriptions for state history and pathdb max diff layers parameters.
Copy link
Copy Markdown

@iamhsk iamhsk left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Copy Markdown
Contributor

@magicxyyz magicxyyz left a comment

Choose a reason for hiding this comment

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

LGTM

@leeederek leeederek merged commit 609eda4 into master Apr 2, 2026
6 checks passed
@leeederek leeederek deleted the derek/clarify-pathdb branch April 2, 2026 12:57
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.

5 participants