A synthetic transaction with an invalid origin is not saved
General
Planning
Metadata
General
Planning
Metadata
Description
Environment
None
Activity
Show:
Ethan Reesor March 7, 2022 at 10:14 PMEdited
Validated by using accumulate credits ...
to send credits to foo
(which did not exist) and verifying that the synthetic transaction was created and can be queried.
Automation for Jira March 4, 2022 at 7:23 PM
Dennis B merged "fix(prot): always record synthetic transactions" (!171)
Automation for Jira March 4, 2022 at 7:23 PM
Ethan Reesor pushed 0 commit(s):
Automation for Jira March 4, 2022 at 7:23 PM
Dennis B approved "fix(prot): always record synthetic transactions" (!171)
Automation for Jira March 3, 2022 at 6:53 PM
Ethan Reesor pushed 1 commit(s): "test: fix" by Ethan Reesor on 2022-03-03T12:53:48-06:00
Done
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Reporter
Ethan Reesor
Ethan ReesorActual end
Mar 07, 2022, 10:14 PM
Story Points
3
Created February 10, 2022 at 10:01 PM
Updated April 4, 2022 at 3:53 PM
Resolved March 7, 2022 at 10:14 PM
Any synthetic transaction produced by a BVN should always make it to DeliverTx and thus be persisted, regardless of whether the transaction succeeds or fails. However, if the origin is invalid, the synthetic transaction is currently rejected by CheckTx: