Skip to content

Coverage beyond the marketplace

Source bitcoinuniverseio/core (private)
Path backend/packages/ecosystem-contracts/lib/protocols.js
Chain bitcoin, dogecoin, zcash
Network mainnet
Verified 2026-09-01

The registry holds 38 protocols. Twenty-nine have a marketplace policy and appear in the support matrix. The other nine have none at all, and this page is where they live.

The in-app /coverage pageThe support matrix here
AnswersWhat does this build read and serve?What can Core do with it?
Generated fromThe routing registry the running application usesThe marketplace registry the backend enforces
RowsEvery protocol with an index or a market routeThe 29 with a marketplace policy
Good forFinding a protocol’s index or market pageDeciding whether you can trade

Read them together. Coverage tells you a page exists. The matrix tells you what the page will let you do when you get there.

Covered means Core reads the protocol and serves it here.

It does not mean:

  • that Universe operates the index behind that row. A row naming a read source is fetched by your browser straight from that host, and a read that does go through Core may itself come from an external provider;
  • that a market has listings right now;
  • that a market has depth or liquidity;
  • that every action is available for that protocol.

A market with nothing listed says so. A market whose reader failed says that instead, and offers a retry. The two are never presented the same way, so an empty table is never a way of hiding an outage.

These are read, explored, or inscribed. None of them can be listed, bought, or sold in Core, and there is no gate to open that would change that: the registry records no marketplace policy for them at all.

ProtocolChainIn CoreIn sibling surfaces
Bitcoinbitcoinbitcoinviewdiscoverview-collectionview-activityview-transactionWallet: view, send, receive, split, combine
SRC-101src101bitcoinviewdiscoverview-collectionview-activityview-transactionWallet: view, send, receive · Inscribe: mint, transfer
Atomicalsatomicalsbitcoinviewdiscoverview-collectionview-activityview-transactionWallet: view, send, receive · Inscribe: mint, transfer
AVMavmbitcoinviewdiscoverview-collectionview-activityview-transactionWallet: view, send, receive · Inscribe: deploy
BLOCK-20block20bitcoinviewdiscoverview-collectionview-activityview-transactionWallet: view, send, receive · Inscribe: deploy, mint, transfer
CAT-721cat721bitcoinviewdiscoverview-collectionview-activityview-transactionWallet: view, send, receive
ZerdinalszerdinalszcashreadexploreNone.
ZRuneszruneszcashreadexploreNone.
ChainBloomchainbloombitcoinviewdiscoverview-collectionview-activityview-transactionWallet: view, receive · Inscribe: inscribe

Three of those deserve a note.

  • Atomicals appears here as the umbrella protocol, while its four tradable members (ARC-20, Atomicals NFTs, Realms, Subrealms) each have their own marketplace row in the matrix.
  • Zerdinals and ZRunes settle on Zcash and are recorded with read and explore only. Their own documentation is at docs-zerdinals-and-zrunes.
  • CAT-721 has no recorded inscribe or marketplace actions, in contrast with CAT-20 which has a testnet-gated trade preview.

TAP, DMT, and UNAT carry a read source on the in-app coverage list, and the same sentence appears again on their index pages beside the numbers it applies to. Their deployment, mint progress, and holder figures are read by your browser from a host Universe does not operate, so their availability and freshness are that host’s rather than Core’s.

Every other row is read through the Core API. That API may in turn read an external provider for a given protocol, which is what /indexer-health reports per protocol.

  • The home screen links to it from the first paragraph.
  • The footer links to it from every page.
  • Its address is https://www.bitcoinuniverse.io/coverage.