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
We are developing a chrome extension-based wallet, called Dekey (www.dekey.app).
It fully supports coin/token transfer and Dapp-browsing in ethereum based chains including layer 2.
Recently, we have completed the development of EIP1559 type 2 tx functions and is testing in various Dapps including Uniswap in ropsten and rinkeby. The production build will be deployed in the chrome app store at the end of this week.
As you know, there is no 'gasPrice' field in the type 2 tx, instead 'maxPriorityFeePerGas' and 'maxFeePerGas' should be inserted. As shown in the attached image, Uniswap interface in ropsten still seems to require 'gasPrice' field in the tx result (delivered by a wallet) though the tx is processed well as a type 2 in the chain (see the following url).
moodysalem
changed the title
Uniswap interface is not compatible with 1599 type 2 tx
Uniswap interface is not compatible with 1559 type 2 tx
Jul 26, 2021
Bug Description
We are developing a chrome extension-based wallet, called Dekey (www.dekey.app).
It fully supports coin/token transfer and Dapp-browsing in ethereum based chains including layer 2.
Recently, we have completed the development of EIP1559 type 2 tx functions and is testing in various Dapps including Uniswap in ropsten and rinkeby. The production build will be deployed in the chrome app store at the end of this week.
As you know, there is no 'gasPrice' field in the type 2 tx, instead 'maxPriorityFeePerGas' and 'maxFeePerGas' should be inserted. As shown in the attached image, Uniswap interface in ropsten still seems to require 'gasPrice' field in the tx result (delivered by a wallet) though the tx is processed well as a type 2 in the chain (see the following url).
https://ropsten.etherscan.io/tx/0x16a6a340df23f7f1978a5b54ff4e648c2c04eae4cf4a701024ac6ef73e7de715
Steps to Reproduce
Expected Behavior
Uniswap interface should process the tx result differently depending on the tx type.
The text was updated successfully, but these errors were encountered: