Arbitrum Bridge withdraws displayed as success

gomesalexandre commented 2 weeks ago

Overview

Currently in all envs, Arbitrum withdraws (ARB -> ETH) are detected as success as soon as the inbound Tx is complete:

However these take ~6-7 days to complete, and eventually require a claim.

That's as opposed to Arbitrum deposits (ETH -> ARB) which take ~5-15mn, and we have proper polling for success, meaning when we show success, the bridge is actually a success.

In an effort to make the experience feel more streamlined and less broken in the app, we should improve this from a product perspective so that this success step looks different from the regular one, and users are clearly informed that their swap is not complete but only their inbound is, as well as getting a gentle reminder (they have already been warned with an ack before bridging) that they will require a claim Tx in ~x days.

References and additional details

Spotted while testing https://github.com/shapeshift/web/pull/7876

Acceptance Criteria

Success step for Arb withdraws doesn't look broken

Need By Date

No response

Screenshots/Mockups

No response

Estimated effort

No response

gomesalexandre commented 2 weeks ago

@twblack88 needs product

twblack88 commented 2 weeks ago

~~We probably need an inbound step and something to indicate that the claim is pending.~~

Scratch that, we have one. https://www.figma.com/design/IAtOWIGhClYAj7dxC4CzhJ/ARB-Bridge?node-id=601-5371&node-type=frame&t=6H4wWqWxVs09eu10-0

We mocked a claim status button, UX would just send user to see pending claim and expose the claim tab on the swapper.

0xean commented 1 week ago

update copy to show "Successfully initiated bridging Fox to Eth"
update transaction copy to state "Bridge Initiated..."
Add a button to view status of claim

shapeshift / web