Change Details

No need to call `setWallet(wallet)` in each of the possible logic gates here. We want to call it no matter what. So, call it first. If it's valid, setLoading(false). Otherwise don't.

Set the wallet in localStorage as the valid wallet immediately on startup. The `getWallet` function already handles validation and potential migration requirements. With chronik, we can always refresh the wallet state on startup -- since this does not cause a noticeable user lag (legacy bch-api + slpdb approach could take 20s).

No need to call `setWallet(wallet)` in each of the possible logic gates here. We want to call it no matter what. So, call it firstSet the wallet in localStorage as the valid wallet immediately on startup. If it'The `getWallet` function already handles valid,idation and potential migration requirements. setLoading(false).With chronik, Otherwise don'twe can always refresh the wallet state on startup -- since this does not cause a noticeable user lag (legacy bch-api + slpdb approach could take 20s).