Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(Event_Logs): How should we learn about encrypted logs? #6534

Closed
Tracked by #5606
LHerskind opened this issue May 20, 2024 · 1 comment
Closed
Tracked by #5606

feat(Event_Logs): How should we learn about encrypted logs? #6534

LHerskind opened this issue May 20, 2024 · 1 comment
Assignees

Comments

@LHerskind
Copy link
Contributor

LHerskind commented May 20, 2024

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.

@LHerskind LHerskind changed the title feat(Event_Logs): How should we learn about logs? feat(Event_Logs): How should we learn about encrypted logs? May 23, 2024
@sklppy88 sklppy88 self-assigned this Jul 10, 2024
@sklppy88
Copy link
Contributor

sklppy88 commented Jul 10, 2024

Marked as completed via #7232.

We can definitely optimize the current approach more, but it will probably require a bit more thinking about the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants