-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"from address mismatch" when tx.from is lowercased #1236
Comments
Good catch. I'll roll this up into a few other changes going out soon. Thanks! :) |
I had to go the other way. Use toLowerCase on them both. Since this is a low-level base class, I try to minimize the dependencies, and the address checksum would add the keccak256 dependency, and depending on tree shaking could also drag in BigNumber. This does bring up an issue I will address in v6, which is this means that if you use an IBAN/ICAP address, in the from field things will get dicey. That said, I think ICAP is all but dead, and I've been considering dropping support for it in v6 (a utility function will still exist for it though; it just won't be a first-class address format). |
Awesome! sounds good, thanks 🙂 |
This should be addressed in 5.0.26. Please try it out and let me know. :) |
Works great!! Closing as resolved. |
If
tx.from
is lowercased then this line throws thefrom address mismatch
because it's comparing against a checksummed address. Would it be better to checksum thetx.from
address and then do the comparison? since they're both the same address so I wouldn't expect it to throw.ethers.js/packages/abstract-signer/src.ts/index.ts
Line 176 in e0ccafb
The text was updated successfully, but these errors were encountered: