Skip to content

Core

One explorer, portfolio, and market for the Bitcoin and Dogecoin metaprotocols. Every figure on screen can be traced to the reader it came from, and a reading that failed says so instead of showing a zero.

Core is the Bitcoin Universe application at www.bitcoinuniverse.io. It is four things in one place:

  • an explorer for Bitcoin and Dogecoin blocks, transactions, addresses, and outputs, and for the metaprotocol assets carried on them;
  • a portfolio that groups what an address holds by chain, protocol, and asset type;
  • an activity record of what has traded and what has moved;
  • a marketplace for the protocols whose execution path is complete.

It is for people who read chain data: collectors checking what they own, buyers checking a listing before they sign, and developers checking what an index actually returned. It is non-custodial. Keys stay in the reader’s own wallet, and no action moves an asset without a signature approved there.

Protocols in the registry
38Across Bitcoin, Dogecoin, and Zcash.
With a marketplace policy
29The rest are read and explored, never traded.
Enabled in the build
912 feature-gated, 7 read-only, 1 gated to testnet.
Declare buy support
19Declared in the registry. A live authority gate still has to agree before a purchase can run.
Support listing
20Delist: 19. Update a listing: 16.
Marketplace profile
read-onlyRead on 1 September 2026 fromthe public health response. Mutation traffic was closed. Check it yourself rather than trusting this line.

Read the support matrix

Twenty-nine protocols, thirteen marketplace actions, and the registry’s own reason for every action that is not available. This is the page to read before you assume you can trade something.

The support matrix

Learn to read the states

Unknown is not zero. Empty is not unavailable. Core shows those four things differently on purpose, and reading them wrongly is the fastest way to make a bad decision.

Reading the numbers

Check where a number came from

Every figure has a reader behind it. Some readers are Universe-operated, some are external providers, and three protocols are fetched by your own browser from a host Universe does not run.

Where each number comes from

Trade safely

What to check before you sign, what a fail-closed gate means, and why an unavailable action is a safety decision rather than proof that a market is empty.

Market safety

Call the public API

An OpenAPI 3.1 document covering the public read endpoints, including the health and per-protocol freshness contracts.

Public API

Fix something that looks wrong

A market that says unavailable, a wallet that will not connect, a figure shown as a dash. What each one means and what to do next.

Troubleshooting

ChainNetworks Core servesProtocols in the registry
Bitcoinmainnet33
Dogecoinmainnet3
Zcashmainnet2, read and explore only

A staging deployment exists for validation. It uses its own isolated API lane and never falls back to production data. It is not a place to move real funds.

Core is a running production application. It does not publish a semantic version string: its release identifier is the exact commit the deployment was built from, and the public health response returns it in the release field. That is the only release number this documentation will quote, because it is the only one the product actually states.

This documentation site is versioned with the product it describes and is marked experimental in its manifest for exactly that reason: there is no tagged Core release to point a releaseVersion at, and inventing one would be worse than admitting it.

Core is one product in a wider set. The portal at docs.bitcoinuniverse.io is the entry point for all of them, including Wallet, Inscribe, and StampDEX, which appear in the protocol registry as sibling surfaces alongside Core.