Hi guys, I executed a swap transaction today (Jan 8, 2026 at ~1:59 PM UTC) through Zashi that has failed, and approximately $4,800 worth of my ZEC is now missing
TRANSACTION DETAILS:
Amount swapped: 12,293 ZEC -
Expected output: 4,789.13 USDT -
Transaction ID: 0x749044bdc7d06e841f07aeb6d28754d0b76317de68ef133d2702d371e70a830c - Recipient address: 0xbc037d4a93d89df31c4a50c57c64e60d05ab20c8 -
Zashi status: “Completed” - BSCScan status: “Transaction Hash not found” PROBLEM: - Zashi claims the transaction is “Completed” - The transaction hash does not exist on BSCScan (BSC network explorer) - The USDT never arrived in my Binance wallet
If both Near and Bsc are evm-compatible chains and you have the private key linked to that address, maybe you can control the assets on near as you’re doing on bsc. I’m not sure, but you can try with a near wallet importing your bsc seed phrase… Search for confirmations!
Hi @quantumboy23, in looking up the swap details, I can see the selected asset was USDT-on-NEAR, which was completed successfully:
NEAR Intents swaps support a number of assets, chains, and L2s. This includes USDT-on-BNB, but also on NEAR, ETH, Base, etc.
It’s unfortunate that the selected asset wasn’t the one you had intentioned. Because so many of these assets are available across multiple EVM-compatible chains (which use ETH-style 0x… addresses), it’s very important to ensure the correct one is chosen.
However, so long as you own the keys to the address, it can be recovered. And if not by you, the counterparty has that possibility as well.
This is correct. With the private key to the address, you can import it into Metamask, and then use the ‘Login with Ethereum’ button on the Welcome to NEAR site to access the funds.
@BostonZcash is there any way you can contact me and help? I’m bit confused and don’t want to make any mistakes. I messaged email support number of times but received no response. I have all the credentials to my zashi app and binance as well (this is the one where I was sending USDT)
I believe NEAR tokens use ED25519 keys for address derivation, and Ethereum uses secp256k1. Unlikely that it’s possible to recover , but what is really strange is that NEAR didn’t validate the address type or check that there is a valid account. Worth contacting NEAR to check the details of the smart contract, and why it was reported as a success instead of being refunded. The smart contract code appears to be here: Tether-Near/src/lib.rs at main · tetherto/Tether-Near · GitHub
Address verification for the appropriate network should definitely be implemented, even a simple regex. And maybe it would be worth including UI to recommend performing a test transaction before sending large amounts.
It’s worth trying this, but most likely the NEAR/ETH account bridge smart contract will need to have been registered before the funds were sent to the NEAR address.
You send USDT on NEAR whereas the exchange expected it on BSC. The only way to resolve it is to ask if the exchange can recover funds. They are the ones that own the private key to that address.
Thanks for the details and your patience. We are currently moving to a new e-mail support system due to the company change, but we’re available here and over Discord and X to help in the interim.
I see from the screenshot that USDT-over-NEAR was selected. If you intend to send USDT to a BNB Smart Chain address, it will need to specifically be USDT (BNB Chain), as shown below:
As mentioned, EVM addresses (0x…) are valid across the majority of USDT options pictured above, so it really is critical to select the correct chain.
If you sent to a Binance exchange address, it will be Binance which owns the keys to that address, and they have the sole ability to credit or refund the deposit.
I wish we could be of further help in this, but unfortunately it is out of the hands of both Zashi and NEAR, as NEAR sent the funds over the selected chain and the funds are with the recipient. I certainly do hope you’re able to arrange a successful outcome with Binance.
I’m sorry that there isn’t more that be done for this situation, though at this point, it’s in the hands of Binance and ultimately up to them. Perhaps someone here has a suggestion for ways to escalate a request with Binance.
, but what is really strange is that NEAR didn’t validate the address type or check that there is a valid account. Worth contacting NEAR to check the details of the smart contract, and why it was reported as a success instead of being refunded. The smart contract code appears to be here: 
