Skip to content

Product tour

Source bitcoinuniverseio/docs-core
Path src/assets/shots/
Chain bitcoin, dogecoin
Network mainnet
Verified 2026-09-01

Every image on this page is the running product at www.bitcoinuniverse.io, captured by a script that visits the public origin, waits for each route to render rather than its skeleton, declines optional storage, and connects no wallet. None of them is a mock.

The first screen states how many protocols this build serves, counted from the same registry that builds the routes, and offers four next steps. Nothing on it needs a wallet.

The Bitcoin Universe home screen: a headline counting the protocols this build serves, a sentence naming the families and chains with a link to the full list, and four start cards for connecting a wallet, buying, selling, and market activity.
Home, light theme.

Light and dark are two complete designs rather than one theme with inverted colours.

The same home screen in dark theme, with the same headline, the same four start cards, and a graphite background.
Home, dark theme.

On a phone the same content stacks, and four persistent destinations sit in a bottom bar that never covers the page.

The home screen on a phone, with the headline, the start cards stacked vertically, and a bottom bar holding Home, Trade, Portfolio and More.
Home on a phone, 390 pixels wide.

One page lists what this build serves, grouped by family, with the index and the market for each row. The counts are computed from the same registry that builds the navigation, so the number on the page is the number of protocols the application can actually open.

The protocol coverage page: totals for protocols, families, chains, and how many have an index, then every row grouped by family with links to its index and its market, and a read source named on the rows the browser fetches elsewhere.
Coverage, light theme.
The same protocol coverage page in dark theme.
Coverage, dark theme.

That page and the support matrix answer different questions. Coverage says what Core reads. The matrix says what Core can do.

Each protocol family has a market with the same anatomy: a family picker, the period the figures cover, a searchable table, and an activity feed. A figure the reader did not return is a dash, never a zero.

The Ordinals market showing featured and top collections, a sortable collections table with floor price and volume columns, and an activity feed beside it.
The Ordinals market.

This is the capture worth studying. When a reader cannot be reached, the market says exactly that and offers a retry. It never presents a failed read as an empty market.

The Runes market showing a message that the order book did not answer so the market could not be read, with a retry link, and a table in a Market unavailable state rather than an empty table.

Unavailable, not empty. Compare it with a market that answered and had nothing listed: that one says “nothing listed” and offers no retry, because retrying would not change the answer.

Paste any Bitcoin or Dogecoin address to see its holdings across the protocols Core reads, with no wallet connected and nothing to sign.

The Explore address page with an address search field, a bulk watchlist input, and the list of protocols this view reads.
The address explorer.

Portfolio opens with what connecting gives you, and offers explore mode for anyone who would rather inspect a public address than connect a wallet.

The Portfolio page before a wallet is connected, naming what connecting shows and offering four choices: connect, explore an address, browse markets, and home.
Portfolio, disconnected.

Screens that need a connected wallet are described in words rather than shown, because a real capture of them would contain someone’s holdings and a mock would be an invention. The Portfolio and market task pages describe those interfaces precisely instead.