Storage Fee Improvement

Instructions

Current implementation of storage fees puts responsibility of maintaining FLOW for storage on user. I guess this can have negative effects on adaptation. I think for end user, buying an NFT should cover the storage cost.

Issue To Be Solved

I think if we think of NFTs (as size of a NFT can be determined depends on several factors such as holding content on chain or not) this will end up confusing from end user.

Suggest A Solution

I suggest some improvement especially on NFTs but also can be on any resource type, on creation on the resource, amount of FLOW needed to store the object that can be included in the resource.

So basically if I am minting an NFT, I can include enough FLOW inside the NFT, and it can stay bound to that NFT until it is destroyed. (which in case of it is destroyed, balance can be deposited into owner that is destroying the NFT)

The issue names no files, tests, or entry points. Start by reviewing how storage fees and resource creation are currently handled in the Flow repository, then clarify the intended lifecycle for storage funding across NFTs and other resources. Done should include an agreed design for creation, ownership, destruction, and refund behavior.