-
Notifications
You must be signed in to change notification settings - Fork 19
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
implement eth_getCode (which currently is hardcoded to return 0x01) #428
Comments
otselnik
added a commit
that referenced
this issue
Jan 27, 2022
otselnik
added a commit
that referenced
this issue
Feb 1, 2022
otselnik
added a commit
that referenced
this issue
Feb 3, 2022
otselnik
added a commit
that referenced
this issue
Feb 3, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I reported this on Telegram (to the "focus group" channel I was asked to join and which I've since escaped) I reported this as being an issue with empty contracts, as I'm used to seeing a similar issue--returning "0x00" instead of "0x"--on new JSON/RPC implementations (at least rsk and Telos that I remember made that mistake). However, reading your code, I see that you've simply not implemented this API. I use this API a lot, so I hope you get around to implementing it before you launch.
https://github.com/neonlabsorg/proxy-model.py/blob/43f6e8bacbcbfadb2ddbefa084350de2364c9a88/proxy/plugin/solana_rest_api.py#L391-L392
┆Issue is synchronized with this Jira Task by Unito
The text was updated successfully, but these errors were encountered: