Web3BaseAdapter makes use of an underneath web3-compatible provider through which the requests are being sent. Formerly, we used ethers.providers.StaticJsonRpcProvider as the adapter's provider.
It's not a big change since the interfaces of both are equal and the operations are the same with the sole difference of the communication protocol.
I tested for Web3BaseConnector using a ws node:
[x] Connection is established correctly
[x] It gets information about blocks, transactions...
[x] It executes reading operations correctly (Write ops. were not considered since these connectors are RO)
Web3BaseAdapter makes use of an underneath web3-compatible provider through which the requests are being sent. Formerly, we used
ethers.providers.StaticJsonRpcProvider
as the adapter's provider.It's not a big change since the interfaces of both are equal and the operations are the same with the sole difference of the communication protocol.
I tested for Web3BaseConnector using a ws node: