-
Notifications
You must be signed in to change notification settings - Fork 513
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
Token Transfer Processor - Derive classic events from operation and operation results #5609
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
159c84a
to
36946d4
Compare
36946d4
to
571679c
Compare
karthikiyer56
commented
Feb 20, 2025
tamirms
reviewed
Feb 21, 2025
tamirms
reviewed
Feb 21, 2025
…action_envelope and the test fixture. It is not used anyway
… work, regardless of order
karthikiyer56
commented
Feb 22, 2025
karthikiyer56
commented
Feb 22, 2025
karthikiyer56
commented
Feb 22, 2025
karthikiyer56
commented
Feb 22, 2025
ingest/processors/token_transfer/token_transfer_processor_test.go
Outdated
Show resolved
Hide resolved
karthikiyer56
commented
Feb 22, 2025
ingest/processors/token_transfer/token_transfer_processor_test.go
Outdated
Show resolved
Hide resolved
…ad of a muxed account. This helps simplify the logic at call site for the operations when called with LPhash or CBid
tamirms
reviewed
Mar 17, 2025
tamirms
reviewed
Mar 17, 2025
…Id everywhere for classic assets
tamirms
reviewed
Mar 18, 2025
tamirms
reviewed
Mar 18, 2025
tamirms
reviewed
Mar 18, 2025
tamirms
reviewed
Mar 18, 2025
…mint and burn to appear correctly in the final list of elements
karthikiyer56
commented
Mar 21, 2025
…and print the error accordingly
Updated dependencies detected. Learn more about Socket for GitHub ↗︎
|
tamirms
reviewed
Mar 21, 2025
protos/ingest/processors/token_transfer/token_transfer_event.proto
Outdated
Show resolved
Hide resolved
tamirms
reviewed
Mar 21, 2025
tamirms
reviewed
Mar 21, 2025
tamirms
reviewed
Mar 21, 2025
tamirms
reviewed
Mar 21, 2025
tamirms
approved these changes
Mar 21, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉 🎉 🎉
Draft
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 deals with deriving TokenTransferEvents from operation and operation results as described in #5580
This PR is strictly dealing with classic and classic operations, i.e the PR implements the ask from #5592