Skip to content

Verify CoinPay runtime capability before vault alerts - #38

Merged
ralyodio merged 1 commit into
mainfrom
fix/coinpay-vault-watch-capability
Oct 30, 2026
Merged

ralyodio merged 1 commit into
mainfrom
fix/coinpay-vault-watch-capability

Conversation

@ralyodio

Copy link
Copy Markdown
Contributor

The installed vault watcher interpreted missing unlock logs as a locked vault and sent duplicate alerts linking to a page absent from the current deployment. Check the running container's module/routes and signing-record formats first. Legacy deployments with sealed records report a compatibility mismatch; unsupported vaults without such records produce no unlock alert. Missing status is unknown, never proof of a lock.

Preserves critical alerts for genuine signing incompatibility. Uses one critical smshub request per six-hour incident cycle. --check performs only read-only diagnostics; it never decrypts keys or forwards funds.

Validation: scripts-check passes, including five new fake-driven cases and the existing alert tests; Node syntax check passes. Production read-only probe confirms a legacy runtime with sealed signing records.

@ralyodio
ralyodio merged commit 07d8144 into main Oct 30, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant