Joshua Hannan

Made a small edit to your proposal to the second capability. This makes sense. One question: I assume that most node operators and delegators are using [the staking collection](https://developers.flow.com/flow/core-contracts/staking-collection), so...

yes, this transaction updates any account to use the staking collection, even if they are already using a different setup: https://github.com/onflow/flow-core-contracts/blob/master/transactions/stakingCollection/setup_staking_collection.cdc

I think the [stable cadence upgrade](https://github.com/onflow/flow-core-contracts/pull/319) would be a perfect place to introduce this feature since it is a great use case for entitlements. I'll try to get it added...

I'm not in charge of the developer grants so I can't provide the final decision, but I'll offer a little bit of feedback. This sounds like a really interesting idea...

I updated all the dependencies, addressed all my previous comments on this PR, and got the cadence tests passing. NFTStorefront is staged on testnet, but NFTStorefrontV2 is not staged on...

@kc1116 Can you base this off the `stable-cadence` branch instead of `master` since we wouldn't be doing the upgrade until after Cadence 1.0?

This is handled in the [v2 standard](https://github.com/onflow/flow-ft/pull/131), so I am going to close this issue

Closing this in favor of https://github.com/onflow/flow-ft/pull/131 because I screwed up Git and I'm not sure how to fix it

@bthaile I just discovered a bug related to this. When trying to deploy a contract with an init argument, the contract doesn't report an error and also doesn't deploy the...

I'm going to close this PR because it is not needed anymore as the Freezing functionality is being removed