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
Currently, after executing transactions, we do not have return data which results from transaction's execution. In particular, in case of contract deployment transaction, we do not have information about deployment contract id, and no deployment specific error information, should transaction be successful yet deployment was not done, for example in case of contract-already-exists error.
Possible solution design or implementation
Devise a scheme to pass the return data back to transaction executor. Possibly, enrich the SpentTransaction struct with a field carrying the return data.
Additional context
This issue is related to the deployment epic #1071, yet it is also wider in scope, as it pertains to transactions in general.
The text was updated successfully, but these errors were encountered:
miloszm
changed the title
Return data from propagated transactions
Return data from executed transactions
Aug 5, 2024
Summary
Currently, after executing transactions, we do not have return data which results from transaction's execution. In particular, in case of contract deployment transaction, we do not have information about deployment contract id, and no deployment specific error information, should transaction be successful yet deployment was not done, for example in case of contract-already-exists error.
Possible solution design or implementation
Devise a scheme to pass the return data back to transaction executor. Possibly, enrich the SpentTransaction struct with a field carrying the return data.
Additional context
This issue is related to the deployment epic #1071, yet it is also wider in scope, as it pertains to transactions in general.
The text was updated successfully, but these errors were encountered: