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

Failed to EstimateGas by both gasPrice and (maxFeePerGas or maxPriorityFeePerGas) specified #41

Closed
yoshidan opened this issue Apr 25, 2024 · 3 comments

Comments

@yoshidan
Copy link
Contributor

yoshidan commented Apr 25, 2024

I had a failed to estimate gas when I called CreateClient.
The cause is both gasPrice and (maxFeePerGas or maxPriorityFeePerGas) specified here is the log.

{"time":"2024-04-25T20:00:12.83226+09:00","level":"ERROR","source":{"function":"github.com/hyperledger-labs/yui-relayer/log.(*RelayLogger).Error","file":"/Users/yoshidan/go/pkg/mod/github.com/hyperledger-labs/yui-relayer@v0.4.22/log/slog.go","line":72},"msg":"failed to estimate gas","module":"ethereum.chain","chain_id":"ibc0","error":"both gasPrice and (maxFeePerGas or maxPriorityFeePerGas) specified","stack":"both gasPrice and (maxFeePerGas or maxPriorityFeePerGas) specified\n(1) attached stack trace\

estimatedGas, err := c.client.EstimateGasFromTx(ctx, tx)

In ethereum, this is thought to occur here.
https://github.com/ethereum/go-ethereum/blob/b20b4a71598481443d60b261d3e5dcb37f8a0d82/internal/ethapi/transaction_args.go#L137

The reason is that gasPrice and gasTipCap and gasFeeCap of the returned tx from SendTx is not null.

スクリーンショット 2024-04-25 20 15 02

Environment

Chain

  • bsc v1.2.10 and v1.4.5

Module

  • go-ethereum v1.13.8
  • ethereum-ibc-relaye-chain v0.2.14 and latest
@bluele
Copy link
Member

bluele commented Apr 28, 2024

The same problem seems to occur using besu. @siburu

@siburu
Copy link
Contributor

siburu commented May 1, 2024

Thank you for reporting this problem.

I guess that this is caused by the change in toCallArg.

@bluele
Copy link
Member

bluele commented May 2, 2024

This issue is fixed at #42 @yoshidan

@bluele bluele closed this as completed May 2, 2024
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

3 participants