OpenZeppelin / OpenZeppelin/compact-contracts
Add Unshielded Native Token standard
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 29
- Avg merge
- 5d 7h
- Merged PRs (30d)
- 25
Description
🧐 Motivation
Counterpart to the Shielded Native Token standard for native unshielded (transparent) ledger tokens. Provides the shielded↔unshielded on/off-ramp within Midnight, so projects aren't limited to shielded-only assets.
📝 Details
Standard for native unshielded ledger tokens (mint/burn/transfer), aligned with the Shielded Native Token API where it makes sense so the two are interoperable. Scope and ledger design TBD.
Roadmap: Libraries → Unshielded Native Token (Priority MNF: high).
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 reviewing the existing Shielded Native Token standard and the Unshielded Native Token roadmap entry. Define the scope and ledger design for native unshielded tokens, including mint, burn, transfer, and shielded↔unshielded interoperability. Done means the standard’s API and design are specified well enough for implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100