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
So this is a weird situation. I've just called rocketpool node deposit and after setting a rather low max fee (13 gwei) I got an error back saying "FeeTooLowToCompete" I've then called deposit again with a max fee of 14 gwei, this succeeded in creating a transaction.
According to etherscan however, the transaction hash of the second deposit call does not exist however even after waiting for a couple of minutes, while another transaction hash has shown up on the node's address with a max fee of 13 gwei.
It seems like the original transaction was indeed performed and the second transaction never made it to the network (or maybe it will show up later and have the same nonce and just replace, who knows).
In any case this is problematic behavior. I don't know where FeeTooLowToCompete comes from, but I should not be restricted in the transactions I can create even if the max fee is low for the current market climate. What especially shouldn't happen is that I get an error but a transaction is created anyway.
The text was updated successfully, but these errors were encountered:
I get the feeling the 14 gwei transaction never made it to the network as it reused the 13 gwei transactions nonce without being 10% above in fees. Though I have no way to verify that.
So this is a weird situation. I've just called
rocketpool node deposit
and after setting a rather low max fee (13 gwei) I got an error back saying "FeeTooLowToCompete" I've then called deposit again with a max fee of 14 gwei, this succeeded in creating a transaction.According to etherscan however, the transaction hash of the second deposit call does not exist however even after waiting for a couple of minutes, while another transaction hash has shown up on the node's address with a max fee of 13 gwei.
It seems like the original transaction was indeed performed and the second transaction never made it to the network (or maybe it will show up later and have the same nonce and just replace, who knows).
In any case this is problematic behavior. I don't know where FeeTooLowToCompete comes from, but I should not be restricted in the transactions I can create even if the max fee is low for the current market climate. What especially shouldn't happen is that I get an error but a transaction is created anyway.
The text was updated successfully, but these errors were encountered: