Dan Notesteinchanged title from TUI - Lock/Unlock a profile - change the default behavior to TUI - Lock/Unlock a profile (or Wallet??) - change the default behavior
changed title from TUI - Lock/Unlock a profile - change the default behavior to TUI - Lock/Unlock a profile (or Wallet??) - change the default behavior
Question: what is really being locked? Beekeeper wallet or a profile? Seems like it should be the beekeeper wallet.
Beekeeper is the one that has the "auto-locking" mechanism implemented. When no actions are taken on wallet, it will send "wallets closing notification" that clive listens to and adjusts its internal application state (so e.g f9 config -> manage key aliases is blocked in a locked state).
I think the best person to explain when beekeeper timeout is refreshed is @Trela - I'm not sure (because Clive is just a listener) if it's only when operating on a specific wallet or during any API call?
Automatically closed with !432 (merged), but I think this MR covers this issue.
Changed the default on "Activate" screen to "Permanent active mode".
IDK if this issue also meant "Permanent active mode" right after completing an onboarding (now will be locked after 15min after the onboarding is completed) but that's being tracked in #243 (comment 173406)