Chain Agnostic MultiNode + EVM Implementation

[DylanTinianov]

Chain Agnostic Multinode

Implemented new Chain Agnostic MultiNode design to enable the scaleability of MultiNode to nonEVM chains.

Design Doc: https://docs.google.com/document/d/1nvgelqk4xbznRy8zdy_KHeEjFjgKkqhSUGXSlDze7nU/edit#heading=h.4e7ng0tekbkc

The MultiNode now has reduced responsibility to simple do the following:

1. Perform healthy checks on all RPCs
2. Select the best healthy RPC node to use

Chain specific implementations will now call RPC methods directly, while MultiNode just provides which RPC to use.

Benefits

• Maintainability: Allows for changes to chain agnostic code to be applied across all chains using MultiNode. New healthy checks and node selection mechanisms can be added across chains.
• Reliability: Using MultiNode on nonEVM chains will improve their reliability by introducing health checks on RPCs and ensuring healthy nodes are used.

Common Components / Interfaces

• MultiNode
• Node
• RPCClient
• Transaction Sender

EVM Implementation

An EVM specific RpcClient was implemented, and the EVM Chain Client was modified to initialize the new MultiNode and TransactionSender for EVM. The client is now responsible for calling RPC methods after asking MultiNode for an RPC to use.

[github-actions]

WF: CI Core#d5ce6f2

No errors found in this run. 🎉

[dhaidashenko]

Nice work!

[cl-sonarqube-production]

Quality Gate passed

Issues
1 New issue
6 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
84.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube