Skip to content

[codex] Clarify STRK20 claim boundaries - #3

Merged
odinfree merged 1 commit into
mainfrom
codex/clarify-strk20-claim-boundaries
Jun 1, 2026
Merged

[codex] Clarify STRK20 claim boundaries#3
odinfree merged 1 commit into
mainfrom
codex/clarify-strk20-claim-boundaries

Conversation

@odinfree

@odinfree odinfree commented Jun 1, 2026

Copy link
Copy Markdown
Owner

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

  • Clarifies the STRK20 formally-ZK partial score and tooltip.
  • Replaces broad post-quantum copy with proof-layer-specific language.
  • Updates STRK20 proof-verification wording to sequencer-level S-two verification.
  • Names encrypted viewing keys in the visible selective-disclosure card.
  • Softens DeFi composability wording and adds a sourced STRK20 caveat footnote.
  • Bumps the cache-busted data file to data_v29.js.

Verification

  • node scripts/validate-data.js
  • git diff --check HEAD~1 HEAD
  • Targeted phrase scan for removed risky wording.

@odinfree
odinfree merged commit 457cd50 into main Jun 1, 2026
1 check passed
@odinfree
odinfree deleted the codex/clarify-strk20-claim-boundaries branch June 1, 2026 14:34
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