Investigate/Hotfix RPC websocket limitation

[Rodebrechtd]

Investigate/Hotfix RPC websocket limitation

Despite migrating from Alchemy to QuickNode, the websocket connection issues continue. While the behavior has changed, inconsistencies still persist

[Rodebrechtd]

The issue has been identified, and a temporary fix involves resource providers using a personal RPC. This solution has been tested, and the errors no longer occur

The long-term solution is to implement multiple RPCs for Lilypad and use a load balancer to evenly distribute the traffic

HotFix

1. Generate Free Alchemy Arbitrum Sepolia RPC
2. Use personal RPC at start-up:

docker run -d --name lilypad-resource-provider --gpus all -p 1234:1234 -e WEB3_PRIVATE_KEY=<private key> -e WEB3_RPC_URL=<personal RPC WS> --restart always ghcr.io/lilypad-tech/resource-provider:main