Skip to content

Persist auto-lock activity across worker restarts #70

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
HDauven merged 1 commit into from
Jun 23, 2026
Merged

Persist auto-lock activity across worker restarts #70

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,6 +73,9 @@ The wallet automatically locks after a configurable timeout:
| Default | 5 minutes |

Implementation uses `chrome.alarms` API for reliable timing even when service worker sleeps.
The last activity timestamp is persisted in extension session storage when available
(falling back to local storage outside extension contexts), so a restarted background
service worker does not immediately lock an otherwise active unlocked wallet.

### 3. dApp Permissions

Expand Down
Loading
Loading