Error getting refund

[Phread420]

I got a JavaScript error after pressing the "claim funds back" button (error from the Chrome developer console below).

If I press the button again, it eventually works.

error Error: cannot estimate gas; transaction may fail or may require manual gas limit [ See: https://links.ethers.org/v5-errors-UNPREDICTABLE_GAS_LIMIT ] (reason="execution reverted: TimeStamp violation", method="estimateGas", transaction={"from":"0x665967fAf572697E53969C0B7E8BD336b1fAC885","to":"0xdC7650c7562E53115eDB02cCC7bf67FB9F79cfF4","data":"0x1c48c074000000000000000000000000000000000000000000000000000000000000024d","accessList":null}, error={"code":-32603,"message":"Internal JSON-RPC error.","data":{"code":3,"message":"execution reverted: TimeStamp violation","data":"0x08c379a00000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000001354696d655374616d702076696f6c6174696f6e00000000000000000000000000"},"stack":"{\n "code": -32603,\n "message": "Internal JSON-RPC error.",\n "data": {\n "code": 3,\n "message": "execution reverted: TimeStamp violation",\n "data": "0x08c379a00000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000001354696d655374616d702076696f6c6174696f6e00000000000000000000000000"\n },\n "stack": "Error: Internal JSON-RPC error.\n at new i (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-2.js:1:308657)\n at a (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-2.js:1:311413)\n at Object.internal (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-2.js:1:312023)\n at c (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/background-3.js:3:25295)\n at chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/background-3.js:3:26327\n at async chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-5.js:19:40569"\n}\n at new i (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-2.js:1:308657)\n at a (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-2.js:1:311413)\n at Object.internal (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-2.js:1:312023)\n at c (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/background-3.js:3:25295)\n at chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/background-3.js:3:26327\n at async chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-5.js:19:40569"}, code=UNPREDICTABLE_GAS_LIMIT, version=providers/5.6.8)
at o.makeError (_app-187b717325aa234f.js:13:162610)
at o.throwError (_app-187b717325aa234f.js:13:162724)
at s (_app-187b717325aa234f.js:13:245063)
at as. (_app-187b717325aa234f.js:13:254098)
at Generator.throw ()
at h (_app-187b717325aa234f.js:13:244180)

[compojoom]

Hi there!
Thanks for the report. I've seen this behavior myself, but currently don't have an idea how to prevent it. My guess is that it happens because we calculate a timestamp when the swap should expire. In the UI we are comparing this timestamp every second to the current time. But when we try to submit a tx to the chain, we are dealing with the the block.timestamp and the block timestamp is not updated every second. So when the UI calculates that the swap has expired the current block.timestamp is behind the swap timestamp and the RPC node says that the tx will fail. So once a new block gets minted we get an updated block.timestamp which is now after the swap timestamp and the rpc node now lets you submit the TX.