diff --git a/developers/arbitrum-deploy.md b/developers/arbitrum-deploy.md
index df057e196b7..3af5aa8a5e9 100644
--- a/developers/arbitrum-deploy.md
+++ b/developers/arbitrum-deploy.md
@@ -4,8 +4,6 @@ description: A guide on how to install Arbitrum Nitro and deploy an instance on
 
 # Deploy an Arbitrum rollup devnet
 
-![nitro-vroom](/img/nitro-vroom-devnet.png)
-
 We will go over installation of Arbitrum Nitro and deploying an instance on an
 Ubuntu AMD machine. This section covers all necessary dependencies needed to be
 installed.
@@ -77,14 +75,42 @@ to this version so that the tutorial works for anyone using it ATM. -->
 ```bash
 git clone https://github.com/celestiaorg/nitro.git && cd nitro/
 git fetch --all
-git checkout c6f5ac2
+# checkout to the stable commit on the blobstream-develop branch
+git checkout 52323cc
 git submodule update --init
 git submodule update --init --recursive
 ```
 
 ## Installing Nitro from Source
 
-Now you can install Nitro from source. After the `make` command completes,
+Before installing Nitro, you'll need to build a local version of
+a Celestia local devnet. Follow these commands to do so:
+
+```bash
+# clone the repo
+git clone https://github.com/rollkit/local-celestia-devnet.git
+cd local-celestia-devnet
+
+# checkout to the stable commit on the blobstream-develop branch
+git checkout 997edce
+
+# build the image
+docker build . -t celestia-local-devnet
+```
+
+:::tip
+If you're on a Mac, you'll need comment out the platform in
+`docker-compose.yml`:
+
+```yaml-vue
+  da:
+    container_name: 'da-celestia'
+    # platform: linux/x86_64 // [!code focus]
+```
+
+:::
+
+Now, you can install Nitro from source. After the `make` command completes,
 you can run the bash script that installs and runs the containers via
 docker-compose.
 
diff --git a/developers/arbitrum-integration.md b/developers/arbitrum-integration.md
index bc6fe813f20..b4a0d8a096e 100644
--- a/developers/arbitrum-integration.md
+++ b/developers/arbitrum-integration.md
@@ -39,14 +39,8 @@ include:
 
 ### Blobstream
 
-:::warning UPCOMING INTEGRATION
-The Blobstream section is currently under development. Please note that
-the integration with Blobstream is not yet finalized, but it is planned
-for implementation in the near future.
-:::
-
-The Celestia and Arbitrum integration also
-[includes Blobstream](./blobstream.md),
+The Celestia and Arbitrum integration also includes
+[Blobstream](./blobstream.md),
 which relays commitments to Celestia’s data root to an onchain light client
 on Ethereum. This allows L2 solutions that settle on Ethereum to benefit
 from the scalability Celestia’s data availability layer can provide.
diff --git a/developers/arbitrum-mocha.md b/developers/arbitrum-mocha.md
index 67ccdc9e3d1..e7af70cb267 100644
--- a/developers/arbitrum-mocha.md
+++ b/developers/arbitrum-mocha.md
@@ -4,13 +4,15 @@ description: An overview of the deploying Arbitrum Nitro and Celestia rollup to
 
 # Deploy an Arbitrum rollup to Mocha testnet
 
-![nitro-vroom](/img/nitro-vroom.png)
-
 <!-- markdownlint-disable MD033 -->
 <script setup>
 import constants from '/.vitepress/constants/constants.js'
 </script>
 
+:::warning
+This tutorial is under construction. 🏗️
+:::
+
 This guide covers deploying an Arbitrum Nitro rollup to
 [Mocha testnet](../nodes/mocha-testnet.md) using Celestia as DA.
 
@@ -36,11 +38,11 @@ This guide covers deploying an Arbitrum Nitro rollup to
 
    ```bash-vue
    da:
-       container_name: 'celestia-da' // [!code ++]
+       container_name: 'da-celestia'
        user: root // [!code ++]
        platform: linux/x86_64
        image: "ghcr.io/rollkit/local-celestia-devnet:v0.12.1" // [!code --]
-       image: "ghcr.io/celestiaorg/celestia-node:v0.12.1" // [!code ++]
+       image: "ghcr.io/celestiaorg/celestia-node:v0.12.3" // [!code ++]
        command: > // [!code ++]
                celestia light start // [!code ++]
                --core.ip rpc-mocha.pops.one // [!code ++]
@@ -77,9 +79,9 @@ This guide covers deploying an Arbitrum Nitro rollup to
 
    # Line 287
    # NOTE: depending on the version you're using, you may have a different
-   # container name to start. Change yours accordingly to `celestia-da`.
+   # container name to start. Change yours accordingly to `da-celestia`.
    export CELESTIA_NODE_AUTH_TOKEN="$(docker exec nitro-testnode-da-1 celestia bridge auth admin --node.store  ${NODE_PATH})" // [!code --]
-   export CELESTIA_NODE_AUTH_TOKEN="$(docker exec celestia-da celestia light auth admin --node.store  ${NODE_PATH})" // [!code ++]
+   export CELESTIA_NODE_AUTH_TOKEN="$(docker exec da-celestia celestia light auth admin --node.store  ${NODE_PATH})" // [!code ++]
    ```
 
 4. Pick a namespace, `<your-10bytenamespace>` that is 10 bytes in hexadecimal.
@@ -93,9 +95,7 @@ This guide covers deploying an Arbitrum Nitro rollup to
    "namespace-id": "<your-10bytenamespace>", // [!code ++]
    ```
 
-[See an example diff of the setup](https://github.com/celestiaorg/nitro/pull/4/files),
-specifically
-[the updates to nitro-testnode](https://github.com/celestiaorg/nitro-testnode/pull/6/files).
+5. TODO ADD CHANGES FOR BLOBSTREAM
 
 ## Run your Nitro rollup on Mocha
 
diff --git a/public/img/nitro-vroom-devnet.png b/public/img/nitro-vroom-devnet.png
deleted file mode 100644
index 69a5bdc8f61..00000000000
Binary files a/public/img/nitro-vroom-devnet.png and /dev/null differ
diff --git a/public/img/nitro-vroom.png b/public/img/nitro-vroom.png
deleted file mode 100644
index 365db4d1f2b..00000000000
Binary files a/public/img/nitro-vroom.png and /dev/null differ