You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When setting the Tx.deadline field in the Settings Modal below 30 minutes, the value automatically clips to 30 minutes. The modal displays the lower value, but the transaction object stores 30 minutes instead.
Steps to Reproduce
Open the Swap UI and select the token pair to trade.
Open the Settings Modal and set the Deadline to 5 minutes.
Close the Settings Modal.
Reopen the Settings Modal — the Deadline is still set to 5 minutes.
Submit the swap.
View the transaction on Etherscan.
Decode the Input Data.
Notice that the deadline field in the transaction data is creationDate + 30min instead of creationDate + 5min.
Expected Behavior
The transaction's deadline field should equal creationDate + user-specific deadline.
The transaction below demonstrates this behavior, set with a 5-minute deadline but an incorrect deadline field in the transaction data.
When setting the Tx.deadline field in the Settings Modal below 30 minutes, the value automatically clips to 30 minutes. The modal displays the lower value, but the transaction object stores 30 minutes instead.
Steps to Reproduce
Expected Behavior
The transaction's deadline field should equal creationDate + user-specific deadline.
The transaction below demonstrates this behavior, set with a 5-minute deadline but an incorrect deadline field in the transaction data.
https://sepolia.etherscan.io/tx/0xe9dd8a1aa07b78e22155dfc8da929462627bda6c8ffe4ea7f9d1c85fb85e5dc0
The text was updated successfully, but these errors were encountered: