OpenZeppelin / OpenZeppelin/compact-contracts
Add Confidential Note Fungible Token Review extension
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 29
- Avg merge
- 5d 7h
- Merged PRs (30d)
- 25
Description
🧐 Motivation
The audit channel is all-or-nothing: its key sees every note. A custodian or FIU should see only the transactions addressed to it, and the two channels have to coexist.
📝 Details
contracts/src/token/extensions/ConfidentialNoteFungibleTokenReview.compact
- Per-output encrypted records to an approved REVIEWER key, alongside (not replacing) the global audit channel.
- Reviewer registry with
_addReviewer/_removeReviewergated by the consumer. - Emission is a compile-time variant, not a runtime flag: in ZK an optional emission still pays its constraints.
- Imports no token module.
Landed in #679 (draft). Final shape pending BitGo FIU feedback.
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 by reading contracts/src/token/extensions/ConfidentialNoteFungibleTokenReview.compact and the draft work referenced in #679. Confirm the final shape with the pending BitGo FIU feedback, then ensure the extension supports per-output reviewer records, gated reviewer management, coexistence with the global audit channel, and compile-time emission without importing a token module.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100