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

Wallets & recovery

What happens if Hybrid-Chain or a required signing service is unavailable?

3 min read

Separate control of assets from the availability of the services needed to use them. Even a customer-controlled design can depend on signing participants, coordinators, network access, or a recovery process being available.

Control does not guarantee instant access

A system may prevent a provider from spending your funds while still depending on services to help you use them. Signing participants, coordination, connectivity, and the external network can each affect availability. Self-custody concerns authority; availability concerns whether the supported path can operate now. Keeping these concepts separate helps a business ask useful questions instead of assuming that one security property guarantees every operational property.

Understand the actual dependencies

Ask which services and participants are required for your intended operation, whether alternatives exist in the supported configuration, and how interruptions are reported. A threshold arrangement can tolerate some unavailable participants only if the required threshold and other dependencies remain satisfied. Independence also matters: several systems relying on the same failing provider may not offer the resilience suggested by their count. These properties must be established for your deployment, not inferred from a generic architecture.

Have a plan for uncertain results

If a request times out during an outage, first establish whether it was accepted before submitting another consequential action. Keep the original reference and any published result. Tell users what is known, when it was last checked, and which next step is supported. After service returns, reconcile pending work rather than assuming that everything failed or completed. A rehearsed continuity plan should cover both access during interruption and the safe handling of operations whose outcome was temporarily unknown.

Illustrative example

An evaluation disables an agreed dependency and checks which reads, approvals, and signing operations remain possible.

In plain language

Recovery is an authority decision, not just a backup

A backup helps preserve information; a recovery process determines how access or authority can be restored when something is lost or unavailable. Those are related but different jobs. For a business wallet, the plan should say who can start recovery, what evidence they must provide, who approves it, and what old access is removed afterward. It should also explain what happens if the usual person, device, or service cannot participate. A process that quietly lets one provider replace the customer’s authority may change the practical custody model, even if everyday signing uses several participants. Do not assume a support team can override the rules or retrieve lost signing material. Ask for the supported procedure for your exact deployment and rehearse it in an agreed safe environment. Record responsibilities and escalation contacts without storing secret recovery material in the same document as ordinary operating instructions.

In plain language

A public record is evidence with a specific scope

An Explorer record is closer to a receipt or an entry in a logbook than to a live control panel. It describes something published about a particular event, object, or process. Some entries include links that let you examine the earlier steps or the underlying transaction. A record can remain useful after it becomes old: it may establish what was recorded at that time. It does not necessarily describe what the system can do now. Look at the record type, network, time, source, and stated verification result together. Missing information means the public view cannot establish that fact; it is not a reason to invent a positive or negative result. Private account records may contain additional context that is deliberately absent from Explorer. This is why a screenshot is a starting point for investigation, while the exact record and its supporting references are much more useful for reaching a conclusion.

Conditions & limitations

Self-custody is not a promise of uninterrupted access or an independent exit route. These properties must be demonstrated for the specific configuration.

What to do next

Request the dependency map, continuity plan, and supported recovery procedure; record observed results separately from documented plans.

Wallet availability and recovery checklist ↗