Closed carlhammann closed 1 year ago
The module that defines TxSkel
needs a cleanup pass. Here are a few things I can think of (maybe one small PR each?):
RawModTx
stuff does nothing. We've got to either remove it or re-implement it in some suitable way.TxOpts
and one separate one on the TxSkel
.TxSkel
. They should be hidden from the end user. I see at least the following options:
TxOpts
or some other clearly "only touch this if you know what you're doing" area.TxSkel
forming a Semigroup
? (I think it might just be of use in writing tests for generateTxBodyContent'
.)Cooked.Tx.Constraints.Type
is not anymore what the module is about.
It's in the title. The motivation is to ensure by construction that the
TxSkel
spends everySpendableOut
at most once.I intend to base my re-integration of the attack language on (something like) this.