Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
|
Closing: superseded by #317, which points the README and the app at the 2026-10-22 testnet deployment. |
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.
Summary
No related issue. Follow-up to #211 (closed by #215).
The allowlist TTL fix only reaches testnet with a new deploy. The contracts listed in the README were from before the fix, so testnet allowlist entries still expired after a few hours.
Changes
mainat934a937, which includes the allowlist TTL fix.[staging.contracts]list the new contract IDs, written by the deploy script.Test plan
Automated tests
HARNESS_NETWORK=testnet npm run test:happy-path -w scripts/harnessagainst this deploy: 24/24 pass.guardson a second throwaway testnet deploy, in CI order (deploy → happy-path → guards): 36/37 pass. The one failure isrefuses cancellation while the notice is running once price is readable. Its 10 s notice runs out across testnet's ~5 s ledgers beforefulfill_epochis sent. This is test timing, not a contract change. It passes on local in CI.guardsagain against the committed deploy failstwo exits of different sizes…. Earlier runs left extra deposits in the vault's liquid reserve. It passes on a fresh deploy.Manual verification
environments.toml→[staging.contracts].Breaking changes
The testnet contract IDs change. The dApp picks up the new ones on its next build.
Checklist
Screenshots
None.