-
Notifications
You must be signed in to change notification settings - Fork 78
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
eth_getLogs does not return anything if filtered #494
Comments
Hey, currently getLogs can't resolve block tags, this should be fixed by this PR #532. For this case
It should be working, but could you post the event signature, so I can check the topic and verify P.S. Is this on the testnet? Those timestamps from the request look pretty old |
@BjMrq please see above comment and request for further details |
Hello, thanks for looking at this, it was on testnet using local json relayer. I just tried again on deployed json relayer for testnet. I freshly deployed the following contract https://github.com/BjMrq/hardhat-sandbox/blob/2211ee994a2397adf522832fd700ddf5fc402056/contracts/AccessRolesBox.sol Same result, when I run
I get the events:
but with:
I get no result at all. |
Hey, thanks for the reply. I think I know what is happening here. Just to confirm, does this request return a status code 400? Also if you add |
According to HIP-482, for eth_getLogs fromBlock and toBlock filters should default to |
@BjMrq with #590 merged into the |
Description
No logs are returned from the call when we add any filter other than address.
This works:
await provider.getLogs({ address: address })
Any of those won't:
or
or
More info:
Request of the one with all filters: d633b6db-a9f7-47c0-8d87-aa87f79d2ce2
[Request ID: d633b6db-a9f7-47c0-8d87-aa87f79d2ce2] [GET] contracts/0x0000000000000000000000000000000002dc46db/results/logs?timestamp=gte:1598571652.347251002×tamp=lte:1598573131.733718001&topic0=0x2f8788117e7eff1d82e926ec794901d17c78024a50270940304540a733656f0d 200 633 ms
Steps to reproduce
Additional context
No response
Hedera network
testnet
Version
tesnet
Operating system
No response
The text was updated successfully, but these errors were encountered: