OpenZeppelin / OpenZeppelin/compact-contracts
Consider hardening cft domain separation
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 29
- Avg merge
- 5d 7h
- Merged PRs (30d)
- 25
Description
The cft currently relies on seed freshness for cross-deployment isolation. This can be improved with instance salt or possibly the contract's own address. Note that this will increase the constraints
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 locating the cft implementation and reviewing how seed freshness currently provides cross-deployment isolation. Compare the proposed instance salt and contract-address approaches, including their increased constraints, and define tests that demonstrate separation across deployments; done means one approach is selected and its constraints are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100