-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Tracking: Ethers -> Alloy transition #4715
Comments
This issue is stale because it has been open for 21 days with no activity. |
This issue was closed because it has been inactive for 7 days since being marked as stale. |
Do we have all the necessary alloy network implementations now? I think so? cc @Evalir @DaniPopes |
I've looked at the tests a few days ago. They use an extension to SignerMiddleware with some RPC calls I believe we don't have yet, and the geth wrapper GethInstance to spawn a geth process:
This would also unblock #6006. |
Main transition
Alloy transition
Ethers removal
Note that only
ethers-core
is used in Reth code, while other crates are used only for testing which is fine for now.ethers-core
reth-primitives
reth_primitives::abi::decode_revert_reason
#4730reth_primitives::abi::decode_revert_reason
to Alloy #4789mod ethers_compat
etc) inreth-primitives
#4738reth_primitives::utils::serde_helpers
re-export #4739H*
type re-exports, and rename toB*
in the codebase #4740reth-rpc
reth-rpc
to Alloy #4742Rest of Ethers, used in tests
Ethers in tests
Further work
Parity removal
rlp
#4796Refactors, upstreaming
reth_primitives::{Chain,NamedChain}
to Alloy #4741reth-rpc-types
to Alloy #4743The text was updated successfully, but these errors were encountered: