-
Notifications
You must be signed in to change notification settings - Fork 678
eth_getStorageAt with block number parameter doesn't return correct result when using fork feature #573
Comments
Hey @davidmurdoch, I noticed that there is a TODO that is linked to this issue. Would you be open to accepting a PR that addresses this problem? |
Hey @seesemichaelj is there anything we can do to help you with resolving this issue? We're open to submitting the PR ourselves if you don't have the capacity to tackle this now 😄 |
Hey @BogdanHabic! I haven't yet scoped out the issue here, but my next priority is to work various forking issues (including this one, #526, #533, #571, and #579). I would definitely appreciate any help you want to provide if you have time to work it now! I can start work on other issues before getting to this one if you want to throw together a PR. Even if you want to describe a solution without doing the implementation, that would also be helpful |
@BogdanHabic I'm also happy to collaborate somehow. I know our timezones are not very forgiving for anything realtime, but feel free to use this issue as a means to bounce ideas off me and @davidmurdoch |
@seesemichaelj great to hear that you're tackling forking issues! @nebojsa94 can help out on this issue from our side. He'll submit a description of the solution first and if we get a 👍 from you, we'll submit a PR with the implementation as well. |
Sounds great! |
Thank you for helping us resolve this issue! There are 2 problems that we need to address here:
@seesemichaelj @davidmurdoch Do you think this approach is valid. I can submit a PR once you approve. P.S. I think this will also fix some issues with |
Hey @nebojsa94, while I was assessing the validity of your solution, I was trying to find a more elegant solution by hacking away. However, I ended up on your proposed solution anyway and opened a PR since it was done. I didn't intend to steal your thunder and hope you didn't spend any time with implementation! Nevertheless, I really appreciate the proposal you made as it saved me discovery time! |
This was just officially released in [email protected] / [email protected] |
JSON RPC method eth_getStorageAt always returns the latest state when using fork feature regardless of the third parameter
Expected Behavior
When changing the storage value in contract c at key k from v1 to v2 in block b,
eth_getStorageAt(c, k, b-1)
should return v1.Current Behavior
eth_getStorageAt(c, k, b-1)
returns v2 for any b.For storage values that didn't change after fork,
eth_getStorageAt
works as expectedSteps to Reproduce (for bugs)
ganache-cli -f mainnet_node --networkId 1
truffle migrate
eth_getStorageAt("[migration_contract]", "0x1", "0x0")
Your Environment
The text was updated successfully, but these errors were encountered: