[Spike] Client Side Node Load Balancing (aka Node Pool)

[solanoepalacio]

• This process should be on wallet-manager and should pick a node before instantiating the provider/wallet

[solanoepalacio]

scrape from conversation:

• can we run a process that checks the health of a pool of nodes and decides what’s the most “trustable” node
• Monitoring evm nodes forking. Bsc case:
  • on aug 29 several providers “forked” on bsc (if you looked at the last block or nonces returned by the node they wouldn’t match the block and/or nonces exposed on bsc explorer)
  • maybe we can sample

[solanoepalacio]

@scnale mentions that it might be a good idea to send the transaction to many nodes instead of one

[solanoepalacio]

Ethers fallback providers might be a solution:
https://docs.ethers.org/v5/api/providers/other/#:~:text=The%20FallbackProvider%20is%20the%20most,a%20priority%20and%20a%20weight%20

One of the drawbacks of this solution is that doesn't solve the problem for non evm chains

[solanoepalacio]

To pick the healthiest node out, we also have to option to do it based on the behaviour of the node on the last transactions