eth_signTypedData
indeed. We're defining a process for EIP-1812 (Verifiable Claims) that heavily relies on an EIP-172 implementation, for a private network (LACChain). Last night a gave it a try at diega/ethsigner@7986cbe. I didn't want to make any refactor like renaming the TransactionSignerProvider
to something more general, but most of the functionality I think it's there. It's just for eth_sign
but it's a beginning. It needs a lot of testing though
@rain-on no worries, thanks for the advice. I just sent PegaSysEng/ethsigner#263 but there is a failure running the acceptance tests that seems unrelated to what I made
GPG error: https://cli-assets.heroku.com/apt ./ InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5DC22404A6F9F1CA
let me know if I miss something for this or you'll like some changes to the code
Hi! I have a problem that I'm unable to resolve... I'm trying to connect Remix (Web3 provider) to EthSigner, because I'm working with a permissioned Besu network. In order to get that, I'm running EthSigner on a Docker container. I know that EthSigner - Besu node connection is working properly, because if I run this command, I can get this result:
curl -X POST --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":51}' http://192.168.43.125:9101
{
"jsonrpc" : "2.0",
"id" : 51,
"result" : "0xfe89"
}
But if I try to connect with Remix (Web3 provider), I get this error from Remix pop-up: Cannot get account list: Error: Invalid JSON RPC response: ""
And if I open the firefox console, i get this: Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://192.168.43.125:9101/. (Reason: CORS header 'Access-Control-Allow-Origin' missing)
I'm using http version of Remix, so I don't know what is the problem. What can I do? Maybe EthSigner isn't compatible with Remix Web3 Provider? Any ideas?
io.vertx:*
deps in ethsigner need to be updated to at least 3.9.0 to address a critical vulnerability. vertx-core
pulls in netty*:4.1.39.Final
which is vulnerable to https://nvd.nist.gov/vuln/detail/CVE-2020-11612 . netty
needs to be at 4.1.46
or higher (ref: https://mvnrepository.com/artifact/io.vertx/vertx-core)