{"id":11741,"date":"2026-08-07T14:21:45","date_gmt":"2026-08-07T12:21:45","guid":{"rendered":"https:\/\/decjaradost.cuprija.edu.rs\/sr\/?p=11741"},"modified":"2026-08-07T14:21:45","modified_gmt":"2026-08-07T12:21:45","slug":"wrong-network-when-exchanging-bnb-pre-transfer-safety-check","status":"publish","type":"post","link":"https:\/\/decjaradost.cuprija.edu.rs\/sr\/uncategorized\/wrong-network-when-exchanging-bnb-pre-transfer-safety-check-11741\/","title":{"rendered":"Wrong Network When Exchanging BNB: Pre-Transfer Safety Check"},"content":{"rendered":"<p><img decoding=\"async\" src=\"https:\/\/decjaradost.cuprija.edu.rs\/sr\/wp-content\/uploads\/2026\/08\/uncategorized_471727.jpg\" alt=\"A user compares the BNB network, destination address, transaction amount, and exchange order details before approving a crypto transfer\" width=\"100%\" loading=\"eager\" fetchpriority=\"high\"><\/p>\n<p>A BNB transfer can reach a valid-looking address and still fail to be credited if the sender and recipient use different networks. This pre-operation check is designed to catch that mismatch before funds leave your wallet. It cannot eliminate every technical, operational, compliance, phishing, or market risk, and a completed checklist is not a guarantee of successful processing.<\/p>\n<h2>Express check: stop signals before sending BNB<\/h2>\n<p>Do not approve the transaction if any of these conditions applies:<\/p>\n<ul>\n<li>The sending wallet shows one network while the exchange order or deposit page specifies another.<\/li>\n<li>The network is identified only as \u201cBNB,\u201d without a precise network name.<\/li>\n<li>You selected BNB Smart Chain because the address begins with <code>0x<\/code>, but the receiving platform has not explicitly confirmed that network.<\/li>\n<li>An old guide, saved screenshot, chat message, or search result tells you to use BNB Beacon Chain or BEP2. BNB Beacon Chain was shut down on December 3, 2024, and its remaining recovery process is limited rather than a normal transfer route. <sup><a href=\"https:\/\/docs.bnbchain.org\/bc-fusion\/overview\/\" data-openai-citation=\"true\" rel=\"nofollow noopener noreferrer\" target=\"_blank\" aria-label=\"Reference 1: Overview - BC Fusion\">[1]<\/a><\/sup><\/li>\n<li>The order requires a Memo or Tag, but the wallet transaction does not include it or shows a different value.<\/li>\n<li>The destination address changed after you copied it, or the beginning and ending characters no longer match.<\/li>\n<li>The asset, amount, fee, or estimated amount to receive changed without a clear explanation before confirmation.<\/li>\n<li>The page asks for a seed phrase, Secret Recovery Phrase, private key, or wallet backup.<\/li>\n<li>Someone is rushing you to send BNB while promising guaranteed returns, account protection, or recovery of previous losses.<\/li>\n<\/ul>\n<p>A BNB symbol alone does not identify the blockchain. BNB Smart Chain mainnet uses chain ID 56, while opBNB is a separate Layer 2 network with chain ID 204; both use BNB as their native currency symbol. <sup><a href=\"https:\/\/docs.bnbchain.org\/bnb-smart-chain\/developers\/wallet-configuration\/\" data-openai-citation=\"true\" rel=\"nofollow noopener noreferrer\" target=\"_blank\" aria-label=\"Reference 2: Wallet Configuration - BNB Smart Chain (BSC)\">[2]<\/a><\/sup><\/p>\n<h2>Two-pass pre-operation verification card<\/h2>\n<p>Complete the first pass while preparing the exchange. Perform the second pass immediately before the irreversible wallet confirmation. Use current information displayed by the wallet, the receiving service, and the appropriate blockchain explorer rather than relying on memory.<\/p>\n<h3>Pass 1: verify the operation context<\/h3>\n<table>\n<caption>Context checks before creating or funding the exchange order<\/caption>\n<thead>\n<tr>\n<th scope=\"col\">Check<\/th>\n<th scope=\"col\">What to compare<\/th>\n<th scope=\"col\">Independent confirmation<\/th>\n<th scope=\"col\">What a discrepancy means<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Domain and session<\/td>\n<td>Confirm that the domain, certificate status, page language, order interface, and support channel are the ones you intended to use. Open the service independently rather than through an unsolicited message.<\/td>\n<td>Compare the address bar with a previously verified bookmark or the service information obtained through a trusted channel. Check whether a browser extension or advertisement redirected you.<\/td>\n<td>An unfamiliar spelling, extra word, unusual subdomain, certificate warning, or forced redirect is a stop signal. Do not connect a wallet or send funds.<\/td>\n<\/tr>\n<tr>\n<td>Exchange direction<\/td>\n<td>Verify which asset you are sending and which asset you expect to receive. \u201cSend BNB\u201d and \u201creceive BNB\u201d are different operation directions.<\/td>\n<td>Compare the order summary with the balances and asset labels in your sending and receiving wallets.<\/td>\n<td>If the source and destination assets are reversed or unclear, do not create or fund the order.<\/td>\n<\/tr>\n<tr>\n<td>Current BNB availability<\/td>\n<td>Confirm that BNB is currently supported for the required direction, pair, and network. Support for the asset does not imply support for every possible pair or blockchain.<\/td>\n<td>Use the live order interface and current service conditions. Do not treat an old article or previous transaction as proof of present availability.<\/td>\n<td>If the desired pair or network is absent, disabled, or ambiguous, clarification is required before proceeding.<\/td>\n<\/tr>\n<tr>\n<td>Exact sending network<\/td>\n<td>Compare the full network name in the wallet with the network required by the order. Distinguish BNB Smart Chain, opBNB, Ethereum, and any other offered route rather than relying on the BNB ticker.<\/td>\n<td>Check official network documentation and the explorer associated with the selected chain. For BNB Smart Chain mainnet, official documentation identifies chain ID 56; opBNB mainnet uses chain ID 204. <sup><a href=\"https:\/\/docs.bnbchain.org\/bnb-smart-chain\/developers\/wallet-configuration\/\" data-openai-citation=\"true\" rel=\"nofollow noopener noreferrer\" target=\"_blank\" aria-label=\"Reference 2: Wallet Configuration - BNB Smart Chain (BSC)\">[2]<\/a><\/sup><\/td>\n<td>Different names or chain IDs mean the networks are not interchangeable. Stop unless the receiving side explicitly supports the exact selected network.<\/td>\n<\/tr>\n<tr>\n<td>Receiving network<\/td>\n<td>Verify that the destination platform will credit BNB arriving on exactly the network selected in the sending wallet.<\/td>\n<td>Use the current deposit or order page generated for this operation. If necessary, request confirmation through the platform\u2019s official support channel before sending.<\/td>\n<td>A valid address format is not enough. Ethereum and BNB Smart Chain can display similarly formatted addresses, so a matching-looking <code>0x<\/code> address does not prove network compatibility. <sup><a href=\"https:\/\/academy.binance.com\/ur-PK\/articles\/how-to-recover-crypto-transferred-to-the-wrong-network-on-binance\" data-openai-citation=\"true\" rel=\"nofollow noopener noreferrer\" target=\"_blank\" aria-label=\"Reference 3: How to Recover Crypto Transferred to the Wrong Network on Binance\">[3]<\/a><\/sup><\/td>\n<\/tr>\n<tr>\n<td>Mainnet rather than testnet<\/td>\n<td>Confirm that the wallet is connected to the production network required by the order, not a test network or manually added network with a similar name.<\/td>\n<td>Compare the wallet\u2019s chain ID and explorer with official network documentation. BNB Smart Chain testnet uses chain ID 97, while its mainnet uses 56. <sup><a href=\"https:\/\/docs.bnbchain.org\/bnb-smart-chain\/developers\/wallet-configuration\/\" data-openai-citation=\"true\" rel=\"nofollow noopener noreferrer\" target=\"_blank\" aria-label=\"Reference 2: Wallet Configuration - BNB Smart Chain (BSC)\">[2]<\/a><\/sup><\/td>\n<td>A testnet selection means the displayed assets may have no relation to the mainnet exchange order. Stop and switch only after independently confirming the correct network.<\/td>\n<\/tr>\n<tr>\n<td>Address source<\/td>\n<td>Confirm that the destination address came directly from the active order or current deposit page and belongs to the selected asset and network.<\/td>\n<td>Reopen the order in a separate trusted session and compare the address. If a QR code is used, compare the decoded address shown by the wallet with the text displayed by the service.<\/td>\n<td>If the order page, QR code, clipboard, and wallet show different addresses, assume possible substitution or an expired order. Do not send.<\/td>\n<\/tr>\n<tr>\n<td>Memo or Tag requirement<\/td>\n<td>Check whether the receiving service displays a Memo, Tag, or other destination identifier in addition to the address.<\/td>\n<td>Use the current order or deposit instructions for that exact network. Do not copy a Memo from an earlier transaction.<\/td>\n<td>If an identifier is required and missing, or if two pages show different values, the payment may not be credited automatically. Stop and obtain clarification.<\/td>\n<\/tr>\n<tr>\n<td>Amount boundaries<\/td>\n<td>Verify that the amount you intend to send satisfies the conditions displayed for the current order and excludes any network fee deducted by the sending wallet.<\/td>\n<td>Compare the order amount with the wallet\u2019s final debit breakdown. Use only current values shown during the operation.<\/td>\n<td>If the wallet will deliver less than the required amount, or the conditions are unclear, adjust only after confirming how the fee is charged.<\/td>\n<\/tr>\n<tr>\n<td>Estimated amount to receive<\/td>\n<td>Review the asset, quoted amount, rate basis, and any displayed fee or adjustment before accepting the order.<\/td>\n<td>Compare the detailed order summary with the final confirmation screen. Treat the live order terms as dynamic rather than assuming that an earlier quote still applies.<\/td>\n<td>An unexplained change requires clarification. Crypto prices and quotes can move, and no rate or final value should be assumed before the order is fixed under the displayed terms.<\/td>\n<\/tr>\n<tr>\n<td>Verification conditions<\/td>\n<td>Check whether the operation displays any identity, source-of-funds, compliance, or additional-information requirements.<\/td>\n<td>Review the current conditions for the specific direction before creating the order. Requirements may depend on the transaction route and compliance results.<\/td>\n<td>If you cannot satisfy a displayed requirement or the applicable conditions are unclear, do not send funds in anticipation that the issue will resolve later.<\/td>\n<\/tr>\n<tr>\n<td>Information freshness<\/td>\n<td>Check the order status, creation time, validity indicator, network availability, and whether any values have refreshed.<\/td>\n<td>Reload the active order through the verified domain and compare it with the wallet confirmation screen.<\/td>\n<td>An expired order, changed address, disabled network, or replaced quote means the old instructions must not be used.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>Pass 2: repeat the critical checks at wallet confirmation<\/h3>\n<table>\n<caption>Final comparison immediately before the transaction is broadcast<\/caption>\n<thead>\n<tr>\n<th scope=\"col\">Check<\/th>\n<th scope=\"col\">What to compare<\/th>\n<th scope=\"col\">Independent confirmation<\/th>\n<th scope=\"col\">What a discrepancy means<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Asset and network<\/td>\n<td>Read the asset name and full network name again on the wallet\u2019s confirmation screen.<\/td>\n<td>Compare them side by side with the active order. Confirm the chain in the wallet\u2019s network selector, not only the token symbol.<\/td>\n<td>If either differs, reject the wallet transaction. Do not assume that the service will convert or bridge a wrong-network deposit.<\/td>\n<\/tr>\n<tr>\n<td>Destination address<\/td>\n<td>Compare the first and last characters and, where practical, the complete address shown in the wallet with the order address.<\/td>\n<td>Return to the active order through the independently verified domain. Avoid using clipboard history or a message from another person as the reference.<\/td>\n<td>Even a one-character difference is a stop signal. Recopying without investigating may repeat clipboard malware substitution.<\/td>\n<\/tr>\n<tr>\n<td>Memo or Tag<\/td>\n<td>If the order requires one, compare every character and confirm that the wallet will transmit it as part of the transaction.<\/td>\n<td>Use only the identifier on the active order page.<\/td>\n<td>A missing, modified, or misplaced identifier can prevent automatic assignment of the deposit. Cancel the transaction and clarify the required format.<\/td>\n<\/tr>\n<tr>\n<td>Amount sent<\/td>\n<td>Check the amount that will reach the destination separately from the total amount leaving the wallet.<\/td>\n<td>Review the wallet\u2019s network-fee treatment and compare the net transfer amount with the order requirement.<\/td>\n<td>If the fee reduces the delivered amount below the order value, do not broadcast the transaction until the amount has been corrected under the current conditions.<\/td>\n<\/tr>\n<tr>\n<td>Network fee and total debit<\/td>\n<td>Confirm the network fee, total wallet debit, and asset used to pay gas.<\/td>\n<td>Compare the wallet\u2019s final breakdown with the balance available on the selected network.<\/td>\n<td>An unexpectedly large fee, an unfamiliar fee asset, or a request to approve an unrelated token or contract requires investigation.<\/td>\n<\/tr>\n<tr>\n<td>Expected receipt<\/td>\n<td>Recheck the destination asset and current estimated amount to receive.<\/td>\n<td>Compare the final order summary with the values accepted when the order was created.<\/td>\n<td>If the destination asset changed or the amount moved outside the displayed order rules, pause and request clarification rather than relying on the earlier screen.<\/td>\n<\/tr>\n<tr>\n<td>Order status<\/td>\n<td>Confirm that the order is active and waiting for this payment.<\/td>\n<td>Refresh the order through the verified site without using a link from a new email or direct message.<\/td>\n<td>Do not send to an expired, cancelled, completed, or replaced order.<\/td>\n<\/tr>\n<tr>\n<td>Final authorization<\/td>\n<td>Verify that the wallet is asking you to send the intended BNB transaction, not to reveal credentials, sign an unrelated message, or grant token permissions.<\/td>\n<td>Read the wallet prompt in full and compare its action with the operation you initiated.<\/td>\n<td>An unexpected signature, approval, network switch, or credential request is a stop signal.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>After completing both passes, one possible next step is to <a href=\"https:\/\/wall-street.exchange\/en\/usdttrc20-to-daibsc?ref=decjaradost.cuprija.edu.rs\">check the current BNB exchange conditions<\/a>. Confirm that the required direction and exact network are available before creating a request.<\/p>\n<h2>How to classify the result<\/h2>\n<h3>You may continue checking<\/h3>\n<p>This status applies when the domain is independently verified, the exact sending and receiving networks match, the address and any required Memo or Tag agree, the order remains active, and the amount fields are internally consistent. It means only that no discrepancy has been found so far. Perform the second pass before authorizing the transfer.<\/p>\n<h3>Clarification is required<\/h3>\n<p>Pause if a network name is abbreviated, a pair is unavailable, a Memo requirement is unclear, the delivered amount may differ because of the fee, the quote changed, or compliance conditions have not been established. Use the service\u2019s official channel and refer to the order identifier without disclosing wallet secrets.<\/p>\n<h3>Stop the operation<\/h3>\n<p>Stop if the domain appears false, the networks differ, old BEP2 instructions are being used, the address changed unexpectedly, the order expired, or anyone requests a seed phrase or private key. Also stop if the transfer is tied to an unsolicited promise of guaranteed profit or a claim that sending BNB will \u201cprotect\u201d or unlock your funds. The FTC identifies guaranteed crypto returns and demands to move cryptocurrency for protection as common scam indicators. <sup><a href=\"https:\/\/consumer.ftc.gov\/articles\/what-know-about-cryptocurrency-scams\" data-openai-citation=\"true\" rel=\"nofollow noopener noreferrer\" target=\"_blank\" aria-label=\"Reference 4: What To Know About Cryptocurrency and Scams | Consumer Advice\">[4]<\/a><\/sup><\/p>\n<h2>Control route before, during, and after the transfer<\/h2>\n<h3>Before broadcast<\/h3>\n<ol>\n<li>Open the order through the verified domain.<\/li>\n<li>Complete both passes of the verification card.<\/li>\n<li>Make sure the order is active and waiting for payment.<\/li>\n<li>Confirm the exact network in both the order and wallet.<\/li>\n<li>Reject the transaction if the address, Memo, amount, or expected receipt changes without explanation.<\/li>\n<li>If the value is material to you and the service conditions permit it, consider whether a small preliminary transfer is appropriate. A test transfer can confirm some routing details, but it creates another transaction, incurs another network fee, and does not guarantee that a later transfer will succeed.<\/li>\n<\/ol>\n<h3>While waiting<\/h3>\n<p>Keep the order page available, but do not repeatedly resend the payment. Copy the transaction ID, or txid, from the sending wallet and inspect it in the explorer for the exact network used. A transaction visible on the wrong explorer is evidence of a network mismatch, not proof that the intended recipient received it correctly.<\/p>\n<p>Distinguish between these states:<\/p>\n<ul>\n<li><strong>Not found:<\/strong> the wallet may not have broadcast the transaction, the txid may be incomplete, or you may be checking the wrong explorer.<\/li>\n<li><strong>Pending:<\/strong> the transaction has been broadcast but has not yet reached the required blockchain status.<\/li>\n<li><strong>Confirmed on-chain:<\/strong> the blockchain recorded the transfer, but the receiving service may still be matching it to the order or performing applicable checks.<\/li>\n<li><strong>Failed:<\/strong> the explorer reports that the transaction did not complete as intended; inspect the status and wallet balance before attempting anything else.<\/li>\n<\/ul>\n<h3>After confirmation<\/h3>\n<p>Compare the explorer\u2019s network, sender, recipient, transferred asset, amount, txid, and status with the order. Then verify the service-side status and the amount credited or exchanged. Do not treat a blockchain confirmation as evidence that an unsupported-network deposit will be credited.<\/p>\n<h2>If the status is delayed, the amount differs, or order data changed<\/h2>\n<p>Do not create another payment until the first transaction has been diagnosed. A second transfer can complicate identification and increase the potential loss.<\/p>\n<ol>\n<li><strong>Verify the network first.<\/strong> Open the explorer corresponding to the chain selected in the sending wallet. Confirm that the txid exists there.<\/li>\n<li><strong>Check the transaction result.<\/strong> Record whether it is pending, confirmed, replaced, dropped, or failed, using the explorer\u2019s actual terminology.<\/li>\n<li><strong>Compare the destination.<\/strong> Match the on-chain recipient with the address from the relevant order. If they differ, preserve the evidence and contact the wallet or receiving service as appropriate.<\/li>\n<li><strong>Check the transferred value.<\/strong> Distinguish the amount sent from the fee and from the amount expected after the exchange. Do not assume that a difference is automatically an exchange error.<\/li>\n<li><strong>Review the Memo or Tag.<\/strong> If the order required an identifier, confirm whether it was included correctly.<\/li>\n<li><strong>Capture the changed fields.<\/strong> If the address, quote, amount, or status changed, record the previous and current non-secret values and the approximate time each was displayed.<\/li>\n<li><strong>Contact the relevant provider.<\/strong> For a custodial destination or exchange, recovery from an unsupported network depends on that platform\u2019s technical capabilities and policies and is not guaranteed. <sup><a href=\"https:\/\/academy.binance.com\/ur-PK\/articles\/how-to-recover-crypto-transferred-to-the-wrong-network-on-binance\" data-openai-citation=\"true\" rel=\"nofollow noopener noreferrer\" target=\"_blank\" aria-label=\"Reference 3: How to Recover Crypto Transferred to the Wrong Network on Binance\">[3]<\/a><\/sup><\/li>\n<li><strong>Reject unsolicited recovery offers.<\/strong> Do not pay someone who contacts you claiming they can retrieve the transfer. The FTC warns that recovery offers can themselves be scams. <sup><a href=\"https:\/\/consumer.ftc.gov\/consumer-alerts\/2022\/11\/worried-about-crypto-exchange-losses-dont-pay-money-help-recovering-money\" data-openai-citation=\"true\" rel=\"nofollow noopener noreferrer\" target=\"_blank\" aria-label=\"Reference 5: Worried about crypto exchange losses? Don\u2019t pay money for \u201chelp\u201d recovering money | Consumer Advice\">[5]<\/a><\/sup><\/li>\n<\/ol>\n<p>If BNB was sent using an obsolete BNB Beacon Chain route, do not follow random migration instructions or connect a wallet to an unverified recovery site. Official BNB Chain documentation states that Beacon Chain has been shut down and that only eligible mirrored BEP2 assets can use the remaining recovery process; recovery availability is therefore not universal. <sup><a href=\"https:\/\/docs.bnbchain.org\/bc-fusion\/overview\/\" data-openai-citation=\"true\" rel=\"nofollow noopener noreferrer\" target=\"_blank\" aria-label=\"Reference 1: Overview - BC Fusion\">[1]<\/a><\/sup><\/p>\n<h2>Threats directly related to a wrong-network BNB transfer<\/h2>\n<h3>Phishing and false order pages<\/h3>\n<p>A phishing page can reproduce an exchange interface while replacing the deposit address or inventing a network requirement. Treat advertisements, shortened links, direct messages, and \u201csupport\u201d accounts that contact you first as untrusted entry points. If the page asks you to restore or synchronize a wallet by entering its recovery phrase, close it.<\/p>\n<h3>Clipboard address substitution<\/h3>\n<p>Malware can replace a copied address with an attacker\u2019s address. Checking only that the pasted string begins with <code>0x<\/code> will not detect this. Compare the beginning and end, and preferably the full destination, after pasting and again on the hardware wallet or software wallet confirmation screen.<\/p>\n<h3>Wrong network despite a familiar address<\/h3>\n<p>BNB Smart Chain and Ethereum use compatible address formats, which makes visual assumptions especially dangerous. The destination may look valid on both networks while the receiving platform supports only one of them. Network selection must match explicitly on both sides. <sup><a href=\"https:\/\/academy.binance.com\/ur-PK\/articles\/how-to-recover-crypto-transferred-to-the-wrong-network-on-binance\" data-openai-citation=\"true\" rel=\"nofollow noopener noreferrer\" target=\"_blank\" aria-label=\"Reference 3: How to Recover Crypto Transferred to the Wrong Network on Binance\">[3]<\/a><\/sup><\/p>\n<p>Similarly, BNB Smart Chain and opBNB are separate networks even though both use BNB for gas. Selecting opBNB when the order requires BNB Smart Chain is not a harmless label difference. Their official mainnet chain IDs are 204 and 56 respectively. <sup><a href=\"https:\/\/docs.bnbchain.org\/bnb-opbnb\/get-started\/network-info\/\" data-openai-citation=\"true\" rel=\"nofollow noopener noreferrer\" target=\"_blank\" aria-label=\"Reference 6: Network Information - opBNB\">[6]<\/a><\/sup><\/p>\n<h3>Seed phrase or private-key exposure<\/h3>\n<p>An exchange transfer requires a public destination address and, in some cases, a public transaction identifier or Memo. It does not require you to send a seed phrase or private key to the recipient or support agent. Anyone with those secrets may control the associated wallet assets. Official MetaMask guidance states that Secret Recovery Phrases and private keys must not be shared, including with someone claiming to provide support. <sup><a href=\"https:\/\/support.metamask.io\/start\/user-guide-secret-recovery-phrase-password-and-private-keys\" data-openai-citation=\"true\" rel=\"nofollow noopener noreferrer\" target=\"_blank\" aria-label=\"Reference 7: How to secure your Secret Recovery Phrase and password | MetaMask Help Center\">[7]<\/a><\/sup><\/p>\n<h3>Guaranteed-return pressure<\/h3>\n<p>A BNB exchange should not be confused with an investment guarantee. If another person supplies the destination address and promises fixed profit, doubled funds, risk-free returns, or a special recovery payout, stop before sending. Regulators warn that guaranteed crypto profits and large returns with little or no risk are scam indicators. <sup><a href=\"https:\/\/consumer.ftc.gov\/articles\/what-know-about-cryptocurrency-scams\" data-openai-citation=\"true\" rel=\"nofollow noopener noreferrer\" target=\"_blank\" aria-label=\"Reference 4: What To Know About Cryptocurrency and Scams | Consumer Advice\">[4]<\/a><\/sup><\/p>\n<h2>Minimal record to keep after the operation<\/h2>\n<p>Retain only the non-secret information needed to trace the transaction and discuss it with the relevant service:<\/p>\n<ul>\n<li>order identifier;<\/li>\n<li>transaction ID or txid;<\/li>\n<li>asset and exact network used;<\/li>\n<li>public sending and receiving addresses;<\/li>\n<li>amount sent and the displayed network fee;<\/li>\n<li>any required public Memo or Tag;<\/li>\n<li>order status and relevant timestamps;<\/li>\n<li>screenshots of the order summary and explorer status with unnecessary personal details removed;<\/li>\n<li>support case number, if one is opened.<\/li>\n<\/ul>\n<p>Do not store a seed phrase, private key, wallet password, authentication code, identity document, or unrelated personal information with this record. The practical final check is simple: the BNB ticker, a familiar address format, and a successful wallet broadcast are not enough. The exact network, destination data, active order conditions, and on-chain result must agree.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A BNB transfer can reach a valid-looking address and still fail to be credited if the sender and recipient use different networks. This pre-operation check is\u2026<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/decjaradost.cuprija.edu.rs\/sr\/wp-json\/wp\/v2\/posts\/11741"}],"collection":[{"href":"https:\/\/decjaradost.cuprija.edu.rs\/sr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/decjaradost.cuprija.edu.rs\/sr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/decjaradost.cuprija.edu.rs\/sr\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/decjaradost.cuprija.edu.rs\/sr\/wp-json\/wp\/v2\/comments?post=11741"}],"version-history":[{"count":1,"href":"https:\/\/decjaradost.cuprija.edu.rs\/sr\/wp-json\/wp\/v2\/posts\/11741\/revisions"}],"predecessor-version":[{"id":11742,"href":"https:\/\/decjaradost.cuprija.edu.rs\/sr\/wp-json\/wp\/v2\/posts\/11741\/revisions\/11742"}],"wp:attachment":[{"href":"https:\/\/decjaradost.cuprija.edu.rs\/sr\/wp-json\/wp\/v2\/media?parent=11741"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/decjaradost.cuprija.edu.rs\/sr\/wp-json\/wp\/v2\/categories?post=11741"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/decjaradost.cuprija.edu.rs\/sr\/wp-json\/wp\/v2\/tags?post=11741"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}