-
Notifications
You must be signed in to change notification settings - Fork 682
Filtering with checksum addresses #97
Comments
Is there a workaround for this issue that does not involve monkey patching either web3.py or Ganache? It seems that web3.py does not want to be able to accept non-checksum addresses and Ganache does not want to do a simple lowercase conversion of the addresses it gets. |
This is believed to be resolved in ganache-cli@v6.1.2 |
This should be resolved per the release of |
@seesemichaelj @benjamincburns @carver I've tried ganache-cli 6.1.2 and I still get an empty list of events back. Can anyone else try to see if they get different results? |
@edevil Same problem. Duplicating my comment here for posterity: I'm still having this issue with:
The following filter does not work:
but this does:
Where |
@edevil My (awful) hack for this currently is to set the contract's address to
(yes this is awful) |
If I'm correct, #127 should fix this! Going to close this, should be in the next release |
@seesemichaelj could you update the issue with the version numbers when it's released? I'd like to include that info in the related web3py issue. |
@carver ganache-core@2.1.3 and ganache-cli@6.1.4 were just released |
Hello @carver, I still have the same type of issue: I'm using ganache-cli 6.1.8 with web3.py and i can't catch emited event with it! btw block filter and transaction filter works perfectly, but event filter doesn't, also i tried catch event with web3.js and it worked!
web3 filter:
|
@Zatonskikh this is OT for this repository. I'll give my first guess about what's wrong below. If you have any more questions, I recommend opening an ethereum.stackexchange question or a new issue on ethereum/web3.py Since you're setting |
Cross-linked from: #494
Expected Behavior
Current Behavior
Everything as expected, except the last step: no logs are returned.
Note that if the lower-case address is used in the filter instead, that logs are returned. So all other steps appear to be configured correctly.
Possible Solution
Force addresses to lower-case in the filter before searching? (optionally, verifying checksums)
Steps to Reproduce (for bugs)
I'm cross-posting from a web3py bug report, which includes source: ethereum/web3.py#674
Given the simplicity of the workaround, it seems that the problem should be easy to reproduce.
Context
Without this fix,
ganache
filters will appear broken in the next stable release of web3py, which is likely within a week or two. All other nodes appear to work as expected.Your Environment
I'll ask the original posters on the web3.py issue to fill in this info:
The text was updated successfully, but these errors were encountered: