satquay

Roadmap

Start with a dependable view.

The current release focuses on one useful task: understanding an address and the network around it. Future work should make that view clearer.

Product directionUpdated November 2026

Available today

Available

Public address observation

Paste a Bitcoin mainnet address or share the selected account from UniSat. Inspect confirmed balance, signed pending change, transaction activity and unspent outputs. Load older confirmed activity when needed.

Available

Network context

Read current fee recommendations, block height and mempool statistics from public data. Refresh when you need a new observation and see failures instead of substituted numbers.

Available

A local watchlist and plan

Save addresses and preferences in this browser. Enable incoming, outgoing, first-confirmation and fee-target alerts for an active, visible session. Only the selected address is refreshed.

Available

Portable snapshots

Download loaded transaction activity as CSV, or a structured JSON snapshot with local preferences and the current view. Keep a useful record without a cloud account.

Under consideration

These are candidate directions, not available features or delivery commitments. They require design, implementation and verification before they can be represented as part of Satquay.

Exploring

More control over the data source

Let experienced users select a compatible service or their own Esplora instance, with clear connection and privacy settings.

Exploring

Wallet-wide views

Investigate explicit multi-address or descriptor-based observation. This would need careful scope, discovery limits and privacy explanations before displaying a whole-wallet total.

Exploring

Durable alert delivery

Evaluate an optional service that checks conditions while the page is closed. It would need a separate backend, delivery channels, account controls and a clear reliability model.

Exploring

Richer activity review

Consider fuller history loading, better transaction annotations and importable settings. Any report should keep its source, time and coverage visible.

There are no announced release dates for these ideas. The documentation describes the functions you can use now.

What stays constant

  • Read-only access. Observation should not require permission to spend.
  • Visible scope. An address, a transaction page and a complete wallet are different things.
  • Honest state. A failed request should appear as a failed request, not a zero or a fabricated statistic.
  • User control. Labels, local settings and exports should remain understandable and easy to manage.

Use the current release. See exactly what it observes.

Open Satquay