Skip to content
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

Internal transactions #18223

Closed
MarcoGuarducci opened this issue Dec 1, 2018 · 3 comments
Closed

Internal transactions #18223

MarcoGuarducci opened this issue Dec 1, 2018 · 3 comments

Comments

@MarcoGuarducci
Copy link

MarcoGuarducci commented Dec 1, 2018

I would like to have this capability to geth.

@karalabe
Copy link
Member

karalabe commented Dec 3, 2018

You can use a call tracer to trace a transaction after it's been included.

debug.traceTransaction(<hash>, {tracer: callTracer})

It however only trance transactions whose state is still available in the database (i.e. last 128 blocks), or you'd need to regenerate the state (expensive). There are some further details here #15516

@karalabe karalabe closed this as completed Dec 3, 2018
@MarcoGuarducci
Copy link
Author

Thanks karalabe.
Unfortunately tracetransaction is too slow and consumes too much CPU. Moreover it is not suitable for a massive use as for example the development of an explorer. That's why I developed simple optional changes to geth to store internal transactions in the leveldb database when they are generated by the virtual machine and i like to contribute to geth project pushing it.

@ramilexe
Copy link

@MarcoGuarducci do you have PR or branch with your changes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants