Fields

• txSkelOptAutoSlotIncrease :: Bool

  Whether to increase the slot counter automatically on transaction submission. This is useful for modelling transactions that could be submitted in parallel in reality, so there should be no explicit ordering of what comes first.

  Default is True.

• txSkelOptModTx :: Tx ConwayEra -> Tx ConwayEra

  Applies an arbitrary modification to a transaction after it has been potentially adjusted and balanced. The name of this option contains unsafe to draw attention to the fact that modifying a transaction at that stage might make it invalid. Still, this offers a hook for being able to alter a transaction in unforeseen ways. It is mostly used to test contracts that have been written for custom PABs.

  One interesting use of this function is to observe a transaction just before it is being sent for validation, with

  txSkelOptModTx = [RawModTx Debug.Trace.traceShowId]

  The leftmost function in the list is applied first.

  Default is [].

• txSkelOptBalancingPolicy :: BalancingPolicy

  Whether to balance the transaction or not, and which user should provide/reclaim the missing and surplus value. Balancing ensures that

  input + mints == output + fees + burns

  If you decide to set txSkelOptBalance = DoNotBalance you will have trouble satisfying that equation by hand unless you use ManualFee. You will likely see a error about value preservation.

  Default is BalanceWithFirstSignatory

• txSkelOptFeePolicy :: FeePolicy

  The fee to use when balancing the transaction

  Default is AutoFeeComputation

• txSkelOptBalanceOutputPolicy :: BalanceOutputPolicy

  The BalanceOutputPolicy to apply when balancing the transaction.

  Default is AdjustExistingOutput.

• txSkelOptBalancingUtxos :: BalancingUtxos

  Which UTxOs to use during balancing. This can either be a precise list, or rely on automatic searches for utxos with values only belonging to the balancing user.

  Default is BalancingUtxosFromBalancingUser.

• txSkelOptModParams :: Params -> Params

  Apply an arbitrary modification to the protocol parameters that are used to balance and submit the transaction. This is obviously a very unsafe thing to do if you want to preserve compatibility with the actual chain. It is useful mainly for testing purposes, when you might want to use extremely big transactions or transactions that exhaust the maximum execution budget. Such a thing could be accomplished with

  txSkelOptModParams = Just $ ModParams increaseTransactionLimits

  for example.

  Default is Nothing.

• txSkelOptCollateralUtxos :: CollateralUtxos

  Which utxos to use as collaterals. They can be given manually, or computed automatically from a given, or the balancing, user.

  Default is CollateralUtxosFromBalancingUser