-
Notifications
You must be signed in to change notification settings - Fork 16
Description
Problem
The webapp stores all synced blockchain data (orders, vaults, trades, transactions) in a local SQLite WASM database (worker.db) running entirely in the user's browser. When a user reports a problem related to this local database — sync failures, missing data, unexpected behavior — we have no way to inspect or reproduce their state.
The existing tooling doesn't help us here. The /db-playground page and LocalDbStatus components are user-facing, but there's nothing that lets a user share their database state, sync status, settings, or any kind of logs with us for investigation. We're left guessing at what went wrong based on screenshots or verbal descriptions.
We need some form of diagnostic capability that gives us visibility into a user's local database state when they report an issue.