Janez Podhostnik

@bluesign thank you for the comments! > Capabilities as Resource makes little sense in my opinion. As I can Proxy the capability with resource. ( nested resource in another resource,...

Thank you all for all the comments :) There were some good arguments for keeping capabilities as values, so I will change the flip to reflect that. As pointed out...

I have prepared a delegation example: https://play.onflow.org/1dab1a55-5555-43d1-934c-991b24082720 Some observations: Its not that difficult to do currently (without this FLIP), but creating a new capability and revoking it requires that the...

So I have done a lot of thinking about the HORTON model, and I'm still not sure I am on the right track. As far as I can see it...

@bluesign A few thoughts: 1. I think if Carol can be sure that an issued capability will only be able to be used by the party it was issued to,...

Without this you are prevented from calling contract functions which emit events, so I totally agree. Is there some way we can make sure that the developer knows that events...

Thank you very much for the report. I did notice something while I was reproducing this: This transaction doesn't have this problem: ```cadence transaction() { prepare(acct: AuthAccount) { var i...

I though this sounded familiar https://github.com/onflow/flow-go/pull/1724. This will be fixed with a new version of flow-go.

I like the idea of the emulator creating accounts defined in flow.json for the `emulator` chain. For testnet or mainnet there could be a way to fetch the data needed...

This is so amazing ❤️ 🔥