OpenZeppelin / OpenZeppelin/compact-contracts
Add ConcurrentConfidentialNoteFungibleToken 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
The concurrency-hardened supply path needs a deployable demonstration that isn't tangled with the regulated composition.
📝 Details
contracts/src/token/presets/ConcurrentConfidentialNoteFungibleToken.compact
- Minimal preset: core + single-issuer gate +
ConcurrentSupply(delta-inbox accounting,concurrency.md§9.2). - Deliberately NOT regulated: no audit, delivery, freeze, or seizure, so the concurrency shape stands alone. Created notes return to the caller and move out of band.
- Serves as the reference for the conflict-free mint/burn pattern.
Landed in #679 (draft).
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 draft work in #679 and read concurrency.md §9.2 for the concurrency shape. The target is contracts/src/token/presets/ConcurrentConfidentialNoteFungibleToken.compact, containing the minimal core, single-issuer gate, and ConcurrentSupply composition. Done means a deployable, standalone reference preset without regulated features.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100