OpenZeppelin / OpenZeppelin/compact-contracts
Add Confidential Note Fungible Token Metadata extension
Open
Nobody has claimed this yet.
effort: 1-XS
enhancement
feat:token
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 29
- Avg merge
- 5d 7h
- Merged PRs (30d)
- 25
Description
🧐 Motivation
No name / symbol / decimals anywhere in the family. Both NativeShieldedToken and ConfidentialFungibleToken have it, and wallets need it to display a note balance at all.
📝 Details
- New standalone extension: sealed metadata fields plus getters, mirroring the existing token modules' metadata shape.
- Imports no token module; the consumer binds the values at initialization.
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 metadata shape used by NativeShieldedToken and ConfidentialFungibleToken, including the work planned outside #679. Done means a standalone extension provides sealed name, symbol, and decimals fields with getters, without importing a token module, while consumers bind those values at initialization.
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
- 58/100