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
In PublicContext the emit_unencrypted_log_with_selector and emit_unencrypted_log. I'm not really sure "why" it actually have event id as part of what it is emitting. In my mind it would be useful to just have emit_raw_log in there, and then use a similar .emit function on events etc to deal with how it is actually constructing the message that is broadcast. Not clear to me why we are enshrining the event id in there.
Likely useful to hear what @fcarreiro says on this 👀.
The text was updated successfully, but these errors were encountered:
I think from our PoV we are (more than) happy to just remove the event selector from the opcode (and context) if it's not needed as something enshrined. It's currently implemented that way because it was in the (vm) spec. @dbanks12 wdyt?
In
PublicContext
theemit_unencrypted_log_with_selector
andemit_unencrypted_log
. I'm not really sure "why" it actually have event id as part of what it is emitting. In my mind it would be useful to just haveemit_raw_log
in there, and then use a similar.emit
function on events etc to deal with how it is actually constructing the message that is broadcast. Not clear to me why we are enshrining the event id in there.Likely useful to hear what @fcarreiro says on this 👀.
The text was updated successfully, but these errors were encountered: