Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
eth_sign API out of sync with ethapi
See original GitHub issueAs of https://github.com/ethereum/go-ethereum/pull/2940, eth_sign api has changed. It is now eth_sign(address, msg), accepting arbitrary input and putting it through keccak256.
Expected Behavior
Upstream eth_api introduced a breaking change where eth_sign now accepts the actual message, rather than a 32 byte hash digest. Signature is now eth_sign(address, msg)
Current Behavior
testrpc currently emulates existing eth_sign(address, sha3(msg)) behavior
Possible Solution
Change ethereumjs-util.ecsign to call keccak256 before calling secp256k1.sign
Context
We need to sign statements with web3, which is now incompatible between testrpc and real ethapi.
Your Environment
- Version used: v3.0.3
- Environment name and version (e.g. PHP 5.4 on nginx 1.9.1): n/a
- Server type and version:
- Operating System and version: os x
- Link to your project: https://github.com/mediachain/aleph-ethereum
Issue Analytics
- State:
- Created 7 years ago
- Reactions:10
- Comments:25 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I made a diagram of the current differences between testrpc, geth and parity with respect to eth_sign behavior and on-chain ecrecover.
Not to mention now we are supposed to use personal_sign or even eth_signTypedData instead of eth_sign (see this).
Does ganache plan to support these new features anytime soon?