Merge branch 'master' into arbos61-notice

Author: anegg0

docs/arbitrum-essentials/bridging/configure-token-gateway/custom.mdx

@@ -768,7 +768,7 @@ In this case, when using this function, a single action occurs:
 
 1. Call the function `setGateway` of `L1GatewayRouter`. This call updates the `l1TokenToGateway` internal mapping and sends a retryable ticket to the counterpart `L2GatewayRouter` contract on the child chain to set its mapping to the new values.
 
-To simplify the process, we’ll use Arbitrum’s SDK and call the method [`registerCustomToken`](https://github.com/OffchainLabs/arbitrum-sdk/blob/main/packages/sdk/src/lib/assetBridger/erc20Bridger.ts) of the [`AdminErc20Bridger`](https://github.com/OffchainLabs/arbitrum-sdk/blob/main/packages/sdk/src/lib/assetBridger/erc20Bridger.ts) class, which will call the `registerTokenOnL2` method of the token passed by parameter.
+To simplify the process, we'll use Arbitrum's SDK and call the method [`registerCustomToken`](https://github.com/OffchainLabs/arbitrum-sdk/blob/main/packages/sdk/src/lib/assetBridger/erc20Bridger.ts) of the [`AdminErc20Bridger`](https://github.com/OffchainLabs/arbitrum-sdk/blob/main/packages/sdk/src/lib/assetBridger/erc20Bridger.ts) class, which will call the `registerTokenOnL2` method of the token passed by parameter.
 
 ```tsx
 /**

docs/arbitrum-essentials/bridging/configure-token-gateway/generic-custom.mdx

@@ -306,7 +306,7 @@ When using this function, you will take two actions:
 1. Call the function `registerTokenToL2` of `L1CustomGateway`. This call will change the `l1ToL2Token` internal mapping it holds and send a retryable ticket to the counterpart `L2CustomGateway` contract on the child chain, setting its mapping to the new values as well.
 2. Call the function `setGateway` of `L1GatewayRouter`. This call will update the `l1TokenToGateway` internal mapping it holds and send a retryable ticket to the counterpart `L2GatewayRouter` contract on the child chain to set its mapping to the new values.
 
-To simplify the process, we’ll use Arbitrum’s SDK. We’ll call the [`registerCustomToken`](https://github.com/OffchainLabs/arbitrum-sdk/blob/main/packages/sdk/src/lib/assetBridger/erc20Bridger.ts) method of the [`AdminErc20Bridger`](https://github.com/OffchainLabs/arbitrum-sdk/blob/main/packages/sdk/src/lib/assetBridger/erc20Bridger.ts) class, which will call the `registerTokenOnL2` method on the token passed as a parameter.
+To simplify the process, we'll use Arbitrum's SDK. We'll call the [`registerCustomToken`](https://github.com/OffchainLabs/arbitrum-sdk/blob/main/packages/sdk/src/lib/assetBridger/erc20Bridger.ts) method of the [`AdminErc20Bridger`](https://github.com/OffchainLabs/arbitrum-sdk/blob/main/packages/sdk/src/lib/assetBridger/erc20Bridger.ts) class, which will call the `registerTokenOnL2` method on the token passed as a parameter.
 
 ```typescript
 /**

docs/arbitrum-essentials/bridging/configure-token-gateway/standard.mdx

@@ -201,5 +201,5 @@ The gateway controls the automatically deployed child chain token—you can't mo
 
 - [Token bridge conceptual overview](/how-arbitrum-works/deep-dives/token-bridging.mdx)
 - [Standard **ERC-20** bridging details](/how-arbitrum-works/deep-dives/token-bridging.mdx#default-standard-bridging)
-- [Arbitrum SDK documentation](/sdk)
+- [Arbitrum SDK](https://github.com/OffchainLabs/arbitrum-sdk)
 - [Contract addresses](/arbitrum-essentials/reference/contract-addresses.mdx)

docs/arbitrum-essentials/bridging/cross-chain-messaging.mdx

@@ -9,8 +9,12 @@ sme: greatsoshiant
 displayed_sidebar: arbitrumEssentialsSidebar
 ---
 
+import ArbitrumSdkInfo from '@site/docs/partials/_arbitrum-sdk-partial.mdx';
+
 The <a data-quicklook-from="arbitrum">Arbitrum</a> protocol and related tooling make it easy for developers to build cross-chain applications; i.e., applications that involve sending messages from Ethereum to an <a data-quicklook-from="arbitrum-chain">Arbitrum chain</a>, and/or from an Arbitrum chain to Ethereum.
 
+<ArbitrumSdkInfo />
+
 ## Ethereum-to-Arbitrum messaging
 
 Creating an arbitrary parent-to-child chain contract call occurs via the Inbox's `createRetryableTicket` method. Upon publishing the <a data-quicklook-from="parent-chain">parent chain</a> <a data-quicklook-from="transaction">transaction</a>, the <a data-quicklook-from="child-chain">child chain</a> side will typically be included within minutes. Commonly, the child chain execution will automatically succeed, but if it reverts, it can be re-executed via a call to the `redeem` method of the [`ArbRetryableTx`](/arbitrum-essentials/precompiles/reference.mdx#arbretryabletx) <a data-quicklook-from="precompile">precompile</a>.
@@ -210,6 +214,6 @@ if (childTxReceipt.status === ParentToChildMessageStatus.REDEEMED) {
 
 - [Greeter tutorial source code](https://github.com/OffchainLabs/arbitrum-tutorials/tree/master/packages/greeter)
 - [Outbox execution source code](https://github.com/OffchainLabs/arbitrum-tutorials/tree/master/packages/outbox-execute)
-- [Arbitrum SDK documentation](/sdk)
+- [Arbitrum SDK](https://github.com/OffchainLabs/arbitrum-sdk)
 - [Retryable ticket lifecycle](/how-arbitrum-works/deep-dives/l1-to-l2-messaging.mdx)
 - [Child to parent messaging protocol](/how-arbitrum-works/deep-dives/l2-to-l1-messaging.mdx)

docs/arbitrum-essentials/bridging/custom-gas-token-chains.mdx

@@ -36,7 +36,7 @@ You should use `EthBridger` when bridging the native token between the parent ch
 - You should use `Erc20Bridger` when bridging an **ERC-20** token between the parent chain and the Arbitrum chain.
 - These APIs are only needed for [`custom gas token`](/launch-arbitrum-chain/chain-config/costs/custom-gas-token-rollup.mdx) <a data-quicklook-from="arbitrum-chains">Arbitrum Chains</a>. For **ETH**-powered rollup and AnyTrust Arbitrum chains, you don't need to use them.
 - When native tokens are transferred to the custom gas token Arbitrum chain, they function equivalently to **ETH** on EVM chains. This means these tokens will exhibit behavior identical to that of **ETH**, the native currency on EVM chains. This similarity in functionality is a key feature to consider in <a data-quicklook-from="transaction">transactions</a> and operations within the Arbitrum chain.
-- Everything else is under the hood, and the custom gas token code paths will be executed just if the `L2Network` object config has a `nativeToken` field.
+- Everything else is handled under the hood, and the custom gas token code paths will be executed only if the `ArbitrumNetwork` object config has a `nativeToken` field.
 
 :::
 

docs/arbitrum-essentials/bridging/deposit/eth-and-messages.mdx

@@ -97,7 +97,7 @@ function sendL2MessageFromOrigin(
 ) external returns (uint256)
 ```
 
-**Example use case**: [Withdraw Ether tutorial](https://github.com/OffchainLabs/arbitrum-tutorials/blob/a1c3f64a5abdd0f0e728cb94d4ecc2700eab7579/packages/delayedInbox-l2msg/scripts/withdrawFunds.js#L61-L65)
+**Example use case**: [Withdraw Ether tutorial](https://github.com/OffchainLabs/arbitrum-tutorials/blob/master/packages/delayedInbox-l2msg/scripts/withdrawFunds.js#L61-L65)
 
 ### Sending unsigned messages
 
@@ -206,11 +206,11 @@ function createRetryableTicket(
 ### Example using the Arbitrum SDK
 
 ```javascript
-import { L1ToL2MessageGasEstimator } from '@arbitrum/sdk';
+import { ParentToChildMessageGasEstimator } from '@arbitrum/sdk';
 
 // Estimate gas for the retryable ticket
-const l1ToL2MessageGasEstimator = new L1ToL2MessageGasEstimator(l2Provider);
-const retryableGasParams = await l1ToL2MessageGasEstimator.estimateAll(
+const parentToChildMessageGasEstimator = new ParentToChildMessageGasEstimator(childProvider);
+const retryableGasParams = await parentToChildMessageGasEstimator.estimateAll(
   {
     from: senderAddress,
     to: destinationAddress,
@@ -249,6 +249,48 @@ Retryable tickets can auto-redeem if sufficient gas is provided. If the initial
 ArbRetryableTx(address(110)).redeem(ticketId);
 ```
 
+## Deposit ETH using the Arbitrum SDK
+
+The [Arbitrum SDK](https://github.com/OffchainLabs/arbitrum-sdk) provides an `EthBridger` class that simplifies depositing `ETH` from the parent chain to the child chain:
+
+```ts
+import { ethers } from 'ethers';
+import { getArbitrumNetwork, EthBridger } from '@arbitrum/sdk';
+
+// Get the Arbitrum network and create an EthBridger
+const childNetwork = await getArbitrumNetwork(childProvider);
+const ethBridger = new EthBridger(childNetwork);
+
+// Deposit ETH from parent chain to child chain
+const depositTx = await ethBridger.deposit({
+  amount: ethers.utils.parseEther('0.1'),
+  parentSigner,
+});
+const depositReceipt = await depositTx.wait();
+
+// Wait for the deposit to be processed on the child chain
+const childResult = await depositReceipt.waitForChildTransactionReceipt(childProvider);
+console.log('Deposit complete:', childResult.complete);
+```
+
+### Deposit to a different address
+
+To deposit `ETH` to a recipient address that differs from the sender, use `depositTo`:
+
+```ts
+const depositTx = await ethBridger.depositTo({
+  amount: ethers.utils.parseEther('0.1'),
+  parentSigner,
+  childProvider,
+  destinationAddress: '0x...recipient',
+});
+```
+
+### Tutorials
+
+- [eth-deposit tutorial](https://github.com/OffchainLabs/arbitrum-tutorials/tree/master/packages/eth-deposit) — full walkthrough of depositing `ETH` using the SDK
+- [eth-deposit-to-different-address tutorial](https://github.com/OffchainLabs/arbitrum-tutorials/tree/master/packages/eth-deposit-to-different-address) — depositing `ETH` to a different recipient
+
 ## Next steps
 
 - For protocol-level details, see [Parent to child chain messaging](/how-arbitrum-works/deep-dives/l1-to-l2-messaging.mdx)

docs/arbitrum-essentials/bridging/deposit/tokens.mdx

@@ -220,7 +220,7 @@ Make sure you approved the correct gateway contract (not the router). Use `getGa
 
 ## Resources
 
-- [Arbitrum SDK documentation](/sdk)
+- [Arbitrum SDK](https://github.com/OffchainLabs/arbitrum-sdk)
 - [ETH deposit source code](https://github.com/OffchainLabs/arbitrum-tutorials/tree/master/packages/eth-deposit)
 - [ERC-20 deposit source code](https://github.com/OffchainLabs/arbitrum-tutorials/tree/master/packages/token-deposit)
 - [Contract addresses](/arbitrum-essentials/reference/contract-addresses.mdx)

docs/arbitrum-essentials/bridging/l1-l3-teleportation.mdx

@@ -196,6 +196,6 @@ If the L3 chain uses a custom gas token (not `ETH`), you must approve the gas to
 
 ## Resources
 
-- [Arbitrum SDK documentation](/sdk)
+- [Arbitrum SDK](https://github.com/OffchainLabs/arbitrum-sdk)
 - [Token bridge architecture](/how-arbitrum-works/deep-dives/token-bridging.mdx)
 - [Parent-to-child messaging details](/how-arbitrum-works/deep-dives/l1-to-l2-messaging.mdx)

docs/arbitrum-essentials/bridging/overview.mdx

@@ -45,4 +45,4 @@ If you're working with an Arbitrum chain that uses a non-**ETH** gas token, see
 
 - [Cross-chain messaging concepts](/arbitrum-essentials/bridging/cross-chain-messaging.mdx)
 - [Token bridge architecture](/how-arbitrum-works/deep-dives/token-bridging.mdx)
-- [Arbitrum SDK documentation](/sdk)
+- [Arbitrum SDK](https://github.com/OffchainLabs/arbitrum-sdk)

docs/arbitrum-essentials/bridging/withdraw/eth-and-messages.mdx

@@ -179,14 +179,14 @@ For **ERC-20** token withdrawals, see the dedicated [Withdraw tokens guide](/arb
 The Arbitrum SDK simplifies child-to-parent messaging:
 
 ```javascript
-import { L2ToL1MessageStatus, L2TransactionReceipt } from '@arbitrum/sdk';
+import { ChildToParentMessageStatus, ChildTransactionReceipt } from '@arbitrum/sdk';
 
 // Get the L2 transaction receipt
 const l2Receipt = await childChainProvider.getTransactionReceipt(l2TxHash);
-const l2TxReceipt = new L2TransactionReceipt(l2Receipt);
+const childTxReceipt = new ChildTransactionReceipt(l2Receipt);
 
-// Get L2ToL1 messages from the transaction
-const messages = await l2TxReceipt.getL2ToL1Messages(parentChainSigner);
+// Get child-to-parent messages from the transaction
+const messages = await childTxReceipt.getChildToParentMessages(parentChainSigner);
 
 // Wait for the message to be executable
 const message = messages[0];
@@ -197,6 +197,34 @@ const executeResult = await message.execute(childChainProvider);
 await executeResult.wait();
 ```
 
+### Withdraw ETH using the Arbitrum SDK
+
+The SDK also provides an `EthBridger` class that simplifies `ETH` withdrawals:
+
+```ts
+import { getArbitrumNetwork, EthBridger } from '@arbitrum/sdk';
+import { ethers } from 'ethers';
+
+const childNetwork = await getArbitrumNetwork(childProvider);
+const ethBridger = new EthBridger(childNetwork);
+
+// Initiate withdrawal from child chain
+const withdrawTx = await ethBridger.withdraw({
+  amount: ethers.utils.parseEther('0.1'),
+  childSigner,
+  from: walletAddress,
+  destinationAddress: walletAddress,
+});
+const withdrawReceipt = await withdrawTx.wait();
+
+// Get child-to-parent events for later outbox execution
+const withdrawEvents = withdrawReceipt.getChildToParentEvents();
+```
+
+After the 6.4-day challenge period, use the outbox execution flow described above (or the SDK's `ChildToParentMessage.execute`) to claim your `ETH` on the parent chain.
+
+For a complete example, see the [eth-withdraw tutorial](https://github.com/OffchainLabs/arbitrum-tutorials/tree/master/packages/eth-withdraw).
+
 ## Message lifecycle
 
 Child-to-parent messages go through these stages:
@@ -211,4 +239,4 @@ Child-to-parent messages go through these stages:
 
 - For protocol-level details, see [Child to parent chain messaging](/how-arbitrum-works/deep-dives/l2-to-l1-messaging.mdx)
 - For token bridging concepts, see [Token bridging overview](/how-arbitrum-works/deep-dives/token-bridging.mdx)
-- For the Arbitrum SDK documentation, see [SDK reference](/sdk)
+- For the Arbitrum SDK documentation, see [Arbitrum SDK](https://github.com/OffchainLabs/arbitrum-sdk)