Ganache fork polygon doesn't give the right balanceOf result

[lingmicha]

Hello, I tried to fork a polygon mainnet at block number: 34581439.

the cmd is as follows:
ganache-cli --chain.vmErrorsOnRPCResponse true --server.port 19999 --fork.url https://polygon-mainnet.g.alchemy.com/v2/H3E99oH7XymptRueBxkO4OXXazhFb7_c@34581439

after the local ganache fork is running, i tried to access a aave atoken balance:

curl -H "Content-Type: application/json" -X POST --data \ '{"id":1337,"jsonrpc":"2.0","method":"eth_call","params":[{"from":null, "to":"0x82e64f49ed5ec1bc6e43dad4fc8af9bb3a2312ee","data":"0x70a082310000000000000000000000005b8effbdae5941b938c1a79616d185cc3c79d4ff" }]}' \ http://localhost:19999
But it give a increasing balance that is not fixed at block 34581439. Everytime i call the eth_call, the return figure increases. And it is also not the lastest_block value. That buffles me a lot!

Anyone can point me to the right direction why this happens?

[davidmurdoch]

What version of ganache are you using?

[lingmicha]

I tried the millisecond presentation, the problem stays the same.

Seems to me some inner conflicts introduced by these to options. Without those two, it works.

Can you reproduce the problem using my cmds?

[davidmurdoch]

I cannot reproduce. I'm running:

$ ganache-cli --version
ganache v7.5.0 (@ganache/cli: 0.6.0, @ganache/core: 0.6.0)

$ ganache-cli --chain.vmErrorsOnRPCResponse true --server.port 19998 --fork.url https://polygon-mainnet.g.alchemy.com/v2/H3E99oH7XymptRueBxkO4OXXazhFb7_c@34581439 --hardfork london --chain.time 2022-10-20T14:51:49 --miner.timestampIncrement 1

and

$ curl -H "Content-Type: application/json" -X POST --data '{"id":1337,"jsonrpc":"2.0","method":"eth_call","params":[{"from":null, "to":"0x82e64f49ed5ec1bc6e43dad4fc8af9bb3a2312ee","data":"0x70a082310000000000000000000000005b8effbdae5941b938c1a79616d185cc3c79d4ff" }]}' http://localhost:19998
{"id":1337,"jsonrpc":"2.0","result":"0x0000000000000000000000000000000000000000000030991a05e26859c1a032"}

I always get the same result, 0x0000000000000000000000000000000000000000000030991a05e26859c1a032, no matter how many times I restart ganache and run the curl command.

Note: you can now use the command ganache, instead of ganache-cli.

[lingmicha]

Something is weird.

I tried the same command on my mac and my ubuntu server. Every time, i got a VM Error:

{"id":1337,"jsonrpc":"2.0","error":{"message":"VM Exception while processing transaction: revert","stack":"CallError: VM Exception while processing transaction: revert\n at Blockchain.simulateTransaction (/home/ubuntu/.nvm/versions/node/v12.22.12/lib/node_modules/ganache/dist/node/1.js:2:81107)\n at processTicksAndRejections (internal/process/task_queues.js:97:5)","code":-32000,"name":"CallError","data":"0x4e487b710000000000000000000000000000000000000000000000000000000000000011"}}

But when i start ganache w/o --chain.time 2022-10-20T14:51:49 --miner.timestampIncrement 1, the return is valid.

How could this happen? I tried to debug in many ways, but there's little useful info i can extract from ganache.

The ganache version:
On Untutu: ganache v7.4.4 (@ganache/cli: 0.5.4, @ganache/core: 0.5.4)
On Mac: ganache v7.5.0 (@ganache/cli: 0.6.0, @ganache/core: 0.6.0)

Pls help investigate. Thanks,
Michael

[lingmicha]

@davidmurdoch Hi david, i've tried the cmd on various machines. ALL failed with the same response.

Tried with different ganache version + different node versions.

I wonder why yours works. :)

[davidmurdoch]

Can you try quoting the the time? Maybe whatever shell you are using is attempting to parse it?

[tenthirtyone]

@lingmicha I think @davidmurdoch and I figured this one out.

In our testing, we were both consistently receiving different results. Then we realized, geographically we are in different locations. When we double checked our timestamps, they were the same. However, because we reside in different geographic locations, those timestamps meant different things to our system time. When we passed in a timezone with the date param, our results were consistently the same.

Timezones

Try to pass the following command to start ganache:

$ ganache-cli --chain.vmErrorsOnRPCResponse true --server.port 19998 --fork.url https://polygon-mainnet.g.alchemy.com/v2/H3E99oH7XymptRueBxkO4OXXazhFb7_c@34581439 --hardfork london --chain.time 2022-10-20T14:51:49Z --miner.timestampIncrement 1 --fork.disableCache -d

There is one small difference in this command from your previous commands:

--chain.time 2022-10-20T14:51:49Z

The Z in timezone tells Node to default to UTC time.

Give this a shot and let us know how it goes.

Edit: Oh, I also ran into the error you shared. When I was swapping API keys david pointed out I forgot to include the block number. Starting without the block number after previous testing caused this error.

STR:

ganache-cli --chain.vmErrorsOnRPCResponse true --server.port 19998 --fork.url https://polygon-mainnet.g.alchemy.com/v2/[YOUR KEY HERE]@34581439 --hardfork london --chain.time 2022-10-20T14:51:49Z --miner.timestampIncrement 1

curl -H "Content-Type: application/json" -X POST --data '{"id":1337,"jsonrpc":"2.0","method":"eth_call","params":[{"from":null, "to":"0x82e64f49ed5ec1bc6e43dad4fc8af9bb3a2312ee","data":"0x70a082310000000000000000000000005b8effbdae5941b938c1a79616d185cc3c79d4ff" }]}' http://localhost:19998                                                     

{"id":1337,"jsonrpc":"2.0","result":"0x000000000000000000000000000000000000000000003099077d1b17613b7dcd"}% 

[lingmicha]

This time it works!

Thanks a lot @davidmurdoch @tenthirtyone ！