This repository was archived by the owner on Nov 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
This repository was archived by the owner on Nov 15, 2023. It is now read-only.
Seal: Deployment Tracking Issue #6357
Copy link
Copy link
Closed
Labels
J1-metaA specific issue for grouping tasks or bugs of a specific category.A specific issue for grouping tasks or bugs of a specific category.U1-asapNo need to stop dead in your tracks, however issue should be addressed as soon as possible.No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Description
We want to get the contracts module ready for deployment soonish. Here we track what is absolutely necessary before doing so. I expect that these should be mainly security and API issues. Please feel free to discuss below.
- Storage Transactions in order to greatly simplify implementation and subsequently creation of a sane weight schedule (Implement nested storage transactions #6269 pallet-contracts: migrate to nested storage transaction mechanism #6382)
- API rework. We need to get the API right before deployment. (seal: Rework the API #6355 Seal: Scratch away the scratch buffer (Part 1) #5513)
- Secure weights: That means working out a weight schedule that secures the module against DoS. The current values are provisional and must be replaced by values that are backed up by benchmarks.
- Use proper weight for balance transfers (Remove the workaround that lowers fees for transfering via contracts module #4713)
- Audit allocator usage (pallet-contracts: audit allocator usage #5379)
- Lazy contract removal (contracts: Lazy contract removal #6594)
- Storage rent for code (seal: Storage rent for code #6596)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
J1-metaA specific issue for grouping tasks or bugs of a specific category.A specific issue for grouping tasks or bugs of a specific category.U1-asapNo need to stop dead in your tracks, however issue should be addressed as soon as possible.No need to stop dead in your tracks, however issue should be addressed as soon as possible.