docs: document Stable v1.4.0#24
Draft
probablyangg wants to merge 2 commits into
Draft
Conversation
Contributor
Styleguide check✓ 127 en pages — 0 blocking, 11 warnings docs/pages/en/explanation/autobahn.mdxdocs/pages/en/explanation/consensus.mdx
docs/pages/en/explanation/ethereum-compatibility.mdx
docs/pages/en/how-to/monitor-node.mdx
docs/pages/en/how-to/troubleshoot-node.mdx
docs/pages/en/reference/indexers.mdx
docs/pages/en/reference/ramps.mdx
docs/pages/en/reference/system-transactions-api.mdx
docs/pages/en/reference/wallets.mdxEnforced by |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
docs | dacdc80 | Commit Preview URL Branch Preview URL |
Jul 16 2026, 01:58 PM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
The documentation contained partial and outdated descriptions of the v1.4.0 release. In particular, OPE and guaranteed blockspace were still described as distant roadmap work, the storage page used older MemDB terminology, and the guaranteed-blockspace page described a dedicated-mempool design instead of nonce-keyed block lanes.
This PR incorporates the supplied Stable v1.4.0 release overview while keeping the Mainnet rollout marked as pending because no Mainnet binary, upgrade height, or date was provided.
Impact
Developers can understand the new transaction envelope, nonce channels, lane configuration, and inclusion guarantees. Node operators get the MemIAVL and VersionDB migration context needed to prepare for the upgrade.
English remains the source of truth. The translation workflow will refresh the generated Chinese and Korean pages.
Validation
npm run check