Bitcoin and Dogecoin
The wallet now holds BTC and DOGE alongside BitFinite, Pepecoin and Bellscoin. Create or restore them like any other wallet, including watch-only.
Neither is swappable or buyable in the app. Those are separate features and both are still off.
A note on the servers, because it took some finding. A Bitcoin Electrum server has to clear three bars at once. Its certificate must match its own hostname. It has to be reachable from the networks our users are on. And it has to be ElectrumX rather than electrs, which cannot serve the transaction detail the wallet needs. Most public servers fail one of these quietly. Several are self-signed, one is CA-signed for the wrong hostname, and some ISPs DNS-hijack the best known one to a block page. Bitcoin talks to electrum2.bluewallet.io, Dogecoin to the two cipig hosts, and both fall back to a TLS relay we run so a block on one operator is not an outage. Certificates are verified strictly. Nothing here accepts a self-signed one.
The wallet screen
- The hero scrolls away, so the transaction list gets the screen.
- The price chart is one row. Price and change sit on the left, the range on the right, and the sparkline runs the full width underneath.
- Balances break at the decimal point, so whole coins read as the headline.
- Buttons, links and the sync chip take the theme's colours rather than the coin's. The coin colour keeps its icon and its card.
- Green up, red down, from the theme. The same green a received amount uses.
- Amounts drop decimals that are only zeros, so labels stop being squeezed.
Mining payouts
A wallet that mining has paid gets a card leading with how recent the last payout was, since that is the question a miner opens the wallet to ask. Tapping it opens the transaction list filtered to payouts. Those rows are titled "Mining payout" and carry their own mark, so earnings are distinguishable from someone paying you.
Fixes
- Large addresses get their balance again. The fetch that sums their unspent outputs used to fail outright on a pool address, so no balance was ever computed and the wallet showed zero. It completes now, though a wallet with tens of thousands of transactions takes a few minutes to reach its first balance.
- While that is happening the wallet list says "Syncing" rather than showing a zero. It used to render a confident 0.00, which reads as an empty wallet, and that is what made a working wallet look broken.
- A wallet watching a busy address no longer freezes the app. The history walk is capped like Pepecoin's and BitFinite's already were, and a quadratic deduplication in the shared fetch is gone.
- 132 text fields cropped their own labels in half. An outlined border floats its label onto the top edge, and the wrapper each field carried cut exactly that half off.
- Maximum precision is bounded. A negative value used to crash every amount the app drew, and the check meant to catch it was compiled out of release builds.
- A coin set to zero decimals rendered "50." with a stranded decimal point.
- The truncation notice is its own card instead of the first row of the transaction list.
- The transaction card has one spacing rule, so day headers line up with the rows they label.
- Watch-only wallets on very large addresses finish syncing.
- Confirmations count from block height, so a balance stops showing as unconfirmed when it is not.
Limits worth knowing
Watch-only wallets work, including on a mining pool payout address. The balance is always exact, because it is the sum of unspent outputs rather than a total derived from the rows on screen.
History is capped at the most recent 1,000 transactions per sync, and the wallet says so on screen when it applies. A very large address can take minutes to produce its first balance, and some cannot be read at all, because public Electrum servers refuse to enumerate very large unspent-output sets.
This is a personal wallet, not a treasury monitoring tool. It is not recommended for exchange vaults, custodial hot wallets, or large institutional addresses. Use an indexer or a block explorer for those. See docs/watch-only-limits.md for the measurements behind each statement.