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

Getting started

Does a product page mean every feature is available?

3 min read

No. Availability is specific to the product, operation, account, and network. Some public experiences are previews, preparation tools, or read-only evidence. A documented workflow is not a promise that signing, deployment, or settlement is enabled.

Why a public page and an enabled feature differ

A product page explains the intended use and the boundaries of a product. It may describe preparation tools, public evidence, or a limited preview alongside a broader integration path. None of these descriptions changes your account’s permissions. Reading about a withdrawal, for example, is different from having an active withdrawal route. The distinction protects users from confusing a useful demonstration with an instruction to send money or depend on a service that has not been agreed.

Ask what is included in your evaluation

Request a short description of the environment, product, network, and operations available for the test. Ask whether each step is read-only, produces a decision, prepares an unsigned request, or actually executes an action. Also ask what data is suitable and who should be contacted if the result is unclear. These are ordinary planning questions, not specialist cryptography questions. They help the team make a fair comparison and prevent a successful read from being presented as a completed transfer.

How to interpret a successful demonstration

Record exactly what worked. “The application returned the permitted collection” is a stronger result than “the platform works,” because it says what was tested. Keep any prerequisites with the result, including access, configuration, and relevant dates. If the next phase involves production data or value movement, treat that as a new approval decision. Availability can differ by operation and environment, so obtain confirmation for that next phase rather than assuming that the evaluation automatically carries over.

In plain language

What “enabled for your operation” means

A product can support several kinds of activity without making all of them available to every user. For example, reading an existing wallet record is different from creating a wallet, signing a transfer, or withdrawing to another chain. Access can depend on the account, environment, network, product configuration, and required approval. An operation is the exact action you want to take, such as reading a status or requesting a withdrawal. A scope is a limit on what a credential is allowed to request. Seeing a feature in documentation tells you what to investigate; it is not itself an access grant. During an evaluation, ask for a simple list of which actions are enabled, which are read-only, and which are outside the agreed test. Keep that list with your test results. This gives business users and developers the same understanding of what a successful demonstration actually establishes.

In plain language

An example is not a production result

The examples in this FAQ explain how to think about a workflow. They are not reports of customer results, guarantees of performance, or instructions to use real funds. A useful evaluation starts with agreed access, a non-production environment where appropriate, and data that you are permitted to use. Decide in advance what a pass looks like and what must be refused. An allowed case alone is not enough: the team should also try an unauthorized request, a missing requirement, or an unavailable dependency where the test scope permits it. Keep the result and its context so someone else can understand what was demonstrated. Passing that test provides evidence for the tested combination of product, configuration, and environment. It does not automatically enable a different operation or network. Moving to production should be a separate, explicit decision with the required owners involved.

What to do next

Check the product’s access boundary and current API contract, then agree the scope of an evaluation.

Product access boundaries ↗Discuss an evaluation ↗