If the user closes the UI before the broadcast has completed, we would
stop broadcasting. Which is unfortunate and not what users expect.
As such we simply hold on to the object for a while (10 min) before we
delete it when it is quite likely already sent.
This uses the strategy to create one transaction per utxo instead of one
per address which makes this module actually provide some usefullness to
such wallets.
This shows the amount of coins stored on a single address, which we
sweep in one transction by default for privacy reasons.
This adds the ability of the user to specify how many outputs a single
transaction should have when we create it.
Instead of pre-allocation, this moves it to just before we actually
broadcast.
This solves a possible failure of detecting target funds in case the
number of transactions is larger than the gap and the user sends only
one or two of the later once instead of all.
When a transaction has been created by the plugin, this stores it also
on our UI classes and forwards the broadcast status for the front end
to use in some animation.
This is probably a good first milestone, the UX is pretty decent
and the wanted functionality is there.
Various todo's are still there which mostly of the cleanup type.
tomFlowee