Hello MetaMask Engineers, I have a critical synchronization bug with the NEAR Protocol Snap. 1. Binance successfully recovered 345.33 NEAR tokens to my MetaMask wallet address via the native NEAR Protocol network. 2. On-chain explorer (Nearblocks) clearly confirms that my address holds the 345.3343 NEAR tokens. 3. I have reinstalled my MetaMask extension on my PC using the 12-word recovery phrase, and the address matches perfectly: 0x0591d23a79fb6a14768d612e41798a7ecf5130ee 4. The official NEAR Protocol Snap is installed and enabled (v1.1.0 or latest). The issue: Despite the Snap being active and the funds being verified on the blockchain, the MetaMask Extension UI and MetaMask Portfolio balance firmly display 0 NEAR. The RPC endpoint of the Snap is failing to fetch or index the balance associated with an EVM-formatted address on the NEAR chain. How can I manually force the Snap’s RPC to fetch the balance or derive the ED25519 private key to move these funds? Thank you.
Hello, thanks for reporting this. If Nearblocks confirms that 345.3343 NEAR tokens are recorded on-chain, but MetaMask shows a balance of 0, the issue is likely related to Snap synchronization or account derivation. Also, the account created with the Snap should be the same address you are using. Please also avoid manually changing the RPC associated with the Snap. Open a MetaMask support ticket and provide the transaction hash, Nearblocks address, Snap version, and screenshots showing the balance discrepancy.
I checked, and around three months ago, 345 NEAR tokens were sent to your Snap address. But this is a bit strange. I couldn’t find any results in the explorer by searching the address, so I tried using the transaction hash to find it. https://nearblocks.io/address/0x0591d23a79fb6a14768d612e41798a7ecf5130ee/receipts Could you try installing a wallet that supports NEAR and importing your MetaMask Snap account into it? You might get an error, but I’m not sure ، maybe it’s supported. Alternatively, you could try connecting to a dApp or bridge that supports the NEAR network using the Snap and see if you can view the balance.
Thank you for your reply. If I understand correctly, the funds are NOT lost or blocked. And Binance is no longer involved, right? Presumably, they were sent correctly? Since my funds are visible on Nearblocks at my MetaMask address, I likely need to claim them using the correct (albeit more complex) method. I’ve tried claiming them with nine different wallets, yet my NEAR still doesn't show up in MetaMask. I’ve tried recovering/claiming them using both the 12-word phrase and the private key, but the result is the same—the balance always shows as zero. Could the funds be blocked in some way, or are they perhaps awaiting additional confirmation? What could be the issue? I would appreciate your help.
Yes, I also think the funds have not disappeared or been blocked; the situation has just become a little more complicated. Even when I check Nearblocks, I can’t see the NEAR token in the Tokens section of the explorer, and even the deposit amount isn’t being displayed correctly. I’ll send you two screenshots. If you look at the “Deposit Value” section, it shows 0 for you, but I happened to find another address where the dollar value is displayed.
Could you tell me how you received this token three months ago? In the screenshot you sent, there is also a site called hot-labs.org. Are you familiar with it? I checked the site as well and found its dApp, bridge, and swap features. Had you used this site before?
I tried using Hot Labs after the funds had already been transferred from Binance. Since I didn’t have any NEAR in the MetaMask account I had provided to Binance, I attempted to access the NEAR via Hot Labs and nine other popular wallets that support the NEAR network/protocol, but none of them worked. I even used AI and followed every step, yet had no success; I spent five hours on it. There must be a trick to it. I understand that it has to operate on the same network, but I don’t get why I can’t access the funds using wallets that support NEAR. The funds are visible on NEARBLOCKS. I assume Binance sent them correctly, right? What do you think? Also, my MetaMask address is definitely correct; otherwise, the funds associated with that address wouldn’t show up on NEARBLOCKS. I’m asking for concrete help. You can charge a fee—just help me unlock the funds. I’m turning to you as experts.
Yes, I agree. In my opinion, this transfer to your address was made about three months ago. I also tried installing the MetaMask Snap, and after installing it, I was prompted to access the NEAR site Hot Labs. I then tried connecting to Hot Labs using the same Snap address, but I didn’t have any balance in the NEAR Snap, so I couldn’t verify it. This is indeed a little strange. Also, how did Binance not give you any warning or error when you made the transfer that this was an EVM address? Even if it was being used for a Snap, you would probably have received some kind of warning from Binance. I’ll send you two links that explain how to use the Snap on the NEAR network. Unfortunately, some of the dApps they recommend are currently not working on the NEAR network. I checked several other dApps as well, but you can also investigate them yourself. In my opinion, you should first try connecting the Snap to a dApp that supports the NEAR network and see whether you can view your balance. You can try different methods, such as WalletConnect or other methods for connecting the MetaMask Snap. This is only one possibility, but you can try it: https://hex.exchange/ This is a site that recommends a Snap for working with the NEAR ecosystem. After you try the dApp and still have the same problem, you should also contact Binance support and ask them how you were able to send NEAR to an EVM address where the balance is not visible. After that, you can contact the NEAR team. They have explicitly stated that NEAR supports MetaMask Snap, but some of the dApps listed in NEAR’s documentation are currently not working. If you still have a problem, please come back again so we can try to connect you with the Snap support team. They may be able to help you. There may also be other options, such as transferring through a contract explorer, but I’m not sure whether NEAR supports this feature. Please try these steps, and never share your private key with anyone. Support teams will never ask you for your private information or private key. Always be careful about scams.
Hey there, the account with the NEAR tokens is 0x0591d23a79fb6a14768d612e41798a7ecf5130ee as you mentioned, but in this post im replying to, your address is actually 0x0591D11B291f06A6F98b36ED086CD8d3aF5130EE while there are similarities with first few and last few characters, this is a whole different address, are you 100% sure you’re in control of the actual 0x0591d23a79fb6a14768d612e41798a7ecf5130ee that you mentioned first?
You dont even need snap for this part, all you have to do is add NEAR RPC, so click where it says “All networks” then “Manage networks”, then “Add a custom network”, you could either do it manually:
