Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nervos sudt destroy status not updating #316

Open
godpan opened this issue Feb 16, 2022 · 4 comments
Open

Nervos sudt destroy status not updating #316

godpan opened this issue Feb 16, 2022 · 4 comments

Comments

@godpan
Copy link

godpan commented Feb 16, 2022

I have cross-chained back to BSC and Ethereum from Nervos many times. Although the cross-chain was successful in the end, the susd destruction status display in the first step of cross-chain execution has always been stuck. Although the block has been confirmed successfully, the status display has always been It is pending, which causes these cross-chain records to be stuck there. Please solve this problem. The following is the cross-chain I executed on 2022.1.28. Until now, the records are still there.
截屏2022-02-16 下午8 29 16

@cryptowen
Copy link
Contributor

  1. Did you fail to cross-chain or it's just a display error?
  2. If you click the link, could you see the transaction on Nervos Explorer? What's the status of the transaction, success, pending or revert?

@godpan
Copy link
Author

godpan commented Feb 17, 2022

1.cross-chain success, only display error, this problem appeared in the last month.
2.the transaction on Nervos Explorer is exists and it success

so i think the logic of checking for destruction needs to be checked.

@nolanxyg
Copy link
Contributor

1.cross-chain success, only display error, this problem appeared in the last month. 2.the transaction on Nervos Explorer is exists and it success

so i think the logic of checking for destruction needs to be checked.

Sorry for the inconvenience. We are grateful if you could disclose the pending burn tx hash to help us to address the problem.

@golferdaytona
Copy link

Hi mkxbl I just had a very similar issue. Below is my TX hash. Your help is greatly appreciated
0x732c6a384a506c8576a902a51e34f3a2806616949739be07be1e15b5aea28e0d

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants