feat: map Safe Harbor whitehat rescue onto the Security Map - #641
Merged
mattaereal merged 1 commit intoSep 14, 2026
Merged
Conversation
Seed adoption, published recovery address, and whitehat fund return. Not a bug bounty and not a substitute for pause or review. Eligibility checklist and on-chain registration walkthrough stay unmapped. No Nomad incident node. Cross-links to Incident Management, smart contracts, the protocol multisig, and governance come from shared exploit and recovery nodes.
Deploying frameworks with
|
| Latest commit: |
9f02789
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://5e30059f.frameworks-573.pages.dev |
| Branch Preview URL: | https://feat-security-map-safe-harbo.frameworks-573.pages.dev |
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.
What does this PR change?
Stacked on #640 (Privacy), which stacks on #639 / #638 / #637 / #636 / #635 / #633.
Maps Safe Harbor for the live-exploit window. Independent whitehats freeze without pre-authorization. Adoption and a published recovery address are the controls. Fund return to that address, with SEAL 911, is the response.
Safe Harbor is not a bug bounty and does not replace pause, review, or responsible disclosure.
Unmapped on purpose: eligibility checklist, on-chain registration walkthrough. No Nomad incident node.
Cross-links:
Wallet Security and Vulnerability Disclosure stay unshared until recovery-address hardening and security-contact pages are mapped in those frameworks.
No
related-toedges. No incident nodes.Type of change
If applicable
vocs.config.tswith thedev: trueparameter