-
Notifications
You must be signed in to change notification settings - Fork 3
Description
When looking at transactions against a contract in etherscan, I can see failed transactions (example)
When crawling blocks with web3.js, I can look through all transactions against my contract, then fetch the transaction receipt for each one to determine if the transaction succeeded or failed (example)
When using a blockHandler in a subgraph, I do not seem to have any similar capability. I see that The Graph's Ethereum API provides access to a transactionsRoot and a receiptsHash, but I see no documentation of how to use these to scan all transactions for the ones I'm interested in, nor do I see info about whether failed transactions would even show up in such a list.
Regarding possible alternatives to blockHandlers:
- I will want my subgraph to work on Rinkeby, so
callHandlerswill not work for me - I would assume that
eventHandlerswill only parse successful transactions, since failed calls do not emit events
If I can already find the failed transactions using existing capabilities of The Graph, great! Please let me know how, and point me in the right direction and I'll happily update your docs with the info.
If The Graph does not currently provide this info in its Ethereum API, please consider this a feature request.