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

eth_call doesn't specify behaviour when Block parameter is omitted #461

Open
SamWilsn opened this issue Aug 17, 2023 · 4 comments
Open

eth_call doesn't specify behaviour when Block parameter is omitted #461

SamWilsn opened this issue Aug 17, 2023 · 4 comments

Comments

@SamWilsn
Copy link

What is the behaviour when you don't specify a block? Should it default to latest?

@s1na
Copy link
Contributor

s1na commented Sep 19, 2023

In Geth block is mandatory and an error will be raised if its not given. But I think it makes sense to default to latest. Happy to submit a PR if other clients agree. In fact we plan to do that for eth_multicall #383.

@SamWilsn
Copy link
Author

I'd have no problem with changing:

required: false

To:

required: true

If that's less work.


if other clients agree

Like on ACD, or can this be more informal?

@s1na
Copy link
Contributor

s1na commented Sep 20, 2023

Ah I didn't know the spec says optional. I just opened ethereum/go-ethereum#28165

@s1na
Copy link
Contributor

s1na commented Sep 26, 2023

Geth defaults to "latest" now.

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

2 participants