OpenZeppelin / OpenZeppelin/stellar-contracts
🎁 [Feature Request]: Consider making `total_supply` tracking optional
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 95
- Forks
- 68
- Avg merge
- 4d 42m
- Merged PRs (30d)
- 20
Description
What is the feature you would like to see?
SEP-41 doesn't require tokens to implement supply tracking, so it's not required for the compliant tokens. Supply tracking has non-trivial performance cost, as its modification introduces a data dependency for all the transactions that use the token, which in turn makes them non-parallelizable, which reduces the token scalability.
It's hard to predict the exact impact - it depends on how often the token is being minted. But given the existence of the cost it would make sense to let the developer decide if they need this functionality given the potential performance cost.
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
No file, test, or entry point is named. Start by locating the token implementation's total_supply tracking and comparing it with SEP-41's supply requirements, then clarify the configuration or API needed to make tracking optional. Done means the design, compatibility implications, and performance trade-offs are documented well enough to guide implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100