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
We should have functionality similar to the l1_payload for notes that can be used for the event logs to ensure that the values are decrypted and that the kernel provided address matches the address in the headers. See #6537.
Furthermore, we should be able to spit out values that can be decoded using the contract artifact for the event such that it is a meaningful value for the user.
For example, or a series of fields, returning Transfer(from, to, amount) if a Transfer event is decoded.
The text was updated successfully, but these errors were encountered:
Notable limitations to be discussed and / or addressed in a future PR.
Currently our events decoder supports only an event of fields.
This stack addresses #6535 and #6530.
We should have functionality similar to the
l1_payload
for notes that can be used for the event logs to ensure that the values are decrypted and that the kernel provided address matches the address in theheader
s. See #6537.Furthermore, we should be able to spit out values that can be decoded using the contract artifact for the event such that it is a meaningful value for the user.
For example, or a series of fields, returning
Transfer(from, to, amount)
if aTransfer
event is decoded.The text was updated successfully, but these errors were encountered: