Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Smartnode reports FeeTooLowToCompete on node deposit, creates transaction anyway #386

Open
Blackclaws opened this issue Jul 27, 2023 · 1 comment

Comments

@Blackclaws
Copy link

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.

@Blackclaws
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant