[codex] Clarify STRK20 claim boundaries - #3
Merged
Conversation
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
This PR clarifies the STRK20 claim boundaries in the privacy grid after the latest content review.
It removes wording that could imply STRK20 is already formally zero-knowledge or full-stack post-quantum safe today, and replaces it with narrower claim language: S-two/STARK proving is live, formal ZK remains a roadmap item, and the post-quantum score applies to the hash-based STARK proof layer rather than every Starknet dependency.
It also tightens adjacent STRK20 wording around sequencer-level S-two proof verification, encrypted viewing keys registered with an independent third-party auditor, and DeFi composability through existing Starknet liquidity and app surfaces without promising zero custom work for every existing contract.
Changes
data_v29.js.Verification
node scripts/validate-data.jsgit diff --check HEAD~1 HEAD