feat(payments): gate Solana and BTC production rails - #457
Open
Svaag wants to merge 1 commit into
Open
Conversation
This was referenced Jul 16, 2026
Svaag
marked this pull request as ready for review
July 16, 2026 23:34
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
Why
Enabling payment code is not sufficient evidence that a rail can safely accept funds. Promotion must fail closed when CDP does not advertise Solana support or the durable BTC scanner is unhealthy.
Impact
Cloud deployments now require the production payment secrets and wait for the payment catalog to prove Solana and BTC readiness. Operators gain explicit alerts, canary evidence, and rail-specific kill switches.
Zcash is intentionally excluded. The prior research PR AS215932/hyrule-cloud#31 is deferred and closed.
Validation
scripts/ci/iac-static.sh— 130 tests passedyamllint -c .yamllint .scripts/ci/deploy-preflight.shthrough the static IaC suitegit diff --checkpromtoolwas unavailable locally; the rules passed repository YAML/static validation and should still run through the normal monitoring CI gate.Rollout
Merge only after the cloud and web companion PRs are available. Populate reviewed Vault values, deploy through the normal approval path, and execute the paid canary before marking the rails production-ready.
Companion PRs