Closed chevdor closed 1 year ago
I think migrating to the Websocket provider might make the Faucet more resistant to the disconnects that happen when we upgrade RPC nodes which are currently breaking the Westend and Rococo faucets frequently. So it would be nice to see this addressed.
In my opinion this feature is very important. WS connections have been the standard for connecting to RPC nodes for many years by now.
@PierreBesson thanks for emphasising it! That seems to be related/duplicate of this issue https://github.com/paritytech/substrate-matrix-faucet/issues/84 right? if so, @parutger might be able to provide some timeline on fixing this
Those are separate issues but it's possible that part of the answer to fix paritytech/eng-automation#3 is to switch from HTTP to WS.
As of today, all faucets are using websocket RPCs
Currently, for some reasons, the server only support
http
. That prevents from benefiting from subscriptions.ref. paritytech/polkadot-testnet-faucet#67