refactor sign_transaction for multiple threads context, #41
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
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.
Hey guys!
JFYI:
We are using the Irys SDK within the Reth ExEx to sign transactions and send data to Arweave. One of the requirements is that the ExEx function should return a future that implements the Send trait.
https://reth.rs/docs/reth/builder/struct.WithLaunchContext.html#method.install_exex
I made some changes in types annotations and #[async_recursion]
Also maybe there were a specific reason for using #[async_recursion(?Send)] in the original implementation?
Could you let me know if there are any concerns? Thx!