the last commit refactors the wasmWrapper to avoid repetition of most of the transaction creation logic.
There are some use cases which are possible but for which we don't have a use yet (and weren't tested): sending a transaction with both a certificate and an output, and sending a transaction with only one input.
Sending a transaction with both an output and a certificate is possible and could be useful, but for now the wallet doesn't use it.
depends on: https://github.com/input-output-hk/js-chain-libs/pull/86
the last commit refactors the wasmWrapper to avoid repetition of most of the transaction creation logic. There are some use cases which are possible but for which we don't have a use yet (and weren't tested): sending a transaction with both a certificate and an output, and sending a transaction with only one input. Sending a transaction with both an output and a certificate is possible and could be useful, but for now the wallet doesn't use it.