-
Notifications
You must be signed in to change notification settings - Fork 20.1k
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
Need to throw error when methods are called at future blocks #18254
Comments
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 0.404 ETH (39.03 USD @ $96.62/ETH) attached to it as part of the MetaMask fund.
|
💰 A crowdfund contribution worth 20.00000 DAI (20.0 USD @ $1.0/DAI) has been attached to this funded issue from @.💰 Want to chip in also? Add your own contribution here. |
Thank you Dan for the excellent writeup of the problem. We pitched in on the Gitcoin. |
As I mentioned at ethereum/EIPs#1474 (comment) I'd be happy to work on PRs to address issues like this if a standard on the response is finalized (which is why I raised it as part of that EIP discussion since I think the clients should agree on the error returned). |
@ryanschneider That proposal in its current state is simply a reformatting of the existing wiki, but has become overloaded with a number of changes to the provider. Because this is an urgent issue that is breaking many dapp dev experiences, I think we should definitely implement a fix before waiting for all methods to be "finalized" (whatever that would mean). |
i have reach the code below ## ethclient/ethclient.go
## 335: err := ec.c.CallContext(ctx, &result, "eth_getBalance", account, toBlockNumArg(blockNumber)) @danfinlay can you guide me to indicate where is rpc api implement code. new comer to go-ethereum codebase. could you do me favor? |
@xiaods I am not actually a regular contributor (nor do I know any go), or I'd submit the change myself. |
@danfinlay got it. let me have a try. |
sorry for the late active response. i will follow this issue now. i will update it asap. 😄 |
This issue has a much larger impact than I think anyone is appreciating. Here's another confused person today: |
@danfinlay i found currently the project missing many more testing for this apis. i can't easily to handle the logic. so i try to add more testing to reproduce the bug, the we can easily to fix it asap. |
i have merged #18346 to my patch, it look good first. |
any update? |
…ture blocks -[x] add unit test for StorageAt rpc call -[x] Return error message on future block -[x] add TransactionCount rpc call unit testing Signed-off-by: Deshi Xiao <xiaods@gmail.com>
@adamschmideg any update on it? |
Fixed in #18346 |
@fjl got it, see this like promise patch |
Not sure how @gitcoinbot works, but the bounty for the #18346 PR should go to @shibli , not me |
This is now implemented, credits to @shibli |
Issue Status: 1. Open 2. Cancelled The funding of 0.404 ETH (59.81 USD @ $148.06/ETH) attached to this issue has been cancelled by the bounty submitter
|
System information
Geth version: 1.8.15 (Infura)
OS & Version: Linux
Commit hash :
Expected behaviour
Geth should throw an error when making a request on a future block.
Actual behaviour
Many types of request simply return
null
or0x
when theblock
parameter is an integer for a future unknown block.This is especially troublesome for clients that hit load-balanced geth clusters like Infura, where one request for latest block could return one number, and then suddenly requests at that block height could start returning
null
and0x
, resulting in inconsistent client app state.In short: This is the cause of many bugs in MetaMask and Dapps building on MetaMask, and probably other similar clients as well, and there is no way for us to detect or work around this issue without a fix in Geth.
Steps to reproduce the behaviour
This bug can be reproduced with many methods that we're aware of, and probably many more are possible.
getStorageAt
of a known contract (mkr
) on a future block:Returns
{"jsonrpc":"2.0","id":914762274,"result":"0x"}
, as if the contract were never published.eth_getTransactionCount
of an account with some mined transactions, on a future block:Returns
{"jsonrpc":"2.0","id":6972925150872393,"result":null}
, as if there were no error. At least this value can possibly be detected as invalid.eth_getBalance
on an account with some ether, on a future block:Returns
{"jsonrpc":"2.0","id":2366105135518150,"result":null}
, as if there were no error. At least this value can possibly be detected as invalid.Related to #3483.
The text was updated successfully, but these errors were encountered: