eth/signature: fix prefix_message for multibyte characters #120
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, thanks for the useful gem!
I encountered a problem when verifying signature signed with web3.js that in some cases could not be verified correctly.
So I tried signing messages using web3.js and eth.rb, and noticed that different signatures are generated only if they contain multibyte characters.
Here is an example.
What's happening?
I found a difference in the logic of prefixing with "known messages" in web3.js and eth.rb.
In the known message, eth.rb counts the number of characters, but web3.js counts the number of bytes.
Which is correct?
The EIP-191 specification quotes go-ethereum as follows.
len
, a built-in function of golang, is designed to "returns the number of bytes" in the case of string.ref: https://pkg.go.dev/builtin@go1.18.3#len
Therefore, I decided that it was a mistake on the eth.rb side and created this PR.