Will
incoming user requests may have authenticated (but not encrypted) data. The gateway should expose a hook by which to validate that e.g. that the user really is who they say...
the downside of inclusion of both the node and subtle implementations for browserify is that the web3c.js library without web3 vendor is >600kb. A lot of this looks like the...
it's a verifier, or a signatureVerifier - it doesn't sign, it verifies. https://github.com/oasislabs/web3c.js/blob/master/web3c/signer.js
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...
We'll need to go through the exercise of releasing relatively soon, and should attempt to see what parts make sense to automate (potentially through CI). * Tagging of commit *...
There may be different code paths exercised when a local JS wallet is registered in the web3 1.0 api. we should validate compatibility with that configuration
Currently, there isn't a process that scans and decrypts logs
Currently, the provider only intercepts individual calls, and not call batches. It's unclear if the eth.Contract interface will trigger batches of calls, but the underlying pub key and confdiential calls...
Local keys should be rotated periodically. Currently it will be reused until the session storage is cleared.