GitLab

Remove the one at the end of loading, it makes more sense to do it
in the constructor since the bloom is about both the private keys
as well as for the utxo

* confirmed
* unconfirmed
* immature

Now we wait for coinbases to mature before we show them in balance and
before we use them in transactions.

We wait until the chain is synched and then we check for and broadcast
unconfirmed transactions.

This essentially means that every single block we receive will trigger
this code. In BCH I think that is just fine since all we really do is
send an INV.

There are some listeners connected to this which may make it more
expensive than expected.

This moves the 'visible' decision to the account page.

We make sure to broadcast our transactions repeatedly if they are not
yet confirmed.
For instance if the last time we made it we were offline.

These QML files were from my first quick&dirty UI, now all functionality
has been replaced with better ones.

Reachable from the 'dotdotdot' menu on the account page.

When a unconfirmed transaction gets made invalid by a mined one spending
the same output, this updates the wallet balance and UTXO state
properly.

When a transaction is received by the p2pnet layer via a simple INV/
GetData we now process this and properly lock the outputs it spent to
avoid creating double spending transactions.

One task is left: properly recognize when a mined transaction
invalidates another transaction (like an unconfirmed one) and update the
datastructures.

The idea is that the user can empty out a wallet using the 'max' button.

This avoids the far to CPU intensive perfect solution and instead does a
best effort comparisn between various semi-random selections of inputs.

This allows us to use it as the favourite wallet we open on startup.

Also allow setting it through a heart-icon