From 18b020a37a7c8b32255e3da5533272d4c27bff5d Mon Sep 17 00:00:00 2001 From: wgyt Date: Tue, 24 Dec 2024 09:34:27 +0800 Subject: [PATCH] fix links --- how-to-guides/arbitrum-integration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/how-to-guides/arbitrum-integration.md b/how-to-guides/arbitrum-integration.md index 52b0dddb6b4..37b5b7ac005 100644 --- a/how-to-guides/arbitrum-integration.md +++ b/how-to-guides/arbitrum-integration.md @@ -81,7 +81,7 @@ from the scalability Celestia’s data availability layer can provide. ### Ethereum fallback mechanism in Nitro By default in [Arbitrum Nitro](https://github.com/OffchainLabs/nitro), the -[Ethereum fallback mechanism in the `BatchPoster` function](https://github.com/OffchainLabs/nitro/blob/master/arbnode/batch_poster.go#L989-L1001) +[Ethereum fallback mechanism in the `BatchPoster` function](https://github.com/OffchainLabs/nitro/blob/d74229c5bcd592db7f6c7e37aa64375f53d2266d/arbnode/batch_poster.go#L1419~L1485) is handling the process of storing data, with a fallback mechanism to store data onchain if the primary data availability storage fails.