[DOCS] Verify commitments: publish the store base URLs - #106
Merged
Merged
Conversation
…ey store base URLs
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
…dd the browsable listing form
…tch URLs live in their sections
…shape, not a live object
…udly on a missing object
…te, the concrete path stays as illustration
…h, keep the shard rule
…ainst the public testnet archive
…archive, the testnet example stays runnable
This branch was successfully deployed
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.
Both stores are publicly readable now, verified by anonymous fetch today:
The pending-values table shrinks to one entry: the CommitmentRegistry address. The page says explicitly which store fills at which event, so nothing needs a docs change after the ceremony.