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
@arbitrum/sdk v4 introduces significant changes to improve support Orbit chains from Offchain Labs. This guide outlines the breaking changes to know before migrating your existing v3 code to v4.
Major Changes Overview
Terminology change from L1/L2 to parent/child
Network types and functions updated
Updates to AssetBridger and Erc20Bridger classes
Changes to Message classes
Detailed Changes
1. Terminology change from L1/L2 to parent/child
Most instances of "L1" and "L2" have been replaced with "parent" and "child" respectively. This change reflects the more general parent-child relationship between chains in the Arbitrum ecosystem.
In most circumstances, when referring to a parent-child relationship between chains, the terms "parent" and "child" are used.
Though, when referring explicitly to "L1", "L2", or "L3", those specific terms are still used.
2. Network types and functions updated
The L1Network is no longer required to be registered before bridging.
Only Arbitrum networks need to be registered.
Arbitrum networks are defined as Arbitrum One, Arbitrum testnets, and any Orbit chain.
If you need a full list of Arbitrum networks, you can use the new getArbitrumNetworks function.
To list all of the children of a network, use the new getChildrenForNetwork function.