Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Transaction tracing #767

Closed
3 tasks done
gavofyork opened this issue Mar 18, 2016 · 2 comments
Closed
3 tasks done

Transaction tracing #767

gavofyork opened this issue Mar 18, 2016 · 2 comments
Assignees
Labels
F8-enhancement 🎊 An additional feature request. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Milestone

Comments

@gavofyork
Copy link
Contributor

ApplyResult should optionally contain a full trace of all CALLs/CREATEs. Should probably use the same substate collection/accrual architecture as logs.

Left todo:

  • ensure built-in calls have no trace entry (and that it works with exterior calls);
  • ensure DELEGATECALL and CALLCODE has no trace entry;
  • ensure excepted calls have no trace entry (and that it works with exterior calls);
@gavofyork gavofyork added F8-enhancement 🎊 An additional feature request. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible. labels Mar 18, 2016
@gavofyork gavofyork self-assigned this Mar 18, 2016
@gavofyork gavofyork added this to the 1.1 Civility milestone Mar 18, 2016
@gavofyork
Copy link
Contributor Author

#772

@gavofyork
Copy link
Contributor Author

#791

@gavofyork gavofyork modified the milestones: 1.2 Civility, 1.1 Apr 14, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F8-enhancement 🎊 An additional feature request. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Projects
None yet
Development

No branches or pull requests

1 participant