Feat(refiner): Include EVM logs for bridge transactions #111
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
aleksuss
previously approved these changes
Nov 22, 2023
mrLSD
previously approved these changes
Nov 22, 2023
aleksuss
approved these changes
Nov 23, 2023
mrLSD
approved these changes
Nov 23, 2023
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 is a follow-up PR from aurora-is-near/aurora-engine#869 . In this PR, the Aurora Engine dependency is updated to the latest (unreleased) version, and we make use of the new
SubmitResultthat is returned from the Standalone Engine forft_on_transfertransactions that cause tokens to be minted.A new test is added to show that the EVM logs for bridge transactions are now included in the Aurora blocks the refiner produces.
Additionally, we needed to add handling for the new
withdraw_wnear_to_routermethod which was added as part of an XCC improvement.