Deniz Mert Edincik

I can write up FLIP if necessary. To be clear, events will be emitted in the interface instead of implementer right? Post condition will call event emitter. (Event emitting will...

Shouldn't interface inherit metadataviewresolver (or till inheritance deployed implement) ? It shouldn't be a problem for rich events ( @bjartek may know more on this )

> oh, I was assuming that we'd put the events in the `Receiver` and `Provider` interfaces, but it sounds like you're saying they should be in the `Vault` and `Collection`...

> In my example there is no inheritance. Each interface is responsible with firing its own events. Can you expand a bit what do you mean?

Sorry @joshuahannan I missed your message will start a FLIP asap

@cybercent yeah this will handle situations like this. Basically events will not change, just they will not be fired from Flovatar but will be fired from interface. I think this...

Thanks @turbolent, I was gonna mae a flip then some work came I forgot , I will try to write this week

@SupunS I am also not sure if Cadence can rollback function invocation; it would be tricky for sure. ( if allowed in transactions)

@sideninja, my go knowledge is a bit limited, is it possible to make two structs somehow compatible in a 3rd one? I mean, something like SDK.address can be also accepted...

Ok I have looked a bit more; Now seems layers as follows: Emulator > Backend > FlowKit and Emulator > Backend > BackEndAdapter What would you think about: Emulator (...