You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature description
Currently subtx uses jsonrpcsee that uses soketto as websocket client, the issue is that Soketto only supports HTTP 1.1 connections, which prevents it from connecting to public RPC urls such as wss://rpc.astar.network:443.
jsonrpcsee was designed to be a safe json-rpc server for substrate, not a client.
Possible Solution
Subtx allow different clients, it just need to implement the RpcClientT trait, it is implemented for jsonrpcsee here, we can implement that same trait for another client like tokio-tungstenite which supports TLS and HTTP 2.0.
Expected output
astar connector can to connect to any public or local RPC node
polkadot connector can to connect to any public or local RPC node
if https://dotapps.io can to connect to it, we must be able to connect too!
Create unit tests using self-signed certificates for testing the TLS connection.
The text was updated successfully, but these errors were encountered:
Feature description
Currently subtx uses jsonrpcsee that uses soketto as websocket client, the issue is that Soketto only supports HTTP 1.1 connections, which prevents it from connecting to public RPC urls such as
wss://rpc.astar.network:443
.jsonrpcsee was designed to be a safe json-rpc server for substrate, not a client.
Possible Solution
Subtx allow different clients, it just need to implement the RpcClientT trait, it is implemented for jsonrpcsee here, we can implement that same trait for another client like tokio-tungstenite which supports TLS and HTTP 2.0.
Expected output
The text was updated successfully, but these errors were encountered: