Specify exceptional bridge payout claim invalidation and prevent duplicate settlement #10

New issue

Open

opened 2026-10-31 02:07:46 +00:00 by PlasticDigits · 0 comments

PlasticDigits commented

2026-10-31 02:07:46 +00:00

Owner

Acceptance:

Pin affected bridge/vault chain and claim identity; document source deposit, destination execution, exceptional payout and cancellation as separate states, with exact principal/decimal conservation.
Design authorized irreversible invalidation/tombstone or equivalent safe settlement mapping so an exceptional payout cannot later coexist with execution of the original claim, even after blacklist removal/guard replacement.
Bind chain/source nonce/token/amount/original destination; define destination consent for authorized changes and race/order handling across pending execution, payout, cancellation and replay.
Specify limited governance authority, independent review and public redacted receipts without private operational details; preserve fees and liquidity accounting.
Produce focused scenario vectors and file/link the implementation issue in the actual owning bridge repository after inventory. No broadcast, private signer work or bridge/token code changes under research.

Dependencies: bridge owner review and #7 coverage inventory. Historical snapshots are not current bridge safety attestations.

Research follow-up from #8. Archive BRIDGE_RECOVERY records 10.154338 vFDUSD rescue while source nonce153 remained unused: recipient blacklist was containment, not cancellation. This is a cross-repository bridge design/handoff, not a CW20 implementation change. Acceptance: - Pin affected bridge/vault chain and claim identity; document source deposit, destination execution, exceptional payout and cancellation as separate states, with exact principal/decimal conservation. - Design authorized irreversible invalidation/tombstone or equivalent safe settlement mapping so an exceptional payout cannot later coexist with execution of the original claim, even after blacklist removal/guard replacement. - Bind chain/source nonce/token/amount/original destination; define destination consent for authorized changes and race/order handling across pending execution, payout, cancellation and replay. - Specify limited governance authority, independent review and public redacted receipts without private operational details; preserve fees and liquidity accounting. - Produce focused scenario vectors and file/link the implementation issue in the actual owning bridge repository after inventory. No broadcast, private signer work or bridge/token code changes under research. Dependencies: bridge owner review and #7 coverage inventory. Historical snapshots are not current bridge safety attestations.

PlasticDigits self-assigned this

2026-10-31 02:07:46 +00:00

PlasticDigits referenced this issue

2026-10-31 02:09:51 +00:00

Security upgrade: incident-driven CW20 protections and wallet security portal #3

PlasticDigits referenced this issue

2026-10-31 02:11:31 +00:00

Research: October wallet-compromise incident, rescued funds, ownership verification and further defenses #8