Skip to content
Universe Wallet

What this release authorizes

That figure comes from the wallet’s own generated capability summary, which is the only source this documentation is permitted to make a version or capability claim from. It is copied into this repository as capability-snapshot.json and every count on this site is rendered from it, so the two cannot drift apart.

Why zero

Section titled “Why zero”
Why an action appears only when evidence covers the whole path behind itA protocol action such as transferring a token has six links behind it: the wallet code that builds and signs the transaction, the Universe API that serves the data, the indexer that decides what the transaction meant, the network the transaction is broadcast to, the confirmation that it was accepted, and reconciliation showing that the indexer and the wallet agree afterwards. A release authorizes that action only when current evidence exists for every link, bound to the exact source commit of that build. If a single link lacks evidence, the action is not authorized. An unauthorized action does not fail when you press it: the screen loads and states that the operation is not available in this build, and names what is missing, rather than offering an action that would break. Two outcomes are shown side by side, the authorized path leading to a usable action and the unauthorized path leading to the not available screen. A closing note records the state of the committed baseline, which authorizes nothing at all on purpose.CODE EXISTING IS NOT SUPPORTEvery link needs current evidenceWalletcodeUniverseAPIIndexermeaningNetworkbroadcastConfirmacceptedReconcileagreesIs every link proved, for this exact build?Checked per protocol, per network, per operation.yesnoThe action is thereAuthorized for this build, this protocol,this network, this operation. Nothing wider.Not available in this buildThe screen opens, says so, and nameswhat is missing. It does not half work.WHERE THE COMMITTED SOURCE STANDSThe baseline in the repository authorizes nothing, deliberately. Authorization is attached at releasetime, to one exact build. So the only honest answer to "is it supported" is: look at your own screen.

An operation is authorized only when current evidence exists for every link behind it, bound to the exact commit of the build. The baseline in the repository carries none, on purpose, so that a build can never inherit an authorization it did not earn.

The rule the product applies is: code existing is not support. A route existing is not availability. A parser existing is not wallet support. Authorization is attached at release time, per protocol, per network, per operation, from evidence covering the wallet, the API, the indexer, the network, confirmation, and reconciliation.

One qualification campaign has completed, scoped to Zerdinals and ZRunes, producing an authorization covering thirteen operations across those two protocols against one candidate commit. That artifact has not been published. See Which version you are running.

What is still true with zero authorized

Section titled “What is still true with zero authorized”

The parts of the wallet that carry no protocol gate work regardless: creating and importing wallets, receiving, addresses and address types, network switching, connections, the security dashboard, locked-coin and coin-health views, the address book, and activity.

The parts that carry a protocol gate, including ordinary Bitcoin sending, depend on what your build authorized. The screen tells you. See Why an action is unavailable.

How to read a claim anywhere else

Section titled “How to read a claim anywhere else”

If a page, a listing, a social post, or a person tells you a protocol action works in Universe Wallet, the way to check is not to ask them. Open the screen. If the operation is not authorized in your build, the screen says so and names what is missing.

Section titled “Related”