You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 12, 2022. It is now read-only.
When issuing a contract keyword for the event log generated, the designated contract will fail if smart contract addresses are stored as checksummed addresses, and not as lower-case addresses
The current fix is to store addresses in the smart contract in lowercase, but the contract-by-address function could show some improvements by allowing lowercase and checksum'd addresses
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The culprit
When issuing a contract keyword for the event log generated, the designated contract will fail if smart contract addresses are stored as checksummed addresses, and not as lower-case addresses
The current fix is to store addresses in the smart contract in lowercase, but the
contract-by-address
function could show some improvements by allowing lowercase and checksum'd addressesThe text was updated successfully, but these errors were encountered: