docs: add SECURITY.md — Phase 1 disclosure policy#21
Open
abhicris wants to merge 1 commit into
Open
Conversation
CR8 is pre-audit Phase 1. This SECURITY.md sets the disclosure expectation explicitly so external researchers know: - Phase boundaries (testnet vs mainnet, audited vs not) - The reporting channel (security@kcolbchain.com) and PGP key reference - Bug-bounty posture (not yet active; signposted for Phase 2) - Out-of-scope items (third-party libs, infra not run by Create Protocol) - Response timeline commitment No code changes.
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
Add
SECURITY.mdto the repo root setting explicit disclosure expectations for the pre-audit Phase 1 period. No code changes.What's in scope
Why
External researchers asking about disclosure now get a clear policy file instead of having to read README + commit history. Signals that the project takes security seriously even pre-audit, which matters for the Phase 1 → Phase 2 audit prep.
What's NOT in scope
docs/security/THREAT_MODEL.mdPR will follow)Pairs with the three already-merged spec PRs (#18, #19, #20) as part of the repo-quality sweep.