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

Business use cases

Can finance oversee multiple networks through a common workflow?

3 min read

A shared operational view can make network context and evidence easier to review consistently. The useful outcome is a team that can identify what happened and where it happened without losing the distinctions between chains.

Consistency helps reviewers ask the same questions

A common workflow can show the asset, network, amount, state, and evidence reference in a consistent way. Finance can then compare related activity without learning an entirely different reporting style for each source. The consistency should help reviewers identify what happened and where, not conceal network differences. A useful report makes it possible to move from a summary to the supporting record when a number or status needs explanation.

Do not combine unlike balances

Keep Mainnet value separate from Testnet or Devnet activity. Distinguish assets by their network and identifier, not just the ticker. Also separate an observed deposit from an available balance and a reserved amount where those concepts apply. If a report converts values into a common currency, retain the price source and time used for that view. A convenient total is not a substitute for the underlying quantities and their actual operating meaning.

Design the view around finance’s decisions

Ask which questions the team needs to answer: pending receipts, unexplained fees, unmatched payments, or evidence for a particular period. Keep reporting access separate from spending authority. Test the proposed view with representative records and an exception that needs investigation. Have a reviewer reconstruct the result from the links rather than relying on the developer’s explanation. This shows whether the common presentation genuinely supports oversight while preserving the relevant facts of each network.

Illustrative example

A treasury report groups activity by network and asset, with links to the relevant underlying records.

In plain language

The network is part of the address and asset

A currency symbol is a convenient label, not a complete destination. Two networks can use similar-looking addresses, and tokens with the same ticker can exist on more than one chain. The safe description includes the asset, its network, and any chain-specific token identifier, as well as the recipient address. Mainnet, Testnet, and Devnet are also separate contexts: a test balance is not a production balance simply because both screens show a familiar name. Before any external transfer, obtain the receiving details from the intended, authorized wallet workflow and compare the network at both ends. Do not choose a different network just because it appears cheaper without confirming the whole route. A shared application can make these choices easier to manage, but it cannot erase the differences between the underlying chains. If the destination or route is unclear, stop before authorizing the transfer and ask for clarification.

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.

Conditions & limitations

Do not combine test credits with production value or treat similarly named tokens as interchangeable. Reporting access also does not grant spending authority.

What to do next

Define the network and asset breakdowns your finance team needs and test them against representative records.

Funding & Settlement ↗Public Explorer ↗