Skip to content

docs: cover Foundry v1.7 Tempo, MPP, and selective follow-up gaps#1803

Merged
zerosnacks merged 4 commits intomasterfrom
docs/foundry-1.7.0-tempo-mpp
Apr 30, 2026
Merged

docs: cover Foundry v1.7 Tempo, MPP, and selective follow-up gaps#1803
zerosnacks merged 4 commits intomasterfrom
docs/foundry-1.7.0-tempo-mpp

Conversation

@decofe
Copy link
Copy Markdown
Contributor

@decofe decofe commented Apr 30, 2026

Summary

This PR documents the most important user-facing gaps I found while reviewing the Foundry v1.7.0 release notes against the current book, with a focus on Tempo and MPP first, plus a small selective follow-up for other high-leverage v1.7.0 features.

This PR now:

  • replaces the outdated foundryup -n tempo install flow with upstream v1.7.0 guidance
  • adds a Tempo guide covering forge init --network tempo, foundry.toml setup, Tempo transaction flags, and Anvil usage
  • adds an MPP guide covering wallet setup, HTTP 402-gated RPCs, key discovery, deposit tuning, and channel persistence
  • documents the new runtime network and namespaced hardfork config in the config reference and default config page
  • adds a selective follow-up for advanced invariant-testing options and debugging improvements such as forge inspect ... linearization
  • exposes the new guides in the guides index and sidebar

Scope

I kept this intentionally selective.

The release notes contain many v1.7.0 changes that are already discoverable through generated CLI reference pages or are too narrow to justify guide-level documentation right now. This PR focuses on the user-facing gaps that were both:

  • clearly missing from the book
  • likely to block or confuse real users upgrading to v1.7.0

Audit Findings

The main gaps I found were:

  • the installation docs still pointed readers to the deprecated Tempo fork instead of the main Foundry release
  • the book had no narrative guide for configuring Foundry projects for Tempo, even though Tempo is upstreamed in v1.7.0
  • the config reference did not explain the new network key or namespaced runtime hardfork values like tempo:T3
  • the book had no page describing MPP-backed RPC endpoints, despite v1.7.0 shipping first-class 402 handling
  • a few important non-Tempo additions still lacked narrative coverage, especially advanced invariant-campaign options and forge inspect ... linearization

References

Validation

  • NODE_OPTIONS='--max-old-space-size=4096' ./node_modules/.bin/vite build

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 30, 2026

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

Project Deployment Actions Updated (UTC)
foundry-docs Ready Ready Preview, Comment Apr 30, 2026 0:40am

Request Review

@zerosnacks
Copy link
Copy Markdown
Member

cc @mablr / @figtracer please have a look

@decofe decofe changed the title docs: document Foundry 1.7 Tempo and MPP support docs: cover Foundry v1.7 Tempo, MPP, and selective follow-up gaps Apr 30, 2026
@zerosnacks zerosnacks marked this pull request as ready for review April 30, 2026 08:41
@zerosnacks zerosnacks marked this pull request as draft April 30, 2026 10:12
Copy link
Copy Markdown
Contributor

@mablr mablr left a comment

Choose a reason for hiding this comment

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

Sgtm.

We will need to include per-test network selection logic foundry-rs/foundry#14530.

Copy link
Copy Markdown
Contributor

@figtracer figtracer left a comment

Choose a reason for hiding this comment

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

lg

@zerosnacks zerosnacks marked this pull request as ready for review April 30, 2026 14:18
@zerosnacks
Copy link
Copy Markdown
Member

We will need to include per-test network selection logic foundry-rs/foundry#14530.

Sounds good, lets do that as a follow up

@zerosnacks zerosnacks merged commit 567e557 into master Apr 30, 2026
3 checks passed
@zerosnacks zerosnacks deleted the docs/foundry-1.7.0-tempo-mpp branch April 30, 2026 14:19
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.

4 participants