This repository has been archived by the owner on Jan 13, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 77
Handling internal Tx #31
Comments
I've plans of adding internal transaction support. It'll take few weeks I guess. |
Are you using it for some purpose @simon-jentzsch ? |
we are looking for a solution to track balance changes and run queries against it. (like what is the amount moved from a certain account within a defined blockrange.) But this would need to include internal tx. |
Yes I understand, currently I'm working on improving block, tx & event syncing mechanism. I've implemented one improved way of doing it. From next week, I'll take up internal tx tracking implementation. Thanks for reporting @simon-jentzsch . |
Is this feature still being implemented? |
I've not yet implemented it, but contribution is welcome. |
I've stopped maintaining ette, so closing this issue. Thanks. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When quering a contract and trying to find out when and how much eth was actually sent, we cannot only look at the
to
and thevalue
field of the transactions in the block, but we must also check the internal transactions triggered.Do you plan to support them as well? (using https://openethereum.github.io/JSONRPC-trace-module#trace_replayblocktransactions would also enable you to put more data in the, like adding the reason for a tx failure)
The text was updated successfully, but these errors were encountered: