Skip to content
Universe Wallet

Capability evidence

Most wallets describe support by listing what the code can do. Universe Wallet does not, because a list of what the code can do is a list of things that might work, presented as things that do.

The rule

Section titled “The rule”

Code existing is not support. A route existing is not availability. A parser existing is not wallet support.

An operation is authorized only when the exact build carries current, verified evidence for the complete path behind it.

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.

Six links, all of which must carry evidence bound to the exact source commit of the build. One missing link means the operation is not authorized, and the screen says so.

What is checked

Section titled “What is checked”

The release matrix carries one row for every protocol, network, and operation combination, with UI, provider, API, signer, indexer, health, evidence, and release-state classifications. In 1.7.5.8 there are 42 protocols and 1,551 operation rows, and 0 authorized operations.

Authorization is produced for an immutable workflow run, not copied by hand into a document. The generated readiness record contains the exact source commit, the workflow run id, individual gate results, the protocol matrix checksum, and the exact extension artifact checksum. A go decision is possible only when every gate succeeds, the artifact is checksum-bound, and every intended protocol operation is evidence-backed. Zero functional coverage is always a no-go.

What this means when you read a claim

Section titled “What this means when you read a claim”

Any statement that Universe Wallet supports a protocol is checkable, and the way to check it is not to ask the person who said it.

  1. Open the screen in your own wallet.
  2. If the operation is not authorized in your build, the screen says so and names what is missing.
  3. That screen is authoritative for you. This documentation is not, and neither is a store listing, a social post, or a support reply.

Why the committed baseline is empty

Section titled “Why the committed baseline is empty”

Deliberately. Authorization is attached at release time to one exact build. If the baseline carried authorizations, a build could inherit a claim it never earned, which is precisely the failure the system exists to prevent.

So gated-blocked in the wallet’s own route inventory means “not authorized in the committed baseline”, not “permanently unreachable”.

The one campaign that has completed

Section titled “The one campaign that has completed”

A qualification campaign scoped to Zerdinals and ZRunes completed on 30 August 2026 against one candidate commit. Every release gate passed and an authorization covering thirteen operations across those two protocols was produced. The matrix regenerated from it authorizes 26 of its 1,595 rows and nothing outside that scope.

That artifact has not been published. See Which version you are running.

Section titled “Related”