Take into account that miners play with block dates, so a block may come
in with a timestamp slightly in the future.
In that case we still want to show 'now' instead of the ISO date.
FloweePay is an appliction singleton and as such a global that is
deleted outside of main().
The FloweePay app owns most of the data, including (implicitly) the
private keys. Private keys are managed with a LockedPoolManager in
order to enable page-locking and avoid them being swapped out.
LockedPoolManager is also a singleton, and so we make sure that it
is created _before_ FloweePay and as a result deleted after FP
releases the memory managed by the LPM.
Singleton interactions are always a bit messy.
We introduced for secret keys the signature-type field, which is required
to avoid signing with one key as both Schnorr and ecdsa as
that can cause leakage making recovering the private key much easier.
So, we now store this data but old wallets didn't fetch that from
the incoming transactions. So this conversion fetches the data from the
transactions (which are on the device) and stores the sigtype with the
keys.
This adds the feature that we show a "last receive" field on a wallet,
and we also change the date format to have "yesterday" style dates
for recent ones.
This changes the default generated wallet to be a HD wallet.
We also add a helper class to configure newly created wallets from QML.
This finishes up the new wallet panel to have all the visible features
actually do something.
We can't delete them completely, at least for a while, because we can't
know if the user has used the QR payment code we presented at the first
app startup.
We store a blockheight at which point a private key is created, allowing
us to skip merkle checks before that time.
This was was tricky for a not yet synched wallet because its blockchain
was stuck at height zero.
Causing us to sync everything anyway.
Now we store the timestamp of wallet create instead, until the time that
the blockchain is synched. After that we resolve the block that we need
to start sync from based on that timestamp.
tomFlowee