Closed sorpaas closed 5 years ago
Are there any news in this subject?, signing verifying should seriously be standardized (e.g removing the weird "Ethereum Signed Message" from some clients). Not only this ecdsa+keccak256 isn't standard and is incompatible with some EC libraries, this at least should have a real doc saying how the sig should work and behave.
(Rendered)
Motivation
The current
eth_sign
definition is different across different client implementation, which creates many problems. In addition, there is currently no way to verify a signed message using JSON RPC. This ECIP defines two new RPC callssign
andrecover
in a different namespace.Namespace
The author of this ECIP recommends to define the two new RPC in a different namespace rather than
eth
. Reusingeth
may cause confusion with the existingeth_sign
RPC call and might further pollute the already huge namespace. We can useetc
namespace, orkey
namespace (so those two RPC method becomesetc_sign
,etc_recover
, orkey_sign
,key_recover
).