refactor(substrate_hash): ♻️ Substrate hash no longer retrieved via rpc call #136
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
added 3 commits
February 27, 2024 17:37
…pc call Substrate hash in `l2.rs` is now retrieved via use of the substrate rpc client created in `service.rs`.
|
There hasn't been any activity on this pull request recently, and in order to prioritize active work, it has been marked as stale. |
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.
Pull Request type
What is the current behavior?
Substrate block hash in
l2.rsis retrieved via an internal RPC call to the running Deoxys node.What is the new behavior?
Substrate hash is now retrieved through the use of the rpc client initialized in
service.rs, which has been passed tol2.rs.Does this introduce a breaking change?
No