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

using block numbers against infura that the nodes are not aware of result in miss information #5881

Closed
frankiebee opened this issue Dec 5, 2018 · 1 comment
Closed

using block numbers against infura that the nodes are not aware of result in miss information #5881

frankiebee opened this issue Dec 5, 2018 · 1 comment
Labels
area-blocktracker area-provider Relating to the provider module. type-bug

Comments

@frankiebee
Copy link
Contributor

if you were to query for example getCode with a block number out of bounds of what the node knows the response will be 0x which is a misrepresentation of the current state and can cause gas estimation on transactions to be set to 21000 along with some other nasty side effects.

some solutions could include allowing 'latest' to be passed as the block number instead of trying to fill it with the block-trackers know number on request.

some cases of this:
#5868
#5588
@frankiebee frankiebee self-assigned this Dec 5, 2018
@frankiebee frankiebee added type-bug area-provider Relating to the provider module. labels Dec 5, 2018
@Gudahtt
Copy link
Member

Gudahtt commented Jan 6, 2021

This appears to have been caused by a bug in geth (ethereum/go-ethereum#18254), and has been fixed.

@Gudahtt Gudahtt closed this as completed Jan 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-blocktracker area-provider Relating to the provider module. type-bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bdresser @Gudahtt @frankiebee