Submit the last protocol level bug on Taurus. Very happy. I hope the next version of the testnet can abandon these known bugs. Move forward easily and create a more stable and optimized network.
Performance: The subspace transfer protocol is valid and can transfer and receive funds normally. But the Auto EVM cross chain bridge will fail.
The specific repair situation is unknown. But I hope to complete it before the deployment of the main network. I also hope to have time to conduct an effective EVM-AUTO transfer test on Taurus.
Because I know the message, it will be discontinued.
If there are any repair messages. Please inform me as soon as possible. I still need to test once: BSC>EVM>AUTO full range cross link bridge test. This takes a lot of time.
No transactions are being processed on Taurus Auto EVM at the moment. XDM requires Auto EVM transactions to work. Your report is not a protocol bug. The bug is in the GitHub issue you’ve posted above which was discovered by team.
We are working to deploy the fix and bring Taurus back up.
I am the last defender on Taurus. The bug I submitted on August 1st was fixed by you on August 2nd. Although it’s the same issue. But the repairman is your programmer, and the discoverer must be me. This is a matter of principle. I cannot accept the statement that ‘this issue was discovered by the team’.
But: my Tai3 token. It’s just lost! Disappeared and disappeared. Perhaps there exists a sixth space. hash:0xfaedfa6dad3d22ac4ce2a2db83584636b5e097bd18c4e7fd8901a29ad570e986
So this is a protocol level error? Do I still need to wait for repairs? Or don’t you have to worry about it? I insist that it is an undiscovered bug, I have discovered it! Eligible to participate: - Support the-watchers-oath
This is a complete report on the automatic evm transfer lost token event. Protocol level bugs. It has nothing to do with PR # 3661 that you mentioned.
The target of your XDM is 0xA787430FABad34Aa48426D35bb457164a12fc8C9 which did receive the funds in block 2,334,600. You can see the event by querying chain state:
chainState → system → eventSegments
segmentIndex: 0
Blockhash to query at: 0xc6084e668fb583fef0d9f92d71ff3f3d221112ffccc1526f4e448f780c2bf780
@Jeremy_Frank right. My address. Should receive 101357.xxx tai3. But now it is 0. and empty. Not a single coin. So my feedback is that these coins are lost and missing. Disappeared. As an L1 level public chain. Lost token, where can’t I find it? Where is the mistake? Finding the cause and how to fix it is not my job! I also don’t understand technology. I only know that my token is missing. please tell me. Where is my 101357.xxx tai3? I don’t need to know the process or where your technical errors lie. I don’t understand those things. The most intuitive for me. Just tell me where the token is.
I spent 6 days. Just submit a simple task. Is it due to language communication issues? I will recount it again. My original address: subma2BoKZaJRGHRPymDp8JWFB2nXDYMy55JQW6JPwEp5HFyC
Cross chain transfer via auto evm to address: 0x5A32857F4D39832b9C8b6e90bc6A0A0175e66419
The amount is: 101357.xxx tai3
hash:0xfaedfa6dad3d22ac4ce2a2db83584636b5e097bd18c4e7fd8901a29ad570e986
Now, these tokens are lost, gone, lost.
Where the problem lies and how to fix it, it’s not something I can solve. I can’t.
I only know 4 questions:
This is a protocol level program error
Where is the cause, how to fix it, and don’t tell me the repair process. I didn’t get it.
3. Please help me retrieve these tokens as soon as possible after the repair.
4.If it cannot be found. Please tell me the reason. And acknowledge that this is a program error. It’s not my personal mishandling.
The EVM block explorer does not pick up XDM as they happen on the substrate layer. I have verified that your balance increased by the XDM amount in block 2,334,600.
