-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Setting gasPrice to 0 has no effect (web3 1.0-beta.30) #1458
Comments
I discovered that the following does work, instead of: Probably there's a test somewhere Not sure if this behavior (having to pass |
Can confirm this bug still exists in 1.0.0-beta.33. And can be mitigated with @joeriexelmans's answer above. EDIT: Also can confirm it exists in 1.0.0-beta.36. |
This should be solved with the PR #2000 |
web3: 1.0.0-beta.30 and 1.0.0-beta.31
ethermint: 0.5.3-b72a1eef
go-ethereum: 1.6.7-stable
When sending a transaction, and setting the gasPrice to 0, the gasPrice is ignored and the default gas price is used instead. Other values (1, 2, 1000000, ...) work. This happens when deploying a contract (as shown below in the example code) and also when sending a transaction on an existing contract.
In web3 0.20.6, setting the gasPrice to 0 works fine.
Setting the gasPrice to 0 is useful for private, permissioned networks (e.g. ethermint).
Example code:
Output:
The text was updated successfully, but these errors were encountered: