nextjs - 💡(How to fix) Fix Docs: Clarify Movement Network Architecture and M1 L1 Migration Details [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#87848Fetched 2026-04-08 02:05:59
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
commented ×2closed ×1issue_type_added ×1locked ×1
RAW_BUFFERClick to expand / collapse

What is the documentation issue?

The current Movement Network documentation lacks clear, consolidated explanations of the M1 Layer 1 architecture and the recent migration from an L2-based deployment to a sovereign L1. Key concepts such as validator design, Move VM enhancements, execution model, and how M1 differs from the previous L2 setup are either missing, scattered, or insufficiently detailed for developers and ecosystem contributors.

Is there any context that might help us understand?

Movement Network recently became the first Move-based blockchain to migrate from an L2 to a full L1 (M1), introducing major changes such as a dedicated validator set, decentralized consensus, and significant performance improvements (e.g., 10,000+ TPS). These changes are highly relevant for developers, validators, and DAO participants, but the current docs do not clearly reflect this architectural shift or its implications. Improving this documentation would reduce confusion and help onboard contributors more effectively.

Does the docs page already exist? Please link to it.

https://docs.movementnetwork.xyz (Relevant information appears to be spread across multiple pages rather than clearly documented in a single M1 overview section.)

extent analysis

TL;DR

The Movement Network documentation needs a comprehensive overhaul to clearly explain the M1 Layer 1 architecture and its differences from the previous L2 setup.

Guidance

  • Create a dedicated M1 overview section on the documentation page to consolidate information on the new architecture, including validator design, Move VM enhancements, and execution model.
  • Review and update existing documentation to reflect the migration from L2 to L1, ensuring that key concepts and changes are clearly explained and easily accessible.
  • Consider adding a changelog or migration guide to help developers and contributors understand the implications of the architectural shift.
  • Collaborate with ecosystem contributors and developers to ensure the documentation meets their needs and is accurate.

Example

No code snippet is provided as this issue is related to documentation.

Notes

The lack of clear documentation may lead to confusion among developers and contributors, hindering the onboarding process and overall ecosystem growth.

Recommendation

Apply workaround: Create a temporary documentation hub or wiki to centralize information on the M1 Layer 1 architecture until a comprehensive overhaul of the official documentation is completed. This will help reduce confusion and provide a single source of truth for developers and contributors.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - 💡(How to fix) Fix Docs: Clarify Movement Network Architecture and M1 L1 Migration Details [2 comments, 2 participants]