You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The events we emit from EVM are not CCF/CBOR encoded which causes issues in the current implementation of APIs and clients.
I believe we should encode all EVM events in the same way as other events and keep the CCF encoding, this way all the existing clients and APIs will work, otherwise we have to handle this exception in all places, and to those who don't care about EVM side of things they will potentially have issues just tracking the events on Flow which doesn't make sense. At the same time I think interacting with Flow we should expect Flow/Cadence types. EVM responses should be decoded by the specific EVM clients from the native Flow types.
The text was updated successfully, but these errors were encountered:
sideninja
changed the title
[EVM] Events emitted from EVM are not cbor encoded
[EVM] Events emitted from EVM are not encoded as other FVM events
Nov 29, 2023
The events we emit from EVM are not CCF/CBOR encoded which causes issues in the current implementation of APIs and clients.
I believe we should encode all EVM events in the same way as other events and keep the CCF encoding, this way all the existing clients and APIs will work, otherwise we have to handle this exception in all places, and to those who don't care about EVM side of things they will potentially have issues just tracking the events on Flow which doesn't make sense. At the same time I think interacting with Flow we should expect Flow/Cadence types. EVM responses should be decoded by the specific EVM clients from the native Flow types.
The text was updated successfully, but these errors were encountered: