Cache and restore wallets

[paullinator]

Improve login performance by caching wallet state on a per account level in unencrypted JSON file and rehydrate before wallets load.

CHANGELOG

Does this branch warrant an entry to the CHANGELOG?

• Yes
• No

Dependencies

none

Description

none

---

Note

Medium Risk
Touches the login/account startup path and changes what EdgeAccount.currencyWallets returns before keys/engines load, which could cause subtle UI or lifecycle regressions if cache data is stale or delegation/update behavior is wrong.

Overview
Implements cache-first login by loading accountCache/<storageWalletId>/walletCache.json during accountPixie startup and immediately exposing cached EdgeCurrencyWallet objects (with background loading of the normal files/engines when cache is present).

Adds a new cache subsystem (cache-wallet-loader/cached-currency-wallet/cached-currency-config/cleaners/utils) that validates cached JSON, constructs delegating wallet/config objects that fall back to real engines when available, supports delegating otherMethods and wallet disklets, and ensures yaob propagation by calling update(wallet) in key setters.

Introduces an auto-saving, throttled cache writer (makeWalletCacheSaver) wired into accountPixie to persist active wallet state (balances, enabled tokens, public info, selected token definitions, and otherMethods names) with failure backoff; makeAccountApi now optionally merges cached wallets/IDs until keys are loaded. Includes extensive end-to-end tests plus fake-plugin hooks to deterministically gate engine startup and simulate missing otherMethods, and adds documentation for the architecture.

^{Written by Cursor Bugbot for commit 28424f6. This will update automatically on new commits. Configure here.}

[cursor]

Getter always allocates new object reducing bridge efficiency

Low Severity

When cacheSetup is non-null (for the lifetime of the account after a cache-first login), the currencyWallets getter always allocates a new result object on every access. The watcher pixie calls update(accountApi) on every Redux state change, causing yaob to re-read this getter, see a new object reference, and push the full wallet map over the bridge—even when the underlying wallet set hasn't changed. Previously the getter returned a stable reference from the pixie output.

 

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is ON. A Cloud Agent has been kicked off to fix the reported issue.}

[cursor]

Bugbot Autofix prepared fixes for 1 of the 1 bugs found in the latest run.

• ✅ Fixed: Initial cache save overwrites token definitions with empty data
  • Added a check for accountState.keysLoaded before triggering the initial cache save, ensuring builtinTokens are populated in Redux before the cache is written.

Or push these changes by commenting:

@cursor push cfdb37f5a6

Preview (cfdb37f5a6)

diff --git a/src/core/account/account-pixie.ts b/src/core/account/account-pixie.ts
--- a/src/core/account/account-pixie.ts
+++ b/src/core/account/account-pixie.ts
@@ -362,8 +362,10 @@
 
           if (cacheSaver == null) return
 
-          // Trigger initial save to persist cached wallet data from login
-          if (!initialSaveDone) {
+          // Trigger initial save to persist cached wallet data from login.
+          // Wait until keysLoaded is true to ensure builtinTokens are populated,
+          // avoiding overwriting cached tokens with empty data during cache-first login.
+          if (!initialSaveDone && accountState.keysLoaded) {
             initialSaveDone = true
             cacheSaver.markDirty()
             return