Repository navigation
chore: point the README and the app at the new testnet deployment - #317
Merged
Merged
Conversation
The 2026-10-05 deployment has no usable keys and archived instances. The new one was made on 2026-10-22 with kept keys.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Oct 22, 2026
luchobonatti
approved these changes
Oct 22, 2026
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
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
Closes #316
The README and the app pointed at the testnet deployment of 2026-10-05. Its keys are lost and several of its contract instances are archived, so nobody could administer it or mint its test USDC. This points both at a fresh deployment made on 2026-10-22 (ledger 5330739) with kept keys (#312); the team holds the keys.
Changes
environments.toml[staging.contracts]lists the same contracts, so the app builds against them.Acceptance criteria
environments.toml[staging.contracts]lists the same contractsTest plan
Automated tests
None: configuration and documentation only.
Manual verification
CD5LYYXGOJ7R23P6D7YUN6DUJQYMI23KEUEOIFKXOSWOX3KHKTXRITED.Breaking changes
The public app moves to the new deployment once this merges.
Checklist
Screenshots
None.