celestiaorg · jcstein · Jan 5, 2026 · Dec 19, 2025 · Dec 19, 2025
diff --git a/app/build/blobstream/integrate-offchain/page.mdx b/app/build/blobstream/integrate-offchain/page.mdx
@@ -34,7 +34,7 @@ type Header struct {
 }
 ```
 
-Note the Celestia-specific structures in the header such as the `Namespace` and the Blobstream-specific structure called the `Span`. The goal of these structures is to locate the data in the Celestia block so that we can prove that data's inclusion via Blobstream if needed. Read more in the [namespace specifications](https://celestiaorg.github.io/celestia-app/specs/namespace.html), and you can think of this like a chain ID. Learn more [information about `shares`](https://celestiaorg.github.io/celestia-app/specs/shares.html), which are small chunks of the encoded Celestia block. We use the same encoding here so that the commitments to the rollup block match those committed to by validators in the Celestia data root.
+Note the Celestia-specific structures in the header such as the `Namespace` and the Blobstream-specific structure called the `Span`. The goal of these structures is to locate the data in the Celestia block so that we can prove that data's inclusion via Blobstream if needed. Read more in the [namespace specifications](https://celestiaorg.github.io/celestia-app/namespace.html), and you can think of this like a chain ID. Learn more [information about `shares`](https://celestiaorg.github.io/celestia-app/shares.html), which are small chunks of the encoded Celestia block. We use the same encoding here so that the commitments to the rollup block match those committed to by validators in the Celestia data root.
 
 The `Span` could take many forms, but in this demo we will use the following:
 
@@ -71,7 +71,7 @@ The rollup sequencer is responsible for creating blocks and, in this demo, writi
 
 Therefore, we can start by first defining the reading and writing interactions rollup nodes will have with both the Celestia and Ethereum networks. The actual implementations of these interfaces are left as exercises to the reader. Assume that those implementations of these interfaces are verifying the respective chain. For the connection to Celestia, this would likely mean connecting to a Celestia light node, which can detect faults in consensus such as hidden data. For the connection to Ethereum, this would likely mean running and connecting to a full node.
 
-More information on the RPC that is exposed by a Celestia light node can be found [in the RPC documentation](https://node-rpc-docs.celestia.org/?version=v0.28.4). Additionally, if you need more information on how to run a light node, you can [check out the documentation](/operate/data-availability/light-node).
+More information on the RPC that is exposed by a Celestia light node can be found [in the RPC documentation](https://node-rpc-docs.celestia.org/?version=v0.28.4). Additionally, if you need more information on how to run a light node, you can [check out the documentation](/operate/data-availability/light-node/quickstart).
 
 ```go
 // CelestiaLightNodeClient summarizes the actions that a rollup that uses
