Skip to content

[phase2/wallet] docs: independent reads and recovery controls #48

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

Open
migberto wants to merge 2 commits into
base: develop
Choose a base branch
from
Open

[phase2/wallet] docs: independent reads and recovery controls #48

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ac9b3c6
docs(web-wallet): describe unavailable balance, history and network s…
bitcoinuniverseadmin Oct 21, 2026
f129851
docs(wallet): explain independent reads and recovery controls
bitcoinuniverseadmin Oct 22, 2026
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
28 changes: 27 additions & 1 deletion src/content/docs/start/web-wallet.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ description: The extension-free Universe Web Wallet and Universe Shielded Wallet
sourceRepo: bitcoinuniverseio/wallet
sourcePath: backend/shared/web-wallet/, frontend/web-wallet/
lifecycle: experimental
lastVerified: 2026-09-29
lastVerified: 2026-10-21
---

**Status:** not yet available. The web wallet is built and tested on a private test network, but it
Expand Down Expand Up @@ -47,6 +47,32 @@ see the same addresses. The two stay separate: connecting one never connects the
The wallet locks after 15 minutes without use. A send only uses coins that Universe has checked
carry no inscription, rune, or Atomicals asset.

## When the network service is unavailable

The wallet reads balances, history, and fees from Universe servers. When a read fails or takes longer
than six seconds, the wallet says so instead of showing an empty wallet.

- **Balance unavailable** means the wallet could not read your coins. It does not mean your balance
is zero. If the wallet read a balance earlier, that amount stays on screen with the time it was
read and **Refresh unavailable**.
- **Transaction history unavailable** means the wallet could not read your history. It does not mean
you have no transactions. If a later page fails, the rows already shown stay, with **More history
could not be loaded**.
- **Unable to verify the Bitcoin network** means the wallet could not check which network the server
serves. Sending stays off until the check works. A server that answers for a different network
shows **Network mismatch**, and balance, history, and sending stay blocked.
- When the coin safety check is unavailable, no coins can be spent. Receiving and backups still work.

Each failed read has a **Retry** button. Automatic retries run after 5, 15, and 30 seconds, or later
when the service asks the wallet to wait. Loading older history uses its own Retry button. The wallet
waits while the tab is hidden or offline. Receiving, showing your address, and downloading a backup
never depend on these reads.

History and rpow availability do not prevent Bitcoin payments when the network, coins, safety
checks, and fee rate are valid. If fee suggestions are unavailable, you can enter a fee rate.
The rpow custody panel shows its own unavailable state and Retry control. Previously loaded records
stay visible with their update time when a refresh fails; dependent actions stay off until recovery.

## Backups

Your recovery phrase is the backup. Write it down when you create the wallet.
Expand Down
Loading