feat: persist unconfirmed transactions

[alexbarnsley]

Proposed changes

(ignore the branch name - i'm considering this a feature instead of a fix)

The app now has a hardcoded 45 minute value for how long it takes for transactions to expire. This is set in core, and there's no endpoint that provides this value. I thought about adding a network modal field, but I didn't want it to confuse users when adding custom networks. It can be added in the future if it causes issues.

To sum up, an unconfirmed transaction is stored in the local database. This remains until the transaction is processed and received, or the 45 minute period ends. At this point it is removed from the local database. If a wallet is in view with a transaction that expires, it will get a strikethrough and remain the unconfirmed grey.

Resolves #644

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactoring (improve a current implementation without adding a new feature or fixing a bug)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Build (changes that affect the build system)
• Docs (documentation only changes)
• Test (adding missing tests or fixing existing tests)
• Other... Please describe:

Checklist

• I have read the CONTRIBUTING documentation
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

[alexbarnsley]

spelt "persist" wrong in my commit message 🤦‍♂️

[j-a-m-l]

Maybe this can be set as a network property, so, when core provides the configuration, the transition would be straight