[Docs] Post-OP-Stack migration: obsolete references and missing post-deadline guidance

Open
#1,395 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Domain
documentation

Research direction

Start with the network fees and migration guide pages, then inspect the base/node and base/contracts README files listed in the issue. Verify the current post-April 9 behavior and architecture wording before editing. Done means obsolete OP Stack references are corrected, post-deadline guidance is documented, and all four locations consistently describe the current state.

Written by the indexing model from the issue text.

Description

Summary

Following Base's exit from Optimism's OP Stack (Feb 2026) and the April 9 migration deadline for Farcaster mini-apps, I found several docs inconsistencies.

Issues Found

  1. Obsolete OP Stack reference in fee docs

    • Page: /base-chain/network-information/network-fees
    • Text links to "op-stack developer documentation"
    • Base now runs the unified base/base stack

  2. Missing post-deadline guidance in migration guide

    • Page: /apps/quickstart/migrate-to-standard-web-app
    • Deadline was April 9, 2026
    • No section explaining what happens to unmigrated apps (grace period? hard stop? error messages?)

  3. README base/node still claims "built on Optimism's OP Stack"

    • Should reflect the unified stack architecture

  4. README base/contracts says "utilizes Optimism's bedrock contracts"

    • Needs clarification post-migration

Suggested Fixes

  • Update fee docs to reference Base's own fee mechanics or clarify OP Stack heritage
  • Add "Post-April 9" FAQ to migration guide
  • Update base/node and base/contracts READMEs to reflect current architecture
Dominant language
JavaScript
Stars
337
Forks
798
Avg merge
7h 24m
Merged PRs (30d)
51

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from base/docs

All issues in base/docs

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.