# Util/sequniv not valid Electrum **URL:** \ **Category:** Alloy 6\ **Created:** [September 10, 2020, 4:17pm UTC](https://alloytools.discourse.group/t/util-sequniv-not-valid-electrum/86 "2020-09-10T16:17:04Z")\ **Posts on this page:** 1\ **Showing post:** 20
**Author:** ![grayswandyr](https://yyz2.discourse-cdn.com/free1/user_avatar/alloytools.discourse.group/grayswandyr/32/17_2.png) [@grayswandyr](https://alloytools.discourse.group/u/grayswandyr)\ **Post date:** [September 12, 2020, 1:18pm UTC](https://alloytools.discourse.group/t/util-sequniv-not-valid-electrum/86/20 "2020-09-12T13:18:34Z")
Sorry for the delay. So, with what I know, I would represent commands as events. Events are represented as _predicates_. Then, using the [“reified event” idiom](https://alloytools.discourse.group/t/modelling-a-state-machine-in-electrum-towards-alloy-6/88), _occurring events_ will be present in every trace you’ll get. As a matter of fact, they will be the commands you were trying to memorize in the `Script` sig. You may export the trace to retrieve them in a shape amenable to further processing in the context of testing. Hope this helps. --- _[View the full topic](https://alloytools.discourse.group/t/util-sequniv-not-valid-electrum/86)._