Same as we encountered on the wallet. using of pokt rpc fail to function because of a wrong response ID.
Solution is simple, remove the pokt rpc's usage and rely on other providers
Complication: somewhere yet to be found it is still using https://eth-rpc.gateway.pokt.network/
[x] - Remove all local references to pokt
[ ] - Find the random place where it still decides to use a pokt rpc for eth
Description
Same as we encountered on the wallet. using of pokt rpc fail to function because of a wrong response ID. Solution is simple, remove the pokt rpc's usage and rely on other providers Complication: somewhere yet to be found it is still using https://eth-rpc.gateway.pokt.network/
Steps to reproduce
1. 1.
Which network did you use?
Supporting data