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

Funding & transfers

What is my Hybrid address, and how do deposits and withdrawals work?

3 min read

Your Hybrid address is an encapsulating identifier linked to your identity within Hybrid-Chain. It provides a common reference for your Hybrid-Chain wallet context, rather than replacing the native addresses used by individual external chains. It is not a Bitcoin, Ethereum, or Solana receive address: Layer-1 funds must be sent to the correct chain-specific wallet address.

Layer 1: deposits from an external chain

In your authorized wallet workflow, select the asset and network and confirm that deposits are enabled. Use the native receive address provided for that exact chain and network, including a memo or tag if required. Send from the external wallet on the matching network, then track the transaction’s confirmations or finality and the funding record. Do not paste the Hybrid identifier into an external wallet as a replacement for the native receive address.

Layer 1: withdrawals to an external chain

Select the enabled asset and network, enter the recipient’s native address for that network, and review the amount, network fee, and any required memo or tag. Complete the required customer authorization and signing workflow. Once broadcast, the transfer takes place on the external Layer-1 chain and can be tracked using its transaction hash. A withdrawal request or internal status alone is not proof of an external transfer’s completion.

Layer 2: internal Hybrid-Chain transfers

For supported internal Layer-2 transfers, value can move natively within Hybrid-Chain using the recipient’s Hybrid identifier. These transfers are internal only; they do not by themselves send coins to a Bitcoin, Ethereum, or other external-chain address. Moving value out to Layer 1 requires a separately enabled and authorized withdrawal route.

In plain language

A verified claim is not unlimited permission

An identity credential is a statement made by an issuer about a subject, with a defined meaning and scope. Verification checks the relevant evidence and status; it does not automatically decide what your organization should allow. A simple comparison is an employee badge: it can identify someone without giving them access to every room or permission to approve every payment. Similarly, an identity-linked wallet identifier does not itself reveal a private key or authorize spending. When you rely on a credential, understand who issued it, what they checked, what the claim says, and whether it remains valid for the decision you are making. Avoid treating a broad “verified” label as a substitute for those questions. Your acceptance policy connects the verified claim to the specific action you are considering. Different actions may legitimately require different evidence or additional approval.

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.

Conditions & limitations

An identity-linked identifier is not a private key or permission to spend. Confirm the asset, network, destination, and operation-specific readiness every time. A visible address, wallet enrollment, or passing health check does not by itself enable deposits or withdrawals. Sending to the wrong address or network can result in loss.

What to do next

Use the receive or withdrawal details in your authorized wallet workflow. For an internal transfer, verify the recipient’s Hybrid identifier; for an external transfer, verify the native chain address and matching network.

Inspect wallet evidence ↗Why a deposit may be pending ↗Review funding boundaries ↗