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
Since the graph-node is supporting eth_getblockreceipts, it is possible to use common node providers at an affordable cost.
In order to prevent the bill to explode because the indexer for some reason failed to detect the eth_getblockreceipts availability, I don't want to use eth_gettransactionreceipt, I prefer stop indexing for this provider.
Im' in stress every time the indexer restarts, I have to watch if the eth_getblockreceipts is detected because sometimes, for some reasons it isn't.
Do you think it's possible to prevent eth_gettransactionreceipt ?
Are you aware of any blockers that must be resolved before implementing this feature? If so, which? Link to any relevant GitHub issues.
No response
Some information to help us out
Tick this box if you plan on implementing this feature yourself.
I have searched the issue tracker to make sure this issue is not a duplicate.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Description
Hello,
Since the graph-node is supporting eth_getblockreceipts, it is possible to use common node providers at an affordable cost.
In order to prevent the bill to explode because the indexer for some reason failed to detect the eth_getblockreceipts availability, I don't want to use eth_gettransactionreceipt, I prefer stop indexing for this provider.
Im' in stress every time the indexer restarts, I have to watch if the eth_getblockreceipts is detected because sometimes, for some reasons it isn't.
Do you think it's possible to prevent eth_gettransactionreceipt ?
Are you aware of any blockers that must be resolved before implementing this feature? If so, which? Link to any relevant GitHub issues.
No response
Some information to help us out
The text was updated successfully, but these errors were encountered: