You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering it makes sense to keep this crate purely for typecasting between alloy and ethers, and pull out the functionality under LedgerClient and ExecutableTransaction.execute into another crate. Maybe keep both crates in this repo as the abstraction layer for working with alloy / ethers to simplify the transition between them?
just thinking of separating concerns: keep one crate purely for the ethers <-> alloy typecasting, and make another for the higher-level abstractions for using ethers/alloy in real-world settings (i.e setting up a ledger client, executing a transaction with feedback logs, etc.)
Does make sense actually. The reason we put it here is because it's an alloy interface to what is ethers under the hood. Once it becomes all alloy we'll still want it separated but it won't have an ethers component anymore. Unless @thedavidmeister disagrees I think go ahead and separate out.
I'm wondering it makes sense to keep this crate purely for typecasting between alloy and ethers, and pull out the functionality under
LedgerClient
andExecutableTransaction.execute
into another crate. Maybe keep both crates in this repo as the abstraction layer for working with alloy / ethers to simplify the transition between them?@hardyjosh @thedavidmeister
The text was updated successfully, but these errors were encountered: