[SDK] Clarification on Use Cases and Necessity of 'zksync-ethers' over 'ethers'

[gauravl-tevaeralabs]

Environment

Mainnet

Acknowledgement

• I understand that issues are expected with the Go SDK as they are being updated.

Issue Description

We are transitioning to zksync-ethers from zksync-web3, and we discovered the following documentation in the NPM package for zksync-ethers:

"While most of the existing SDKs should work out of the box, deploying smart contracts or utilizing unique zkSync features, like account abstraction, requires providing additional fields compared to those that Ethereum transactions have by default."

Besides deploying contracts, do we have documentation outlining all the scenarios where using zksync-ethers is necessary? Account Abstraction is mentioned, suggesting that zksync-ethers might be required for paymaster functionality. Are there any other common use cases where zksync-ethers is essential, and things might not function correctly with ethers?

We're in the process of developing an abstract SDK for our contracts that will function across any chain, primarily focusing on our layer-zero bridging functionality. As such, we plan to use ethers for most cases and reserve zksync-ethers for essential functionalities.

Expected Behavior

NA

Code Example

NA

Repo Link (Optional)

No response

[dutterbutter]

@gauravl-tevaeralabs I believe the specific functionality is captured here: https://docs.zksync.io/build/sdks/js/zksync-ethers/features.html

@danijelTxFusion is there anything else not mentioned in that page that is relevant?

[gauravl-tevaeralabs]

Hi @dutterbutter, this is exactly what I was looking for. Thank you so much!

[danijelTxFusion]

is there anything else not mentioned in that page that is relevant?
The page contains everything that ethers cannot do in the zkSync Era and zksync-ethers does.

[emresen30]

Thanks a lot <<<