Deniz Mert Edincik

I think the question is; what is the practical use case to prefer identity to capability ?

I don't think there is a need for Capability version of the functions. What is the use case for them? ```cadence pub fun swapExactSourceToTargetTokenUsingPath( sourceToTargetTokenPath: Type[], sourceVault: @FungibleToken.Vault, exactTargetAmount: UFix64,...

I see too many edge cases to be honest, maybe at least we can limit this to migration. I always suggested composeability to people, instead of copying to reuse (...

> My main concern here is that permission to remove types effectively means a contract cannot revoke its keys if it has any dependency because of the risk that it...

copied from Discord to keep discussion in one place: I think the main issue is you it feels like you are committed to this ( at least in FiatToken case...

btw if we stay out of Circle situation; and focus on the FLIP: > The Cadence 1.0 upgrade in particular has exacerbated this need, as the changes to access control...

thanks @SupunS , yeah the problem is it makes sense in the first look, but then it becomes tricky when someone else relies on it somewhere. Thats the reason I...

> Concretely, we've thought of different "levels" for updatability: This is a great idea actually. I agree lack of macro view creates problems, to be fair, so far we always...

> "accessNode.api": "archive.mainnet.nodes.onflow.org:9000", it needs grpcWeb proxy in front ( and probably archive.onflow.org endpoint )

Does this also allow p2p sharing? Observers in between sharing blobs I mean. If so there may need to add some additional protections.