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
when the remote web3 gateway supports the web3c protocol, but is running in a test or insecure mode where a trusted key manager is not running, it won't be able to produce valid signatures.
We should allow the client library to be instantiated in an insecure mode where it skips validation of signatures, similar to the path already implemented for testing, such that protocol functionality can be tested in insecure instances.
The text was updated successfully, but these errors were encountered:
when the remote web3 gateway supports the web3c protocol, but is running in a test or insecure mode where a trusted key manager is not running, it won't be able to produce valid signatures.
We should allow the client library to be instantiated in an insecure mode where it skips validation of signatures, similar to the path already implemented for testing, such that protocol functionality can be tested in insecure instances.
The text was updated successfully, but these errors were encountered: