Cosmos: Add the message handler #3975
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
Add Message Handler
…ssage Fix struct and field name error in padding unit test
Pass a transaction context to the message handler and event handler
evaporei
approved these changes
Sep 22, 2022
@evaporei It's the amount of gas requested for a transaction. |
This was referenced Sep 28, 2022
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.
This PR extends the Cosmos integration with a new type of handler, which enables subgraph developers to access transaction data in a more granular way.
Each Cosmos transaction contains multiple messages. Until now, in order to access a single message a subgraph developer had to define a transaction handler and loop over the message array inside the mapping function. With the introduction of the message handler, the same goal can be achieved just by adding a message handler and specifying a message type.
The data passed to the message handler includes the transaction context, which is a light-weight structure that contains the most important information about a transaction (hash, index, status code, gas information). The same structure is also passed to the event handler.