@@ -124,7 +124,7 @@ For optimistic rollups, this could be as simple as referencing the data in the C
 
 For zk rollups, this would involve creating an inclusion proof to the data root tuple root in the Blobstream contracts, and then verifying that proof in the zk proof used to verify state. Find more information in the [data root inclusion proof documentation](https://github.com/celestiaorg/blobstream-contracts/blob/master/docs/inclusion-proofs.md#1-data-root-inclusion-proof).
 
-Also see the documentation for the [data square layout](https://github.com/celestiaorg/celestia-app/blob/v1.1.0/specs/src/specs/data_square_layout.md) and the [shares](https://github.com/celestiaorg/celestia-app/blob/main/specs/src/specs/shares.md) of the Celestia block to see how the data is encoded in Celestia.
+Also see the documentation for the [data square layout](https://github.com/celestiaorg/celestia-app/blob/v1.1.0/specs/src/specs/data_square_layout.md) and the [shares](https://github.com/celestiaorg/celestia-app/blob/main/specs/src/shares.md) of the Celestia block to see how the data is encoded in Celestia.
 
 ### Creating blocks
 
@@ -242,7 +242,7 @@ This outline of a Blobstream rollup isn't doing execution or state transitions i
 
 ### Submitting block data to Celestia using client tx
 
-As linked above, use the [Celestia Node API](/build/rpc/node-api/?version=v0.28.4#blob.Submit) or [check out the tutorial](/build/post-retrieve-blob/client/go/) to submit the data to Celestia.
+As linked above, use the [Celestia Node API](/build/rpc/node-api) or [check out the tutorial](/build/post-retrieve-blob/client/go/) to submit the data to Celestia.
 
 ### Posting headers to Ethereum
 

diff --git a/app/learn/blobstream/page.mdx b/app/learn/blobstream/page.mdx
@@ -20,7 +20,7 @@ Celestia and then verify that it was published in the target EVM chain.
 
 ![Blobstream Architecture](/img/blobstream/Blobstream.png)
 
-Data is first attested to by the Celestia validator set—they sign commitments to the data. Then, these signatures are relayed to the target EVM chain (in this case, Ethereum). Finally, the layer 2, or any party, can verify that the data was published to Celestia directly on the EVM chain via the Blobstream smart contract. You can reference [the Blobstream smart contract](https://github.com/celestiaorg/blobstream-contracts/blob/master/src/Blobstream.sol).
+Data is first attested to by the Celestia validator set—they sign commitments to the data. Then, these signatures are relayed to the target EVM chain (in this case, Ethereum). Finally, the layer 2, or any party, can verify that the data was published to Celestia directly on the EVM chain via the Blobstream smart contract. You can reference [the Blobstream smart contract](https://github.com/celestiaorg/blobstream-contracts/blob/v3.0.0/src/Blobstream.sol).
 
 The specification of Blobstream `Valset`s, which track the Celestia validator set changes, can be found in [ADR 002](https://github.com/celestiaorg/celestia-app/blob/main/docs/architecture/adr-002-qgb-valset.md).
 

diff --git a/app/operate/blobstream/install-binary/page.mdx b/app/operate/blobstream/install-binary/page.mdx
@@ -41,7 +41,7 @@ If you want to post commitments on an EVM chain, you will need to deploy a new B
 
 ### Tools
 
-1. Install [golangci-lint](https://golangci-lint.run/usage/install/)
+1. Install [golangci-lint](https://golangci-lint.run/docs/welcome/install/)
 2. Install [markdownlint](https://github.com/DavidAnson/markdownlint)
 
 ### Helpful Commands
@@ -60,7 +60,7 @@ make fmt
 ## Useful links
 
 - The smart contract implementation is in [blobstream-contracts](https://github.com/celestiaorg/blobstream-contracts/)
-- The state machine implementation is in [x/blobstream](https://github.com/celestiaorg/celestia-app/tree/main/x/blobstream)
+- The state machine implementation is in [orchestrator-relayer](https://github.com/celestiaorg/orchestrator-relayer)
 - Blobstream ADRs are in [the docs](https://github.com/celestiaorg/celestia-app/tree/main/docs/architecture)
 - Blobstream design explained in [this blog post on layer 2s](https://blog.celestia.org/celestiums/)
 
diff --git a/app/operate/blobstream/orchestrator/page.mdx b/app/operate/blobstream/orchestrator/page.mdx
@@ -1,6 +1,6 @@
 # Blobstream orchestrator
 
-The role of the orchestrator is to sign attestations using its corresponding validator EVM private key. These attestations are generated within the Blobstream module of the Celestia-app state machine. To learn more about what attestations are, you can refer to [the Blobstream overview](https://github.com/celestiaorg/celestia-app/tree/main/x/blobstream).
+The role of the orchestrator is to sign attestations using its corresponding validator EVM private key. These attestations are generated within the Blobstream module of the Celestia-app state machine. To learn more about what attestations are, you can refer to [the Blobstream overview](https://github.com/celestiaorg/orchestrator-relayer).
 
 ## How it works
 

diff --git a/app/operate/blobstream/relayer/page.mdx b/app/operate/blobstream/relayer/page.mdx
@@ -1,6 +1,6 @@
 # Blobstream relayer
 
-The role of the relayer is to gather attestations' signatures from the orchestrators, and submit them to a target EVM chain. The attestations are generated within the Blobstream module of the Celestia-app state machine. To learn more about what attestations are, you can refer to [the Blobstream overview](https://github.com/celestiaorg/celestia-app/tree/main/x/blobstream).
+The role of the relayer is to gather attestations' signatures from the orchestrators, and submit them to a target EVM chain. The attestations are generated within the Blobstream module of the Celestia-app state machine. To learn more about what attestations are, you can refer to [the Blobstream overview](https://github.com/celestiaorg/orchestrator-relayer).
 
 While every validator in the Celestia validator set needs to run an orchestrator, only one entity needs to run the relayer, and it can be anyone. Thus, if you're a validator, most likely you want to read [the orchestrator documentation](/operate/blobstream/orchestrator).
 

diff --git a/app/operate/consensus-validators/install-celestia-app/page.mdx b/app/operate/consensus-validators/install-celestia-app/page.mdx
@@ -118,7 +118,7 @@ preferences.
 You will see an output with the menu for `celestia-appd`. Learn more
 on the [helpful CLI commands page](/operate/consensus-validators/cli-reference)
 
-View [the script](https://github.com/celestiaorg/docs/tree/main/public/celestia-app.sh)
+View [the script](https://github.com/celestiaorg/docs/blob/main/public/celestia-app.sh)
 to learn more about what it is doing.
 
 ## Ports

diff --git a/app/operate/data-availability/install-celestia-node/page.mdx b/app/operate/data-availability/install-celestia-node/page.mdx
@@ -121,10 +121,10 @@ You can install the latest version or specify a particular version:
 
 ```bash
 # Install latest version
-bash -c "$(curl -sL https://raw.githubusercontent.com/celestiaorg/docs/main/public/celestia-node.sh)"
+bash -c "$(curl -sL https://docs.celestia.org/celestia-node.sh)"
 
 # Install specific version, Mainnet Beta in this example
-bash -c "$(curl -sL https://raw.githubusercontent.com/celestiaorg/docs/main/public/celestia-node.sh)" -- -v {{mainnetVersions['node-latest-tag']}}
+bash -c "$(curl -sL https://docs.celestia.org/celestia-node.sh)" -- -v {{mainnetVersions['node-latest-tag']}}
 ```
 
 The script will:
@@ -147,7 +147,7 @@ Follow the instructions in the terminal output to choose your installation prefe
 celestia version && celestia --help
 ```
 
-View [the script](https://github.com/celestiaorg/docs/tree/main/public/celestia-node.sh) to learn more about what it is doing.
+View [the script](https://github.com/celestiaorg/docs/blob/main/public/celestia-node.sh) to learn more about what it is doing.
 
 > **Note**: The script maintains a log file at `$HOME/celestia-node-temp/logfile.log` for troubleshooting purposes.
 

diff --git a/app/operate/maintenance/snapshots/page.mdx b/app/operate/maintenance/snapshots/page.mdx
@@ -47,7 +47,6 @@ Their services include installation scripts, state sync, snapshots, RPC endpoint
 
 | Provider    | Consensus Node                                                                                                                                 | Bridge Node                                                                |
 | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
-| Stake Town  | [Pruned](https://services.stake-town.com/home/mainnet/celestia/sync)                                                                           | -                                                                          |
 | ITRocket    | [Pruned](https://itrocket.net/services/mainnet/celestia/) • [Archive](https://itrocket.net/services/mainnet/celestia/)                         | [Archive](https://itrocket.net/services/mainnet/celestia/)                 |
 | Polkachu    | [Pruned](https://polkachu.com/tendermint_snapshots/celestia)                                                                                   | -                                                                          |
 | kjnodes     | [Pruned](https://services.kjnodes.com/mainnet/celestia/snapshot/) • [Archive](https://services.kjnodes.com/mainnet/celestia/snapshot-archive/) | -                                                                          |
@@ -60,7 +59,6 @@ Their services include installation scripts, state sync, snapshots, RPC endpoint
 
 | Provider    | Consensus Node                                                                                                         | Bridge Node                                                                |
 | ----------- | ---------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
-| Stake Town  | [Pruned](https://services.stake-town.com/home/testnet/celestia/sync)                                                   | -                                                                          |
 | ITRocket    | [Pruned](https://itrocket.net/services/testnet/celestia/) • [Archive](https://itrocket.net/services/testnet/celestia/) | [Archive](https://itrocket.net/services/testnet/celestia/)                 |
 | Polkachu    | [Pruned](https://polkachu.com/testnets/celestia/snapshots)                                                             | -                                                                          |
 | kjnodes     | [Pruned](https://services.kjnodes.com/testnet/celestia/snapshot/)                                                      | -                                                                          |

diff --git a/app/operate/networks/mainnet-beta/page.mdx b/app/operate/networks/mainnet-beta/page.mdx
@@ -240,7 +240,6 @@ The following websites provide analytics for Celestia:
 
 - [https://alphab.ai/s/m/celestia/](https://alphab.ai/s/m/celestia/)
 - [https://celestiahub.org/explorer/blobs](https://celestiahub.org/explorer/blobs)
-- [https://cosmoslist.co/mainnet/celestia](https://cosmoslist.co/mainnet/celestia)
 - [https://itrocket.net/services/mainnet/celestia/](https://itrocket.net/services/mainnet/celestia/) - Node setup, monitoring, and chain status tools
 - [https://itrocket.net/services/mainnet/celestia/analytics/consensus-signal-tracker/](https://itrocket.net/services/mainnet/celestia/analytics/consensus-signal-tracker/) - Consensus signal tracker
 - [https://itrocket.net/services/mainnet/celestia/decentralization/](https://itrocket.net/services/mainnet/celestia/decentralization/)

diff --git a/app/operate/networks/mocha-testnet/page.mdx b/app/operate/networks/mocha-testnet/page.mdx
@@ -238,7 +238,6 @@ The web faucet is available at [https://mocha.celenium.io/faucet](https://mocha.
 
 The following websites provide analytics for Mocha Testnet:
 
-- [cosmoslist.co/testnet/celestia](https://cosmoslist.co/testnet/celestia)
 - [https://itrocket.net/services/testnet/celestia/](https://itrocket.net/services/testnet/celestia/) - Node setup, monitoring, and chain status tools
 
 ## Node maps