BMR Transport and RPC requirement

[mohamedelshami]

Is there a requirement for maintaining a common jsonrpc for all chain clients?

We're currently leveraging BSC rpc client to monitor block and handle subscriptions properly. Also makes it easy to maintain a consistent client interface with the target network.

Apart from from runtime dependency optimisation or increased binary size, I don't see this having an impact on behaviour of the BMR monitor/update process.

Also, we might need to introduce a second endpoint for ws protocol option in the BMR cmd (btpsimple.main) - Binance Smart Chain runs websocket on a different port.

Thoughts?

[jspark-icon]

There is no requirement for using /common/jsonrpc
For second endpoint or any other options, you could use src.options or dst.options as module/icon/sender.opt