Custom reverts never worked with Ethers v5, but worked when using Hardhat with Ethers v5... Now we have tests for ethers v5 & ethers 6.
Note that reversion data returned by oasis-web3-gateway isn't encrypted. These errors are successfully caught by Ethers v6 and are not attempted to be decrypted by the sapphire wrapper. So the recommendation is to upgrade to Ethers v6.
Closes: #169
While testing I encountered another problem: custom reverts are broken with Ethers v5. This is due to type confusion in Ethers v5 by then trying to work-around people avoiding type confusion in JSON-RPC endpoints. See: https://github.com/ethers-io/ethers.js/blob/ec1b9583039a14a0e0fa15d0a2a6082a2f41cf5b/packages/providers/src.ts/json-rpc-provider.ts#L61
Custom reverts never worked with Ethers v5, but worked when using Hardhat with Ethers v5... Now we have tests for ethers v5 & ethers 6.
Note that reversion data returned by oasis-web3-gateway isn't encrypted. These errors are successfully caught by Ethers v6 and are not attempted to be decrypted by the sapphire wrapper. So the recommendation is to upgrade to Ethers v6.