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

rpcdaemon: eth_call returns error when (optional) sender parameter is absent #2017

Closed
sealer3 opened this issue May 10, 2024 · 0 comments · Fixed by #2019
Closed

rpcdaemon: eth_call returns error when (optional) sender parameter is absent #2017

sealer3 opened this issue May 10, 2024 · 0 comments · Fixed by #2019

Comments

@sealer3
Copy link

sealer3 commented May 10, 2024

When trying to query a smart contract, such as like this:

{
	"id": 19,
	"jsonrpc": "2.0",
	"method": "eth_call",
	"params": [
		{
			"data": "0xfeaf968c",
			"to": "0xffe5b13cb108a99edf87926faf09d5008186dd91"
		},
		"latest"
	]
}

Erigon replies with an error saying the sender cannot be recovered:

{
	"jsonrpc": "2.0",
	"id": 19,
	"error": {
		"code": -32000,
		"message": "malformed transaction: cannot recover sender"
	}
}

Note that by default, if a sender isn't given it's assumed to be the zero address.

@sealer3 sealer3 changed the title rpcdaemon: eth_call throws error when (optional) sender parameter is absent rpcdaemon: eth_call returns error when (optional) sender parameter is absent May 10, 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

Successfully merging a pull request may close this issue.

1 participant