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

Improve Log Decoding by Associating Logs with Contract IDs #3779

Open
Torres-ssf opened this issue Mar 14, 2025 · 0 comments · May be fixed by #3805
Open

Improve Log Decoding by Associating Logs with Contract IDs #3779

Torres-ssf opened this issue Mar 14, 2025 · 0 comments · May be fixed by #3805
Assignees
Labels
feat Issue is a feature

Comments

@Torres-ssf
Copy link
Contributor

Currently, the TS SDK decodes all logs from a transaction and stores them in an array under the logs property of the transaction result.

However, all decoded log values are grouped together in the same array. This makes it difficult to determine which log belongs to which contract in cases where a contract makes an inter-contract call and the called contract also produces logs.

As a result, users may struggle to identify the logs relevant to them.

To address this, we need to associate each log with its corresponding contract by using the contract ID during log decoding.

@Torres-ssf Torres-ssf added the feat Issue is a feature label Mar 18, 2025
@petertonysmith94 petertonysmith94 self-assigned this Mar 19, 2025
@petertonysmith94 petertonysmith94 linked a pull request Mar 20, 2025 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat Issue is a feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants