-
Notifications
You must be signed in to change notification settings - Fork 1.5k
add Bytzz aggregator adapters #4137
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
base: master
Are you sure you want to change the base?
Conversation
The bytzz adapter exports:
|
The bytzz adapter exports:
|
Hey, I see there are problems with public RPC, range max 100 blocks. Is there a solution? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR, bit of heads up. I am not sure why, but we have trouble pulling event logs from x layer rpcs, tried with paid rpcs as well, same issue, have you faced this issue? did you find a workaround?
just saw this comment, so... we dont have a solution so far and sort of gave up on the x layer as a chain, like I said, even paid rpcs are not working |
Hmm. I have my own indexer for the volume (getLogs, same event). I'm also seeing a 400 error, but I've slightly modified the log retrieval method. I'm reducing the range for fromBlock - toBlock, and so far it seems to be working in most cases. |
hmm, is the indexer endpoint open? maybe we can pull logs from there 🥺 |
No description provided.