OpenZeppelin / OpenZeppelin/compact-contracts
docs(token): note that shared sk/ek voids the ek guard on sweep and clearMemos
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 29
- Avg merge
- 5d 7h
- Merged PRs (30d)
- 25
Description
The ConfidentialFungibleToken header (added in #818) states that sharing key material between wit_ConfidentialTokenSK and wit_ConfidentialTokenEK is permitted and safe, because domain separation keeps the published account identifier from revealing the encryption scalar. That is true for confidentiality, which is all the note claims.
#830 fixes M-03 (#797) by requiring the encryption secret in sweep and clearMemos, so holding the account secret alone cannot freeze an account. That guarantee holds only while the two secrets are independent. A wallet following the permitted-sharing note collapses them, and the prune-then-sweep freeze returns.
Qualify the note: sharing is safe for confidentiality, and it forfeits the two-secret authority split sweep and clearMemos rely on. Wallets wanting the M-03 protection must keep the secrets independent.
Refs: #792, #797, #818, #830
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ConfidentialFungibleToken header added in #818 and review the sweep and clearMemos authority change described in #830. Qualify the sharing note to state its confidentiality scope and the loss of the two-secret authority split; done means the documentation clearly preserves the M-03 caveat for wallets.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 75/100