📢 Upcoming Changes to ZKsync RPC API

[uF4No]

We’re making changes to the ZKsync node API to simplify and streamline developer experience. Several RPC methods are being removed or migrated due to deprecation, protocol evolution, or simplification of the API.

Please read carefully and plan necessary updates to your applications or integrations.

---

❌ Deprecated RPC Methods

The following methods are considered deprecated and will be removed from the node API:

• zks_getConfirmedTokens: Returns a list of ERC20 tokens bridged to L2 via the canonical bridge.
• zks_getAllAccountBalances: Returns confirmed token balances for an account.
• zks_getL2ToL1MsgProof: Used in protocol versions <v24 for L2 → L1 messaging.
• zks_getProtocolVersion: Returns protocol version, verification keys, and system contracts info.

Additionally, one method will be migrated:

• zks_sendRawTransactionWithDetailedOutput: Will now live under the unstable_ namespace: unstable_sendRawTransactionWithDetailedOutput.*

---

✅ Recommended Alternatives

Here’s how you can update your applications:

• zks_getConfirmedTokens → Use third-party APIs such as Coingecko or TokenLists.org.
• zks_getAllAccountBalances → Use the addresstokenbalance method from the block explorer API or token APIs from providers like Alchemy or QuickNode.
• zks_getL2ToL1MsgProof → Use the newer method: zks_getL2ToL1LogProof (available since protocol v24).
• zks_getProtocolVersion → Use:
  • eth_protocolVersion for basic version info.
  • en_getProtocolVersionInfo for full protocol metadata (new method).
• zks_sendRawTransactionWithDetailedOutput → Use unstable_sendRawTransactionWithDetailedOutput.

---

🛠 SDK Impact

These deprecated RPC methods are used in the zksync-ethers and other SDKs. The following methods will be flagged as deprecated and removed in future SDK versions:

• Provider::getConfirmedTokens
• SmartAccount::getAllBalances
• Provider::getAllAccountBalances
• AdapterL2::getAllBalances
• Provider::getProtocolVersion
• Provider::sendRawTransactionWithDetailedOutput

---

🔄 Timeline

We’ve analyzed production usage and identified that these methods are either deprecated or very rarely used. As such, we will begin the removal process shortly.

Please start migrating your applications to the recommended alternatives as soon as possible to avoid disruptions.

If you have questions or need migration support, feel free to reach out via GitHub discussions.

[bxpana]

Additional Deprecations and New Methods