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 currently have no nice way of learning about the encrypted event logs. Consider how we could support filters or similar searching when only the incoming_tag and outgoing_tag is readable without decrypting anything.
As we will not be able to look for a specific contract, it might be very very hard to do a "small" search for logs as you cannot filter on any values if you have not already decrypted it.
One option might be to do similar to the note processor, and have a logs processor that is building a view of events that you can decrypt that is then easily searchable, but this might add a significant overhead in the amount of compute required until tags are properly supported if notes is expected to receive actual usage.
The text was updated successfully, but these errors were encountered:
We currently have no nice way of learning about the encrypted event logs. Consider how we could support filters or similar searching when only the
incoming_tag
andoutgoing_tag
is readable without decrypting anything.As we will not be able to look for a specific contract, it might be very very hard to do a "small" search for logs as you cannot filter on any values if you have not already decrypted it.
One option might be to do similar to the note processor, and have a logs processor that is building a view of events that you can decrypt that is then easily searchable, but this might add a significant overhead in the amount of compute required until tags are properly supported if notes is expected to receive actual usage.
The text was updated successfully, but these errors were encountered: