HYBRID DEVNET · PUBLIC EVIDENCE LIVEVerifiable infrastructure for value, markets, identity, and operational dataInspect the network

Explorer & evidence

What is the difference between a ceremony and a wallet record?

3 min read

A ceremony is the process and audit trail behind a wallet attempt, not the wallet itself. The wallet record presents published wallet evidence and readiness. An enrollment without a matching published ceremony remains publication-unconfirmed, not a completed or failed ceremony.

A ceremony records the process

A ceremony is a coordinated attempt to complete a wallet-related process under its required conditions. Its record can show stages, participants’ evidence, and an ending state. It is useful for understanding how an attempt progressed. It is not itself a spendable wallet or proof that a current operation is enabled. An attempt can expire or stop while its history remains available for review, just as a closed application file remains part of an administrative history.

A wallet record describes a different subject

The wallet record concerns the wallet and its published context or readiness. There may be multiple historical attempts associated with a wallet journey. Read the links and references rather than assuming that the newest ceremony or the most favorable historical label establishes current capability. A wallet’s network and exact operation still matter. Activation evidence, signing health, and funding permission may be presented separately because they answer different questions.

How to read an incomplete journey

An enrollment with no matching published ceremony should remain unconfirmed in that public view. It should not be silently promoted to completed, and it should not be described as failed without evidence. Compare the account workflow with the public records if you need to continue an action. For an investigation, keep the enrollment, ceremony attempt, and wallet identifiers labeled separately. That gives the team a clear trail without treating every record as an alternative name for the same thing.

In plain language

Permission, signing, and completion are different

Think of a business bank payment: preparing the instruction, approving it, and seeing it complete are separate events. A wallet workflow also has distinct responsibilities. Authorization means the required person or policy permits a particular action. Signing means the participating systems produce the cryptographic signature needed for that action. Completion means the relevant system has accepted or settled the result under its rules. A screen displaying a wallet, or a service responding successfully, does not combine these steps into one. In Hybrid-Chain, customer authorization is separate from distributed signing participation. When reviewing a status, ask which of these stages it describes, which asset and network it concerns, and whether the evidence is current. This distinction helps prevent a common mistake: treating an informational record as permission to move money. An operator should be able to explain the stage in ordinary language without asking you to share any secret material.

In plain language

Why several reference numbers can describe one journey

A business request, a payment-provider record, a Hybrid-Chain event, and an external blockchain transaction can each have their own identifier. These are not competing names for the same database row. They identify different parts of a journey, just as an order number and a parcel tracking number describe related but different records. Keep the relationship between them rather than overwriting one with another. A hash is a compact cryptographic fingerprint used to identify or commit to data; a UUID is another kind of record identifier. Neither should be interpreted from its appearance alone. Use the label beside it and the system that issued it. When asking for help, include the network and the type of reference as well as the value. This makes it much easier to distinguish a missing link from a failed operation and avoids searching an external chain for an internal reference.

What to do next

Use the ceremony directory for attempt history and the wallet page for the current published wallet context.

Ceremony directory ↗Wallet directory ↗