Deniz Mert Edincik

> But you will need to be able to set them on chain as well wouldn't you? Yeah for example if you have in flow.json 4,5,10 account index accounts, I...

We can always create on first access, but it kinda feels like a 'hack'.

@ssingal05 actually we have parallel discussion about this (especially types to query storage) in https://github.com/onflow/cadence/issues/208 I am mostly against usage of paths (as least in common usage). For capabilities part:...

> Would the resource create a new vault for a user when someone tries to send them tokens that their account doesn't already support? This unfortunately cannot be because of...

@joshuahannan yeah , basically, if someone is sending me something new, there can be a function on switchboard contract where they can pay for the storage. Something like deposit with...

@alilloig nice proposal. Unfortunately after thinking on sender pays storage part, I concluded that there is currently no way to enforce that with cadence. I think we can remove that...

@joshuahannan It is possible maybe but I saw problems when trying some attack scenarios: - How to calculate the fee ? We can do naive storageUsed before and storageUsed after...

I agree, on happy path it works, though when we open the gates, generic receiver is pretty risky. I can even deploy contract, create some Fungible, send to your switchboard,...

I think depends on how we store, if we store in resource field ( as array or dictionary ) , breaks all switchboard I guess. If we store on storage...

> The only test I have written so far is a deployment test, which is currently failing because it says the `ExampleToken.Vault` does not implement `FungibleToken.Vault` correctly, which I am...