Open
Conversation
Introduced TrustedNodeVerifier to handle comparison of responses between main and trusted nodes. This includes mechanisms for enabling/disabling verification, detailed error tracking, and discrepancy logging. Updated relevant components to integrate trusted node handling and stats collection.
Refactored the trusted node verification logic to enhance comparison mechanisms like content length and body validation.
… and `TRUSTED_NODE_URL`
This file contains hidden or 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.
This PR contains a comprehensive solution for implementing response verification through a trusted node. The solution focuses on validating RPC method responses by comparing them with responses from a predefined trusted node. The comparison approach varies depending on the type of RPC method. Currently, two comparison strategies are implemented:
content_lengthandbody.