Inform user when they have token balances in the wallet due to a "refund"

[ewingrj]

We need to inform the user when they have a balance of any bridge currency in their Rinkeby wallet.

This should also include a button that will easily allow the user to withdrawal the funds via the bridge

[GriffGreen]

Showing another user how to do it now :-(

[GriffGreen]

https://rinkeby.etherscan.io/tx/0x63c47cc37a91f80be103b5ea1ea367b1af4bba23aaea0935b2229027d3487e8d#decodetab

Thats how i did it the first time...

here are the instructions i'm giving to someone else:

go here: https://rinkeby.etherscan.io/address/0xff9cd5140e79377feb23f6dfaf1f8b558c0fe621#writeContract

Click "Connect with metamask"

make sure your metamask is set to the address that asked for the refund (and has the tokens in it)... it should be this address: https://rinkeby.etherscan.io/token/0xe3ee055346a9efaf4aa2900847deb04de0195398?a=0xc38f6a88b03fb2322d9815f043b5713afc3aad49

scroll down to "withdraw" and put those things in

Recipient: 0xc38f6a88b03fb2322d9815f043b5713afc3aad49 SideToken: 0xe3ee055346a9efaf4aa2900847deb04de0195398 Amount: 25e18

(NOTE: 25e18 is 25 eth in wei... 25 followed by 18 0's)

Click the write button and in like 5 minutes you will end up with the ETH in your wallet

[geleeroyale]

Thank you @GriffGreen for these step by step instructions. I need to rescue some DAI - not ETH from the contract. I tried to do it like you wrote here, but I get execution reverted.

This is how it looks for me before sending - I try to liberate 25.89590400 DAI

[ewingrj]

note: recipient should be where you want the funds to be withdrawn to. It will take 2-3 days for the funds to end up in your wallet, not 5 mins due to the security delays on the bridge.

For DAI use 0xb5afaed1ae9b0485a859023e1372c100b11e98ab as the sideToken address

[geleeroyale]

Thank you with the correct token address - it seems like it worked. Can confirm after delay period!

[papermache]

@geleeroyale Is this fixed?

[geleeroyale]

I love Griff's description. Not sure anybody had that problem recently. Did not create the issue, I was somebody affected.

@GriffGreen I guess these instructions stay valid still. We should save it and collect it in the docs?

[mosaeedi]

@MoeNick