What to Share With an XMR Bridge

For an XMR bridge swap, share only the transaction details needed to match your deposit and deliver the other asset; never share keys that control your wallet. The exact request depends on how the service handles swaps and support cases. Ask what each item is for if the request is unclear.

What wallet details can a bridge ask for?

A bridge may ask for information that helps it find a payment and identify where to send the swap output. That can include your deposit transaction ID, the amount you intended to send, an approximate time, and the destination address for the other asset. Share only what the service needs for the case.

Check that the destination address is correct before you submit it; a typo can send funds somewhere you cannot recover them. If the service asks for a screenshot, crop it to the relevant transaction details and remove unrelated balances, account names, or other personal information.

Why does an XMR bridge need transaction details?

The service needs to match your deposit to a swap request, then work out whether it can send the agreed asset to your destination. The steps and information required vary by service. For a closer look at the swap path and what arrives in the wallet, read how an XMR bridge handles a swap.

Monero transaction details work differently from those on many public blockchains: the protocol hides key details such as amounts and addresses from public view. A transaction ID can help a service locate a payment, but it does not give the service control of your wallet. A view key, by contrast, can reveal some wallet activity, so do not share one casually.

Which wallet information should stay private?

Never send a seed phrase, private spend key, wallet password, or remote access to your device. Those can let someone take control of your funds. A support agent does not need them to check a transaction.

• Share a transaction ID only through the service’s verified support channel.
• Share a destination address only after checking the asset and network.
• Ask why a request needs a view key or extra wallet data before sharing it.
• Ignore requests to install software or hand over control of your screen.

If a request goes beyond basic transaction details, pause and verify it through the service’s official site or app. Watch for whether the bridge explains what data it needs, how it will use it, and what to do if a deposit is delayed.