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
Description:
I have an transaction with custom/advanced gas settings. This transaction doesn't seem to get included with the current gas cost, so I want to "speed up" this transaction to have a higher possibility to complete within some hour (i'm not in real hurry but do want the tx to get included this day..).
With this said, I do not want to spend more gwei + tip than I need. I still want a lower gas cost than the current base fee (within BlockWallet) offer. The goal is to have the transaction go through, and use lower gwei than BW let me manually choose...
The issue
Im not able to set my new transaction-cost (gwei values) in a advanced way. Blockwallet forces me to use a value higher than the current basefee+tip. I would prefer that the "speed up rule" should be: as long as I enter a higher gas value with than the current/pending transaction (both gas limit and tip), BlockWallet should accept it.
To Reproduce
I want to let this tx have a fair chanse to complete in an hour
Below are the cost values BW gives.
The original cost was 10gwei + 1 gwei tip
I only want to add some more gwei. Not as high as the current base fee! The reason is I’m betting on that the gas-price will go down to my target within some our (otherwise I will need to adjust with new speed up).
It is ok that BlockWallet warns that my values is below current base fee + tip.
However, now Im forced to speed up the transaction with the higher base fee+tips than I'm willing to spend, since BW don't let the transaction update with my custom (but still higher) gwei values. I get this error when submitting:
Desktop (please complete the following information):
OS: Mac OSX 13.0.1
Browser: Chrome v107, Brave Browser v108
Additional context
This has been possible in MetaMask, and I want to be able to adjust the gas spending here as well.
The text was updated successfully, but these errors were encountered:
JeppeP
changed the title
Speed up transaction wierd behavier
Speed up transaction bug
Dec 6, 2022
Description:
I have an transaction with custom/advanced gas settings. This transaction doesn't seem to get included with the current gas cost, so I want to "speed up" this transaction to have a higher possibility to complete within some hour (i'm not in real hurry but do want the tx to get included this day..).
With this said, I do not want to spend more gwei + tip than I need. I still want a lower gas cost than the current base fee (within BlockWallet) offer. The goal is to have the transaction go through, and use lower gwei than BW let me manually choose...
The issue
Im not able to set my new transaction-cost (gwei values) in a advanced way. Blockwallet forces me to use a value higher than the current basefee+tip. I would prefer that the "speed up rule" should be: as long as I enter a higher gas value with than the current/pending transaction (both gas limit and tip), BlockWallet should accept it.
To Reproduce
I want to let this tx have a fair chanse to complete in an hour
![telegram-cloud-photo-size-4-5798783879639841693-x](https://user-images.githubusercontent.com/1104024/206035540-bcf5537c-55b2-428a-9564-82ced56d1dba.jpg)
Below are the cost values BW gives.
![telegram-cloud-photo-size-4-5798783879639841694-y](https://user-images.githubusercontent.com/1104024/206035739-cb5a5dfc-be9f-438f-b1a0-0e3b046d22d4.jpg)
The original cost was 10gwei + 1 gwei tip
I only want to add some more gwei. Not as high as the current base fee! The reason is I’m betting on that the gas-price will go down to my target within some our (otherwise I will need to adjust with new speed up).
It is ok that BlockWallet warns that my values is below current base fee + tip.
Desktop (please complete the following information):
Additional context
This has been possible in MetaMask, and I want to be able to adjust the gas spending here as well.
The text was updated successfully, but these errors were encountered: