OpenZeppelin / OpenZeppelin/compact-contracts
Add ERC6909
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 29
- Avg merge
- 5d 7h
- Merged PRs (30d)
- 25
Description
Given the constraints with batching and "safe" transfers, ERC6909 might be a better multi token standard to emulate. It's minimal be design and thus much more flexible for Midnight. AFAICT the only thing we currently cannot approximate well is introspection and events
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 the linked ERC6909 specification and comparing it with the current batching and “safe” transfer constraints described in this issue. Clarify the intended Midnight approximation, especially the limitations around introspection and events; done should be a decided scope and an agreed implementation plan.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100