feat(validation/rpc): implement Soroban RPC response schema validator#417
Merged
Conversation
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
2 participants
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.
📖 Summary
This PR introduces a strict validation layer for Soroban RPC responses under src/validation/rpc/stellar/. It ensures all incoming RPC payloads conform to expected JSON-RPC structure before being processed by bridge workflows.
This prevents malformed or inconsistent RPC responses from breaking downstream bridge operations.
Soroban RPC providers may occasionally return malformed or incomplete responses. Without validation, these invalid payloads can propagate into the bridge pipeline and cause runtime failures or incorrect state handling.
closes #370