From the wrong link to the manual verification: the BVM Canary cross-chain recharge appeal will be improved and the full record will be improved
(Contract the previous article: Recharge by mistake, dismissed for the first complaint, and the second contact with Binance manual customer service successfully submitted an asset recovery application)
1. After the appeal is submitted: enter the link to improve the information
InlastIn the process of Binance manual customer service, I have successfully submitted an application for BEVM Canary recharge recharge recharge, prepaid 20 USDT handling fee, and the work order officially entered the manual review queue.
After the appeal is submitted, enterApplication details improvement stage, the platform system prompts that you need to fill in the relevant information of the refund, the core requirements are: must be filled inbevm networkThe external wallet refund address, and the Binance platform’s own address cannot be used, and strictly follow the original return rules.
As shown in Figure 1, the application details page clearly states that the network belongs to BeVM, which can only be returned in the same chain, and does not support cross-chain replacement of other public chain addresses.
At this point I immediately realized a key real problem:
I’ve already found out Bevm Canary (ChainID:1501) official block browsers and public RPC nodes have long been unable to use, the page cannot be opened, and the transaction cannot be packaged and confirmed. If the original wallet address is filled as required and returned, the assets will only be locked on this almost paralyzed chain, which is equivalent to a permanent loss.
2. Connect to the manual customer service again, and report that the network is really abnormal
After realizing that there is a major asset risk in the original route, I did not directly fill in the address and submit, but contacted the Binance manual customer service again to truthfully conduct in-depth feedback and communication.
I have a complete explanation of the situation to the customer service:
I can provide the original wallet address of the Bevm Canary network as required, but the current front-end service of the chain is completely abnormal, the block browser cannot be accessed, and the on-chain transaction cannot be confirmed for a long time, and ordinary users cannot collect and transfer money normally. If the original road is forced to be returned, the assets will be directly stuck in the chain and cannot be removed and used. It is hoped that the platform can face up to the current situation of the network and give a reasonable solution.
As shown in Figure 3, in the process of communication with customer service, the platform still adheres to the unified rules: asset recovery is only supportedReturn with the original network, the system and technical level do not allow cross-chain to change the refund network. The customer service said that it can only wait for the background team to review according to the process, and it is temporarily impossible to make an exception.
As shown in Figure 4, Binance feedback said that the BVM blockchain link and the corresponding network can still be opened normally and initiate a transfer. Therefore, it is recommended that I further check whether there is a wallet or platform that supports the token of BEVM network, so as to receive refund assets in the future.
3. Go to the official GEB community to verify the true running status of the chain
The exchange only talks about the rules and is inflexible. In order to get the evidence, I joined the official Chinese community of GEB Community, and directly verified the true state of the BEMM Canary canary chain with the project party administrator.
As shown in Figure 5, the project administrator gives a clear official reply:
The underlying node of BEVM canary (chainid:1501) is currently out of the normal block, which can be transferred normally;There are no asset migration programs from beginning to end.
This reply makes the situation very embarrassing:
The project party only sees whether the underlying node is blocked, and determines that the network is normal; the exchange only requires the original path to be returned according to the rules; but from the actual use point of ordinary users, this chain browser cannot be opened, the node is unstable, and the transaction is stuck, and there is no normal collection conditions at all.
At the same time, browsing other users in the community and found that there are also users who cross-chain transactions have timed out, but in the later stage, they are slowly credited to the account, further confirming:The chain is only the height of the underlying block growing, and the external public service is extremely unstable..
4. Self-tested by many parties: the chain is high, and the service is completely paralyzed
In order to objectively verify the status of the network and keep the complete complaint evidence, I will measure it through the multi-dimensional measurement of the tools and wallets on the chain.
As shown in Figure 6, search the BEVM Canary network on the ChainList official website, you can clearly seeThe block height continues to rise in real time, the high value of the chain remains dynamically updated, which is also the core basis for the project party to determine the normal network.
But it is seriously contradicted by:
Bevm Canary Official Block Browser https://scan-canary.bevm.io It is always impossible to open, the page parsing fails, and it is completely impossible to query the transaction hash, block details and other on-chain information.
I use the MetaMask little fox wallet, switch to the Bevm Canary (1501) network, and replace multiple sets of official RPC node tests. Discovery is not able to view historical data. as shown in Figure 7
Comprehensive all measured conclusions:
The underlying ledger of BEVM Canary is still out, butThe daily transfer and collection functions of public RPC nodes, block browsers, and users are all paralyzed, no longer have actual use value.
5. Key transfer: Binance backstage self-checks the height of the block on the chain
During the continuous wait-and-see review, I opened the Binance Appeal Application Details page and found a very important change.
As shown in Figure 8, the platform background has independently pulled and verified the data on the BEVM chain, and the page remarks clearly show:Get on-chain data to verify again. Network:BEVM, block height:17988444
This is crucial:
Binance’s official background has successfully captured BEVM Canary’s block height is 17988444. This value is similar to the height of the chain height data I found in Chainlist, indicating that the platform has independently completed the data verification on the chain, and no longer only depends on my unilaterally provide data, and officially enters the stage of in-depth evaluation of special cases.
The platform also recognizes the special situation of this incident, and needs to extend the investigation and review time, and it is no longer a simple mechanical application of the original road return rule.
6. Current progress: wait and see, wait for the final review result
Up to now, the entire wrong-chain recharge appeal incident has advanced to a stable wait-and-see stage:
- Complaint work orders remainmanual reviewstatus, no progress is closed, no refusal notice;
- Binance backend has verified the height of the block on the chain by itself, and mastered the real operation data of the network;
- The project party has no asset migration plan, and the chain can only be held in place, and cannot be replaced across the chain;
- I have kept screenshots of wallets, transaction hashes, browser errors, chainlist high chain, social chat records, customer service communication records and other complete evidence chains.
The best strategy at this stage isWait and wait patiently, infrequently urging singles to disturb the review team, and at the same time, continue to take screenshots to keep the status changes of each work order, so as to use the subsequent supplementary appeal.
Seven, the whole process of review experience
From the initial mistake of recharging the wrong chain, the failure of the first complaint, to the second contact customer service to submit the retrieval application, to the improvement of the information and the feedback network difference Constantly, verify the project party, and measure the status of the chain by itself, until the height of the block is independently verified in the background of Binance. The whole process is tortuous and long.
Also remind all users of the currency circle:
Cross-chain transfers must check the difference between the network name, chainid, mainnet and canary test network again and again; when the project is renamed and the old chain browser is invalid , keep all the screenshot evidence at the first time; when appealing to the exchange, the logic is clear, the evidence is complete, and the cooperation process is the key to promoting the special handling of cases.
I will continue to follow up the whole process of the follow-up review of the work order, the processing of funds, and the final arrival of the account, and the latest progress will be updated in time.
