Support configuration of acceptable payload format(s) for each service, e.g. JSONRPC for Ethereum relay chain.
Origin Document
Part of work on #860
The client, should support configuration that specifies the payload format for each service: this will eliminate the need for the oversimplified approach of deserializing the payload until it matches a format.
Goals
Avoid sending any relays that are clearly invalid due to format mismatch with the target service.
Deliverable
[ ] The client binary should allow configuration of accepted payload format(s) for each service
[ ] The client binary should have a default set of mappings indicating service -> accepted payload format(s).
[ ] Updated documentation describing the behavior change and how to update the default configuration.
Objective
Support configuration of acceptable payload format(s) for each service, e.g. JSONRPC for Ethereum relay chain.
Origin Document
Part of work on #860
The client, should support configuration that specifies the payload format for each service: this will eliminate the need for the oversimplified approach of deserializing the payload until it matches a format.
Goals
Deliverable
[ ] The client binary should allow configuration of accepted payload format(s) for each service
[ ] The client binary should have a default set of mappings indicating service -> accepted payload format(s).
[ ] Updated documentation describing the behavior change and how to update the default configuration.
[ ] Updated Validation diagrams, e.g. the Client-side Relay Validation diagram
Non-goals / Non-deliverables
A thorough validation of the relay contents based on the target service
General issue deliverables
Testing Methodology
make ...make ...make test_allLocalNetis still functioning correctly by following the instructions at docs/development/README.mdk8s LocalNetis still functioning correctly by following the instructions hereCreator: [@adshmh] Co-Owners: [@Olshansk]