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

Security & privacy

What information is public in Explorer?

3 min read

Explorer presents public records and verification evidence, such as identifiers, commitments, network context, and published state. Wallet and ceremony views are not intended to expose account identity, authentication secrets, entropy bytes, or private key shares.

Public evidence is deliberately narrower than an account

Explorer lets people inspect published records without giving them the private account behind those records. A wallet reference, network label, time, or commitment can help establish a particular event. It is not an invitation to retrieve personal details or signing secrets. The record should be interpreted according to what it actually exposes. Do not assume that information absent from the public view does not exist in an authorized private workflow.

What a commitment contributes

A commitment is a cryptographic reference used to check a relationship to particular data without necessarily publishing that data. An everyday analogy is retaining a sealed reference for a later comparison, although the technical mechanism is different. It can support an integrity check: does the material match the reference? It does not automatically disclose the contents, establish that every statement is true, or give the reader permission to open the protected source.

Be careful when combining records

Public information can become more revealing when someone connects several records or adds information from outside the platform. Use the minimum references needed for the task and avoid attaching confidential customer context to a public screenshot. If a record appears to disclose material that should be private, report the exact public location through an appropriate channel without copying the sensitive material more widely. Transparency is most useful when the relevant claim can be checked without unnecessarily exposing the people or documents behind it.

In plain language

Share references, not secrets

A public reference helps someone locate a record without giving them control of it. Examples include an Explorer URL, a transaction hash, a record identifier, and the network name. A secret can provide access or signing power and must be handled differently. Passwords, access tokens, recovery material, and private signing shares do not belong in a support ticket, screenshot, chat message, or public log. Even public identifiers can reveal business activity when combined with other information, so share only what the recipient needs. Before sending a screenshot, check for account details, customer names, browser tokens, and unrelated transactions. A request to “verify your wallet” does not justify revealing recovery material. Use established contact channels and the authorized account workflow. Protecting private information is compatible with transparent evidence: the goal is to demonstrate the relevant fact without publishing everything that sits behind it.

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.

What to do next

Review the scope of the specific evidence page; never put private credentials or recovery material into a public lookup.

Explore public records ↗Wallet privacy boundaries ↗