Skip to main content
ArcBlock Community

Revoke Stake on ArcBridge Node: Bug

Wasil
Support
chain-and-bridgebugqualifiedrewarded

I'm currently in the process of Revoking my Stake and recording it for a tutorial.

I could suspend and leave the Bridge, but when I got to the screen below, I encountered an issue.Screen Shot 2024-05-14 at 12.05.47 AM.png

Once I put in the Revoke amount and signed the message with my wallet to begin the process, this popped up in response.

Screen Shot 2024-05-14 at 12.18.18 AM.png

The account Address it shows is mine as indicated in the image below.

Screen Shot 2024-05-14 at 12.19.56 AM.png

Not sure where to go from here, so I thought to reach out! Thanks for your help in advance!!

7 replies

Wasil2 years ago

And I might as well mention it since we're already here.

In the mobile view, the screen to Revoke the Stake is a little off.

I took a screenshot of it, just so you guys know!!

Not a big deal or anything, but I figured to point it out lol

IMG_6728 2.PNG

wangshijun2 years ago

This seems to be caused by the connected account (the address in your screenshot) never receiving any token on the ArcBlock main chain before (an error is thrown here for safety reasons since the chain can not determine if the address is incorrect)

2 workaround when encountering this situation:

  • Send 0.001 ABT or less to the account in your screenshot (the account can also be found in your bridge-node dashboard member list) on the ArcBlock mainnet, then try revoking it again.
  • Try revoke from your DID Wallet: Mine -> Top Right Icon -> Stakings -> Find your stake and revoke.
Wasil2 years ago

Okay bet, I’ll try that!! Thanks for your help and advice🔥⭐️

wangshijun2 years ago

I noticed this issue when I looked into the transaction history from this node: https://main.abtnetwork.io/explorer/accounts/0x5050DC2990c696fB2B2032F91035D1410ab283eC

Will work on a fix so that things work intuitively.

Wasil2 years ago

Okay cool🔥

wangshijun2 years ago

This issue is fixed in arc-bridge-node v1.4.88, please upgrade your node to latest version.

Wasil2 years ago

bet!!🔥

Reply