Seal: Deployment Tracking Issue

[athei]

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)

[athei]

The issues open for deployment are now tracked in a separate column inside the contracts project.