Add all addresses metadata to decoded #87
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Ferossgp
force-pushed
the
add-address-meta-to-decoded-tx
branch
from
422c48f to
f1fdd6e
Compare
Deploying loop-decoder with
|
| Latest commit: |
727b186
|
| Status: | ⚡️ Build in progress... |
Ferossgp
force-pushed
the
add-address-meta-to-decoded-tx
branch
from
f1fdd6e to
727b186
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To provide more context inside interpretations we will need the metadata of all addresses interacted in the transaction. Now we will be able to add the name of addresses that were part of the transaction but are not contracts.
Because the Contract Meta loader now loads metadata for all addresses and not only for contract we will need to rename the loader to include the extra scope it does. We will do that in a separate PR