OpenZeppelin / OpenZeppelin/compact-contracts
Add BasicConfidentialNoteFungibleToken preset
Open
Nobody has claimed this yet.
effort: 2-S
enhancement
feat:token
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 29
- Avg merge
- 5d 7h
- Merged PRs (30d)
- 25
Description
🧐 Motivation
RegulatedConfidentialNoteFungibleToken composes six modules and is the wrong entry point for someone learning the family or wanting plain confidential value with no compliance layer.
📝 Details
- Core + Issuer only: gated mint, self-gated transfer and burn, notes handed over out of band.
- No audit, delivery, freeze, allowlist, review, or seizure.
- The readable reference composition to sit next to Regulated.
Planned, not in #679 (confidential-note-token.md §0).
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 confidential-note-token.md §0 and compare the planned composition with RegulatedConfidentialNoteFungibleToken. Define the BasicConfidentialNoteFungibleToken preset with Core and Issuer only, excluding the listed compliance modules; done means the readable reference composition is available alongside Regulated.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100