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.

Sign up for GitHub

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

Jump to bottom

Why we use eth_traceCall instead of eth_estimateGas? #90

Closed
ghost opened this issue May 31, 2017 · 2 comments
Closed

Why we use eth_traceCall instead of eth_estimateGas? #90

ghost opened this issue May 31, 2017 · 2 comments

Comments

@ghost
Copy link

ghost commented May 31, 2017

https://github.com/ethereum/wiki/wiki/JSON-RPC#eth_estimategas
@ghost
Copy link
Author

ghost commented May 31, 2017

Isaak said: w/r/t traceCall vs. estimateGas ->
traceCall can be used for an arbitrary block number and will also return returnValue, while
estimateGas uses PendingBlockNumber and just returns gas

@elaineo
Copy link
Contributor

elaineo commented May 31, 2017

Yes, also contracts can change their behavior based on the order of different tx's submitted to it.
Issue duplicated here: #32

@ghost ghost closed this as completed May 31, 2017
@snyk-bot snyk-bot mentioned this issue Sep 10, 2020
Open
@snyk-bot snyk-bot mentioned this issue Sep 24, 2020
Open
@snyk-bot snyk-bot mentioned this issue Dec 23, 2021
Open
@snyk-bot snyk-bot mentioned this issue Jan 18, 2022
Open
@snyk-bot snyk-bot mentioned this issue Aug 29, 2022
Open
@ali8889 ali8889 mentioned this issue Nov 23, 2023
Open
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@elaineo