We want to split WalletInitNavigator and use switch and stack navigators combination probably.

Please rethink the navigation flow

Once we are far enough with the project, we should support persisting some data between app restarts. This includes

• wallets and their settings
• transaction history for offline use

Adapt styles to the new design.

This is the screen where user choose between Creating and restoring new Wallet

We have following api calls to implement

• Fetch transaction history
• Filter used addresses (for discovery phase) (not needed by new sync implementation)
• Fetch utxo (for preparing transactions & estimating fees) (PPershing: might not be needed)
• send transaction

wait until #29 is implemented

Adapt the screen to the new design

So we can easily work on any screen

For example 1 confirmation - 10 confirmations

How should this works in other languages?

This way we will have control over display format in one place and also there will be no strange format strings in components...

Note: this needs to work together with #21

What needs to be done:

• encrypt keys and store them in permanent/secure storage
• Initial address discovery
• Create new wallet
• Restore existing wallet (needs syncing of history...)
• Syncing of history
• Discovery of addresses from newly synced transactions
• Spending ADA #115
• save/restore state to persitent storage

• secure storage of keys
• face/touch/pin auth

Generic dialog component with transparent background capable accepting children as its content

All ADA calculations should use big numbers to avoid rounding errors on very huge transactions

Add all form components and their basic styling to CreateWalletScreen.

For the starter, we need to explore which library to use, how to enroll and how to verify biometrics

Recovery phrase field should have autocomplete

Add form for recovery phrase confirmation to its screen