Skip to content

Create v4.0.0.md (v4.0.0 upgrade instructions) - #129

Merged
lexavellino merged 1 commit into
mainfrom
fix/v4.0.0-doc-filename
Jul 1, 2026
Merged

Create v4.0.0.md (v4.0.0 upgrade instructions)#129
lexavellino merged 1 commit into
mainfrom
fix/v4.0.0-doc-filename

Conversation

@lexavellino

Copy link
Copy Markdown
Contributor

Validator instructions for the v4.0.0 passage-2 chain upgrade (gov prop #23, height 19950687).

Same content as #128, but under the correct filename — the #128 file carried a trailing invisible U+200E (LEFT-TO-RIGHT MARK), so it would have landed as v4.0.0.md\u200E instead of v4.0.0.md. Credited to @musicgreg via Co-authored-by.

Content verified: checksums in the doc match the envadiv/Passage3D v4.0.0 release sha256sum.txt (amd64 b2b5b63d…ec22, arm64 86b744f9…a6c5), release is published and not a draft.

Supersedes #128.

Validator instructions for the v4.0.0 passage-2 chain upgrade
(gov prop #23, upgrade height 19950687). Content verified against
the envadiv/Passage3D v4.0.0 release checksums.

Supersedes #128; identical content under the correct filename
(the #128 branch name carried a trailing invisible U+200E).

Co-authored-by: musicgreg <13667490+musicgreg@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@lexavellino
lexavellino merged commit 8994cb8 into main Jul 1, 2026
2 checks passed
@lexavellino lexavellino mentioned this pull request Jul 1, 2026
@lexavellino
lexavellino deleted the fix/v4.0.0-doc-filename branch July 1, 2026 16:39
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.

1 participant