We currently sign messages on Raiden simply by signing the hash of the message. By using eth_sign_sha3 as default hasher in signing.sign, and changing the smartcontracts accordingly (should be as simple as prepending the prefix before keccak256 it), we can make all our signing compatible with eth_sign RPC interface.
Of course, it doesn't mean we fully support this standard, but as the changes are minimal, it could allow us to fully use a web3 signer middleware, and possibly add in the future the option of doing all signing on the eth-node side, getting rid of opening the private key in the Raiden node, and easily switching to eip712 signatures when finished.
Problem Definition
We currently sign messages on Raiden simply by signing the hash of the message. By using eth_sign_sha3 as default hasher in
signing.sign
, and changing the smartcontracts accordingly (should be as simple as prepending the prefix beforekeccak256
it), we can make all our signing compatible witheth_sign
RPC interface.Of course, it doesn't mean we fully support this standard, but as the changes are minimal, it could allow us to fully use a web3 signer middleware, and possibly add in the future the option of doing all signing on the eth-node side, getting rid of opening the private key in the Raiden node, and easily switching to eip712 signatures when finished.
Related: #1293 #1402 #1467 #1475