Repository navigation
docs(testnet): add launch notes and historical deployment context - #757
Closed
ranjeet150 wants to merge 1 commit into
Closed
ranjeet150 wants to merge 1 commit into
ranjeet150 wants to merge 1 commit into
Conversation
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
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
Adds
testnet/registry/testnet-launch-notes.mddocumenting historical and institutional context regarding when the Bridgelet testnet environment was first provisioned and stood up, preserving deployment architecture, operational scripts, key contacts, and maintainer transition guidelines.Changes
testnet/registry/testnet-launch-notes.mdcovering initial standup epoch (September 2026), architecture, and RPC/Horizon network parameters.Closes #719