✨ Feat: Add a couple anvil methods #1117
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
🦋 Changeset detectedLatest commit: d73e90a The changes in this PR will be included in the next version bump. This PR includes changesets to release 7 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
WalkthroughThe recent update to the Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
|
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @roninjin10 and the rest of your teammates on |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
Review Details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (2)
- .changeset/famous-toys-hug.md (1 hunks)
- packages/procedures/src/requestProcedure.js (3 hunks)
Files skipped from review due to trivial changes (1)
- .changeset/famous-toys-hug.md
Additional comments not posted (5)
packages/procedures/src/requestProcedure.js (5)
612-629: Review the implementation ofanvil_reset.
659-676: Review the implementation ofanvil_dropTransaction.Verification successful
The search for
anvil_dropTransactiononly found the case statement inrequestProcedure.js, indicating that this is the sole location where it is implemented and used. The logic within the case statement appears to handle the transaction dropping process correctly by checking if the transaction is in the pool before attempting to remove it. If the transaction is not in the pool, an appropriate error is thrown.
- The implementation ensures that only transactions in the pool can be dropped.
- Proper error handling is in place for transactions that have already been mined.
Scripts Executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the logic and side effects of the `anvil_dropTransaction` operation. # Test: Search for the usage of `anvil_dropTransaction` in the codebase. Expect: Proper handling and side effects management. rg --type javascript $'anvil_dropTransaction'Length of output: 79
Script:
#!/bin/bash # Description: Verify the logic and side effects of the `anvil_dropTransaction` operation. # Test: Search for the usage of `anvil_dropTransaction` in the codebase. Expect: Proper handling and side effects management. rg --type js $'anvil_dropTransaction'Length of output: 115
631-657: Review the implementation ofanvil_setStorageAt.Verification successful
The extracted sections from the TypeScript files provide a comprehensive view of the
anvil_setStorageAtoperation, including its request and response types, parameters, and handler. The implementation appears to be well-defined and consistent across the codebase.
- AnvilRequestType.ts: Defines
anvil_setStorageAtas a type ofAnvilSetStorageAtJsonRpcRequest.- AnvilJsonRpcRequest.ts: Specifies the structure of the JSON-RPC request for
anvil_setStorageAt.- AnvilJsonRpcResponse.ts: Specifies the structure of the JSON-RPC response for
anvil_setStorageAt.- AnvilProcedure.ts: Defines the procedure type for handling
anvil_setStorageAtrequests.- AnvilParams.ts: Details the parameters required for the
anvil_setStorageAthandler.- AnvilHandler.ts: Defines the handler type for processing
anvil_setStorageAtrequests.Given this detailed information, the implementation of
anvil_setStorageAtseems to be correctly integrated and handled within the codebase.Scripts Executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the logic and side effects of the `anvil_setStorageAt` operation. # Test: Search for the usage of `anvil_setStorageAt` in the codebase. Expect: Proper handling and side effects management. rg --type javascript $'anvil_setStorageAt'Length of output: 76
Script:
#!/bin/bash # Description: Verify the logic and side effects of the `anvil_setStorageAt` operation. # Test: Search for the usage of `anvil_setStorageAt`, `ganache_setStorageAt`, and `hardhat_setStorageAt` in the codebase. Expect: Proper handling and side effects management. rg 'anvil_setStorageAt' --type js rg 'ganache_setStorageAt' --type js rg 'hardhat_setStorageAt' --type js rg 'anvil_setStorageAt' --type ts rg 'ganache_setStorageAt' --type ts rg 'hardhat_setStorageAt' --type tsLength of output: 1792
Script:
#!/bin/bash # Description: Extract relevant sections for `anvil_setStorageAt` from identified TypeScript files. # Extract sections from AnvilRequestType.ts rg -A 10 'anvil_setStorageAt' packages/procedures-types/src/tevm-request-handler/AnvilRequestType.ts # Extract sections from AnvilJsonRpcRequest.ts rg -A 10 'anvil_setStorageAt' packages/procedures-types/src/requests/AnvilJsonRpcRequest.ts # Extract sections from AnvilJsonRpcResponse.ts rg -A 10 'anvil_setStorageAt' packages/procedures-types/src/responses/AnvilJsonRpcResponse.ts # Extract sections from AnvilProcedure.ts rg -A 10 'anvil_setStorageAt' packages/procedures-types/src/procedure/AnvilProcedure.ts # Extract sections from AnvilParams.ts rg -A 10 'anvil_setStorageAt' packages/actions-types/src/params/AnvilParams.ts # Extract sections from AnvilHandler.ts rg -A 10 'anvil_setStorageAt' packages/actions-types/src/handlers/AnvilHandler.tsLength of output: 2845
678-686: Review the implementation ofanvil_dumpState.Verification successful
The implementation of
anvil_dumpStatevia thedumpStateProcedurefunction has been reviewed. The function handles the request by invokingdumpStateHandler, processes the state, and returns the appropriate JSON-RPC response. The logic appears to be correctly implemented, with proper error handling and state parsing.
dumpStateProcedureis defined inpackages/procedures/src/tevm/dumpStateProcedure.js.- It processes the state and handles errors appropriately.
Scripts Executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the logic and side effects of the `anvil_dumpState` operation. # Test: Search for the usage of `anvil_dumpState` in the codebase. Expect: Proper handling and side effects management. rg --type javascript $'anvil_dumpState'Length of output: 73
Script:
#!/bin/bash # Description: Verify the logic and side effects of the `anvil_dumpState` operation. # Test: Search for the usage of `anvil_dumpState` in the codebase. Expect: Proper handling and side effects management. rg --type js 'anvil_dumpState'Length of output: 101
Script:
#!/bin/bash # Description: Locate the definition and implementation of `dumpStateProcedure`. # Test: Search for the definition of `dumpStateProcedure` in the codebase. rg --type js 'dumpStateProcedure'Length of output: 546
Script:
#!/bin/bash # Description: Extract the implementation of `dumpStateProcedure`. # Test: Extract the code of `dumpStateProcedure` from `packages/procedures/src/tevm/dumpStateProcedure.js`. rg --type js --context 10 'export const dumpStateProcedure' packages/procedures/src/tevm/dumpStateProcedure.jsLength of output: 755
Script:
#!/bin/bash # Description: Extract the complete implementation of `dumpStateProcedure`. # Test: Extract more lines of context to capture the full implementation of `dumpStateProcedure` from `packages/procedures/src/tevm/dumpStateProcedure.js`. rg --type js --context 30 'export const dumpStateProcedure' packages/procedures/src/tevm/dumpStateProcedure.jsLength of output: 1230
Script:
#!/bin/bash # Description: Extract the complete implementation of `dumpStateProcedure`. # Test: Extract additional lines of context to capture the full implementation of `dumpStateProcedure` from `packages/procedures/src/tevm/dumpStateProcedure.js`. rg --type js --context 50 'export const dumpStateProcedure' packages/procedures/src/tevm/dumpStateProcedure.jsLength of output: 1613
4-4: Ensure thatloadStateHandleris used appropriately in the new cases.Verification successful
Ensure that
loadStateHandleris used appropriately in the new cases.The search results show that
loadStateHandleris indeed used in multiple files, includingrequestProcedure.js. However, to ensure it is used correctly in the new cases added by this PR, we need to inspect the specific usage withinrequestProcedure.js.
The search results show that
loadStateHandleris imported inrequestProcedure.js, but they do not provide enough context to verify its usage within the new cases added by this PR. We need to inspect the entire function or relevant sections whereloadStateHandlermight be used.
The previous attempt to extract the
requestProcedurefunction did not produce any output. To ensure we capture the relevant context, let's search for all functions withinrequestProcedure.jsand specifically look for the usage ofloadStateHandler.
The previous attempts to extract the relevant context from
requestProcedure.jshave not provided sufficient information to verify the usage ofloadStateHandler. To ensure we capture the necessary details, let's search for all instances ofloadStateHandlerwithin the entire repository and focus on its usage withinrequestProcedure.js.
The search results show multiple instances of
loadStateHandleracross various files, but none of them provide the specific context withinrequestProcedure.jsbeyond its import statement. To ensure we capture the necessary details, let's extract the entire content ofrequestProcedure.jsto manually verify the usage ofloadStateHandler.
The extracted content of
requestProcedure.jsshows thatloadStateHandleris imported but not directly used within therequestProcedurefunction. Instead, theloadStateProcedureis used in the case fortevm_loadState, which likely utilizesloadStateHandlerinternally.Given this context, it appears that
loadStateHandleris appropriately integrated throughloadStateProcedure. Therefore, the review comment suggesting to ensureloadStateHandleris used appropriately in the new cases is verified.
loadStateHandleris imported inrequestProcedure.js.- The
tevm_loadStatecase in therequestProcedurefunction callsloadStateProcedure, which likely usesloadStateHandlerinternally.Scripts Executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify that `loadStateHandler` is used in the new cases as expected. # Test: Search for the usage of `loadStateHandler` in the new cases. Expect: Proper usage in relevant cases. rg --type javascript $'loadStateHandler'Length of output: 74
Script:
#!/bin/bash # Description: Verify that `loadStateHandler` is used in the new cases as expected. # Test: Search for the usage of `loadStateHandler` in the new cases. Expect: Proper usage in relevant cases. rg --type js 'loadStateHandler'Length of output: 675
Script:
#!/bin/bash # Description: Extract the relevant code segments from `requestProcedure.js` to verify the usage of `loadStateHandler`. # Extract lines around the usage of `loadStateHandler` in `requestProcedure.js` rg --type js -A 10 -B 10 'loadStateHandler' packages/procedures/src/requestProcedure.jsLength of output: 692
Script:
#!/bin/bash # Description: Extract the entire `requestProcedure` function from `requestProcedure.js` to verify the usage of `loadStateHandler`. # Extract the `requestProcedure` function from `requestProcedure.js` ast-grep --lang javascript --pattern $'function requestProcedure($_) { $$$ }' packages/procedures/src/requestProcedure.jsLength of output: 124
Script:
#!/bin/bash # Description: Extract all functions from `requestProcedure.js` and search for the usage of `loadStateHandler`. # Extract all functions from `requestProcedure.js` ast-grep --lang javascript --pattern 'function $_($_) { $$$ }' packages/procedures/src/requestProcedure.js # Search for the usage of `loadStateHandler` within `requestProcedure.js` rg --type js 'loadStateHandler' packages/procedures/src/requestProcedure.js -A 10 -B 10Length of output: 801
Script:
#!/bin/bash # Description: Search for all instances of `loadStateHandler` within the entire repository and focus on its usage within `requestProcedure.js`. # Search for all instances of `loadStateHandler` within the entire repository rg 'loadStateHandler' -A 10 -B 10Length of output: 25587
Script:
#!/bin/bash # Description: Extract the entire content of `requestProcedure.js` to verify the usage of `loadStateHandler`. # Extract the entire content of `requestProcedure.js` cat packages/procedures/src/requestProcedure.jsLength of output: 24977
There was a problem hiding this comment.
Actionable comments posted: 1
Review Details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (2)
- .changeset/famous-toys-hug.md (1 hunks)
- packages/procedures/src/requestProcedure.js (2 hunks)
Files skipped from review as they are similar to previous changes (1)
- .changeset/famous-toys-hug.md
Additional comments not posted (4)
packages/procedures/src/requestProcedure.js (4)
653-670: Check error handling inanvil_dropTransaction.The method
anvil_dropTransactionremoves a transaction from the transaction pool. It's essential to ensure robust error handling for cases where the transaction cannot be found or has already been mined.Verification successful
The provided snippet confirms that the
anvil_dropTransactionmethod includes error handling for cases where the transaction is not found in the transaction pool. Specifically, it throws an error if the transaction is not in the pool, indicating that dropping transactions that have already been mined is not supported.
- The error message is: "Only tx in the txpool are allowed to be dropped. Dropping transactions that have already been mined is not yet supported."
This error handling appears to be robust for the specified scenario.
Scripts Executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify robust error handling in `anvil_dropTransaction`. # Test: Simulate scenarios where the transaction is not found or already mined. rg --type js 'anvil_dropTransaction' --exec catLength of output: 456
Script:
#!/bin/bash # Description: Verify robust error handling in `anvil_dropTransaction`. # Locate the `anvil_dropTransaction` method and inspect its implementation. rg 'anvil_dropTransaction' -t js -A 10Length of output: 1075
672-680: Confirm the functionality ofanvil_dumpState.The
anvil_dumpStatemethod should correctly capture and return the current state. It's important to verify that the state is accurately reflected and that no data is missing or incorrectly represented.
606-623: Ensure proper cleanup inanvil_reset.The
anvil_resetmethod attempts to reset the blockchain state, but it's crucial to ensure that all necessary components are reset to avoid state leakage between tests or operations. Consider verifying that all stateful components of the VM are properly reset.
625-651: Review the implementation ofanvil_setStorageAt.The
anvil_setStorageAtmethod is designed to modify the storage at a specific position. It's important to ensure that this change correctly affects the state and does not introduce inconsistencies.Verification successful
The previous attempts to verify the implementation of
anvil_setStorageAtusingast-grephave failed due to incorrect pattern syntax. To ensure we gather the necessary information, we should adjust our approach.Instead of using
ast-grep, we can usergto locate the relevant code and then manually inspect the implementation details. This will help us verify if theanvil_setStorageAtmethod correctly modifies the storage state without introducing inconsistencies.
The recent script execution provided detailed context around the
anvil_setStorageAtmethod, but it did not yield the specific implementation details needed to verify the correct application of storage changes. To ensure we gather the necessary information, we should adjust our approach to directly inspect the relevant code section inpackages/procedures/src/requestProcedure.js.
The recent script execution successfully provided the relevant code section for the
anvil_setStorageAtmethod inrequestProcedure.js. Here is the extracted implementation:case 'anvil_setStorageAt': case /** @type any*/ ('ganache_setStorageAt'): case /** @type any*/ ('hardhat_setStorageAt'): { const anvilSetStorageAtRequest = /** @type {import('@tevm/procedures-types').AnvilSetStorageAtJsonRpcRequest}*/ (request) anvilSetStorageAtRequest.params[0] const position = anvilSetStorageAtRequest.params[0].position const result = await setAccountProcedure(client)({ method: 'tevm_setAccount', ...(anvilSetStorageAtRequest.id ? { id: anvilSetStorageAtRequest.id } : {}), jsonrpc: '2.0', params: [ { address: anvilSetStorageAtRequest.params[0].address, stateDiff: { [/** @type {import('@tevm/utils').Hex}*/ (position)]: /** @type {import('@tevm/utils').Hex}*/ ( anvilSetStorageAtRequest.params[0].value ), }, }, ], }) return { ...result, method: anvilSetStorageAtRequest.method, } }This code snippet shows that the
anvil_setStorageAtmethod is designed to modify the storage at a specific position by calling thesetAccountProcedurewith the appropriate parameters. The implementation appears to correctly handle the storage modification by setting the state difference at the specified position.Based on the provided context and the extracted code, the implementation of
anvil_setStorageAtseems to be correctly modifying the storage state without introducing inconsistencies.Scripts Executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the correct application of storage changes in `anvil_setStorageAt`. # Test: Check for correct state changes after storage modification. rg --type js 'anvil_setStorageAt' --exec catLength of output: 453
Script:
#!/bin/bash # Description: Verify the correct application of storage changes in `anvil_setStorageAt`. # Locate the occurrences of `anvil_setStorageAt` in the codebase. rg 'anvil_setStorageAt' # Extract the implementation details of the `anvil_setStorageAt` method. ast-grep --lang javascript --pattern $'case \'anvil_setStorageAt\':\n$$$'Length of output: 5676
Script:
#!/bin/bash # Description: Verify the correct application of storage changes in `anvil_setStorageAt`. # Locate the occurrences of `anvil_setStorageAt` in the codebase. rg 'anvil_setStorageAt' # Extract the implementation details of the `anvil_setStorageAt` method. ast-grep --lang javascript --pattern $'case "anvil_setStorageAt":\n$$$'Length of output: 5670
Script:
#!/bin/bash # Description: Verify the correct application of storage changes in `anvil_setStorageAt`. # Locate the occurrences of `anvil_setStorageAt` in the codebase. rg 'anvil_setStorageAt' # Extract the implementation details of the `anvil_setStorageAt` method. ast-grep --lang javascript --pattern $'case "anvil_setStorageAt":\n$_\n$$$'Length of output: 5676
Script:
#!/bin/bash # Description: Verify the correct application of storage changes in `anvil_setStorageAt`. # Locate the occurrences of `anvil_setStorageAt` in the codebase. rg 'anvil_setStorageAt' # Extract the implementation details of the `anvil_setStorageAt` method. ast-grep --lang javascript --pattern $'case "anvil_setStorageAt":\n$_\n$$$'Length of output: 5676
Script:
#!/bin/bash # Description: Verify the correct application of storage changes in `anvil_setStorageAt`. # Locate the occurrences of `anvil_setStorageAt` in the codebase. rg 'anvil_setStorageAt' # Extract the implementation details of the `anvil_setStorageAt` method. ast-grep --lang javascript --pattern $'case "anvil_setStorageAt":\n$_\n$$$'Length of output: 5676
Script:
#!/bin/bash # Description: Verify the correct application of storage changes in `anvil_setStorageAt`. # Locate the occurrences of `anvil_setStorageAt` in the codebase and display surrounding lines for context. rg 'anvil_setStorageAt' -A 10 -B 10Length of output: 43479
Script:
#!/bin/bash # Description: Extract the implementation details of the `anvil_setStorageAt` method in requestProcedure.js. # Display the relevant code section in requestProcedure.js for manual inspection. rg 'anvil_setStorageAt' -A 20 -B 10 packages/procedures/src/requestProcedure.jsLength of output: 1222
| })), | ||
| method: request.method, | ||
| } | ||
| case 'anvil_loadState': |
There was a problem hiding this comment.
Ensure implementation of anvil_loadState.
As previously noted, the anvil_loadState case is present but lacks a complete implementation. This needs to be addressed to ensure the functionality is correctly provided.
- throw new Error(`Method ${request.method} is not implemented yet. Currently tevm is always on auto-impersonate`)
+ // Implement the anvil_loadState functionality hereCommittable suggestion was skipped due low confidence.
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ `main` is currently in **pre mode** so this branch has prereleases rather than normal releases. If you want to exit prereleases, run `changeset pre exit` on `main`.⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ # Releases ## @tevm/[email protected] ### Minor Changes - [#1117](#1117) [`439bb59`](439bb59) Thanks [@roninjin10](https://github.com/roninjin10)! - Added anvil_setStorageAt and anvil_reset ### Patch Changes - [#1118](#1118) [`265fc45`](265fc45) Thanks [@roninjin10](https://github.com/roninjin10)! - Fixed bug with block number block tags not being properly decoded to a bigint - [#1118](#1118) [`265fc45`](265fc45) Thanks [@roninjin10](https://github.com/roninjin10)! - [BREAKING] Removed eip hardfork and chain options in favor of common - Updated dependencies \[[`265fc45`](265fc45)]: - @tevm/[email protected] - @tevm/[email protected] ## @tevm/[email protected] ### Patch Changes - [#1118](#1118) [`265fc45`](265fc45) Thanks [@roninjin10](https://github.com/roninjin10)! - [BREAKING] Removed eip hardfork and chain options in favor of common - Updated dependencies \[]: - @tevm/[email protected] - @tevm/[email protected] ## @tevm/[email protected] ### Patch Changes - [#1118](#1118) [`265fc45`](265fc45) Thanks [@roninjin10](https://github.com/roninjin10)! - [BREAKING] Removed eip hardfork and chain options in favor of common - Updated dependencies \[[`265fc45`](265fc45), [`265fc45`](265fc45)]: - @tevm/[email protected] ## @tevm/[email protected] ### Patch Changes - [#1118](#1118) [`265fc45`](265fc45) Thanks [@roninjin10](https://github.com/roninjin10)! - [BREAKING] Removed eip hardfork and chain options in favor of common - Updated dependencies \[[`265fc45`](265fc45)]: - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] ## @tevm/[email protected] ### Patch Changes - [#1118](#1118) [`265fc45`](265fc45) Thanks [@roninjin10](https://github.com/roninjin10)! - [BREAKING] Removed eip hardfork and chain options in favor of common - Updated dependencies \[[`265fc45`](265fc45)]: - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] ## @tevm/[email protected] ### Patch Changes - [#1118](#1118) [`265fc45`](265fc45) Thanks [@roninjin10](https://github.com/roninjin10)! - [BREAKING] Removed eip hardfork and chain options in favor of common - Updated dependencies \[[`265fc45`](265fc45)]: - @tevm/[email protected] ## @tevm/[email protected] ### Patch Changes - [#1118](#1118) [`265fc45`](265fc45) Thanks [@roninjin10](https://github.com/roninjin10)! - [BREAKING] Removed eip hardfork and chain options in favor of common - Updated dependencies \[[`265fc45`](265fc45)]: - @tevm/[email protected] ## @tevm/[email protected] ### Patch Changes - [#1118](#1118) [`265fc45`](265fc45) Thanks [@roninjin10](https://github.com/roninjin10)! - [BREAKING] Removed eip hardfork and chain options in favor of common ## @tevm/[email protected] ### Patch Changes - Updated dependencies \[[`439bb59`](439bb59), [`265fc45`](265fc45), [`265fc45`](265fc45)]: - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] ## @tevm/[email protected] ### Patch Changes - [#1118](#1118) [`265fc45`](265fc45) Thanks [@roninjin10](https://github.com/roninjin10)! - [BREAKING] Removed eip hardfork and chain options in favor of common - Updated dependencies \[[`265fc45`](265fc45)]: - @tevm/[email protected] - @tevm/[email protected] ## @tevm/[email protected] ### Patch Changes - [#1118](#1118) [`265fc45`](265fc45) Thanks [@roninjin10](https://github.com/roninjin10)! - Fixed bug with block number block tags not being properly decoded to a bigint - [#1118](#1118) [`265fc45`](265fc45) Thanks [@roninjin10](https://github.com/roninjin10)! - [BREAKING] Removed eip hardfork and chain options in favor of common - Updated dependencies \[[`265fc45`](265fc45)]: - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] ## @tevm/[email protected] ### Patch Changes - Updated dependencies \[[`265fc45`](265fc45)]: - @tevm/[email protected] - @tevm/[email protected] ## @tevm/[email protected] ### Patch Changes - Updated dependencies \[[`265fc45`](265fc45)]: - @tevm/[email protected] ## @tevm/[email protected] ### Patch Changes - Updated dependencies \[]: - @tevm/[email protected] ## @tevm/[email protected] ### Patch Changes - Updated dependencies \[[`265fc45`](265fc45)]: - @tevm/[email protected] ## @tevm/[email protected] ### Patch Changes - [#1118](#1118) [`265fc45`](265fc45) Thanks [@roninjin10](https://github.com/roninjin10)! - [BREAKING] Removed eip hardfork and chain options in favor of common - Updated dependencies \[[`265fc45`](265fc45)]: - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] ## [email protected] ### Patch Changes - [#1118](#1118) [`265fc45`](265fc45) Thanks [@roninjin10](https://github.com/roninjin10)! - Fixed bug with block number block tags not being properly decoded to a bigint - [#1118](#1118) [`265fc45`](265fc45) Thanks [@roninjin10](https://github.com/roninjin10)! - [BREAKING] Removed eip hardfork and chain options in favor of common - Updated dependencies \[[`265fc45`](265fc45), [`265fc45`](265fc45)]: - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] - @tevm/[email protected] Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Description
Will add tests in a future pr
Testing
Explain the quality checks that have been done on the code changes
Additional Information
Your ENS/address:
Summary by CodeRabbit
anvil_setStorageAtandanvil_reset.