As a bridge user, when I exceed slippage limits I need to be notified and have clear/working options

[alexwhte]

Problem Users can specify slippage limits in the UI. If the limits are exceeded during the transfer, funds can get "stuck" on destination

Ideas to solve this We should notify the user allow them to: A. Re-submit execute with higher slippage (can we recommend the level needed?) B. Receive local on destination instead C. Cancel and return to sender (#1878)

Questions What is the most critical paths for Beta. Would any bridge user ever choose option B? If user cancels and returns to origin, what costs do they incur?

Acceptance Criteria

• [ ] User is notified of the slippage failure
• [ ] User is presented options to proceed If A
• [ ] TBD: User is recommended a new slippage level
• [ ] (If choosing to re-execute) Then user will have an option to resubmit execute with more slippage tolerance If B
• [ ] User instead received local asset (nextAsset?) on destination and can try swapping manually in the UI If C
• [ ] User is effectively paid back on origin chain/wallet.

Other

[alexwhte]

Hardest part is tracking the failure

[alexwhte]

P0

[just-a-node]

There are two parts to this:

1. https://github.com/connext/nxtp/issues/2094
2. https://github.com/connext/nxtp/issues/1878

[alexwhte]

closing as dupe 2094

[alexwhte]

closing as dupe 2094