diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index b989c1cd964..89198dfb4f9 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -4,7 +4,7 @@ Thanks for considering making a contribution to the IOTA network or its document
 
 ## Contribute to IOTA
 
-See [IOTA Environment Setup](https://github.com/iotaledger/iota/blob/main/docs/content/developer/getting-started/iota-environment.mdx) for approach to submitting code fixes and enhancements.
+See [IOTA Environment Setup](https://github.com/iotaledger/iota/blob/develop/docs/content/developer/getting-started/iota-environment.mdx) for approach to submitting code fixes and enhancements.
 
 Found a bug or security vulnerability? Create a [GitHub issue](https://github.com/iotaledger/iota/issues/new/choose).
 
diff --git a/chocolatey/iota.nuspec b/chocolatey/iota.nuspec
index 173e11fe35d..26d9153b6bd 100644
--- a/chocolatey/iota.nuspec
+++ b/chocolatey/iota.nuspec
@@ -9,7 +9,7 @@ enclosed in quotation marks, you should use an editor that supports UTF-8, not t
 		<title>Main Iota Binary</title>
 		<authors>iota</authors>
 		<projectUrl>https://iota.org/</projectUrl>
-		<licenseUrl>https://github.com/iotaledger/iota/blob/main/LICENSE</licenseUrl>
+		<licenseUrl>https://github.com/iotaledger/iota/blob/develop/LICENSE</licenseUrl>
 		<iconUrl>https://assets-global.website-files.com/6425f546844727ce5fb9e5ab/643775f4a15c9a9e10426daa_Iota_Favicon_256.png</iconUrl>
 		<projectSourceUrl>https://github.com/iotaledger/iota/</projectSourceUrl>
 		<bugTrackerUrl>https://github.com/iotaledger/iota/issues</bugTrackerUrl>
diff --git a/crates/iota-types/src/README.md b/crates/iota-types/src/README.md
index 9c999feada9..2ed1f4446db 100644
--- a/crates/iota-types/src/README.md
+++ b/crates/iota-types/src/README.md
@@ -3,7 +3,7 @@
 Note: this README file currently covers cryptography-related structs and methods.
 
 Currently, three files are equipped with signature and hashing functionality (`crypto.rs`, `signature_seed` and
-`messages.rs`). See [Iota Signatures](https://github.com/iotaledger/iota/blob/main/docs/content/concepts/cryptography/transaction-auth/signatures.mdx) for supported signature schemes and its requirments for user and authority signatures. See [fastcrypto](https://github.com/MystenLabs/fastcrypto) for concrete implementation of various cryptography libraries.
+`messages.rs`). See [Iota Signatures](https://github.com/iotaledger/iota/blob/develop/docs/content/concepts/cryptography/transaction-auth/signatures.mdx) for supported signature schemes and its requirments for user and authority signatures. See [fastcrypto](https://github.com/MystenLabs/fastcrypto) for concrete implementation of various cryptography libraries.
 
 ## Quick links
 
diff --git a/docs/content/developer/advanced/onchain-randomness.mdx b/docs/content/developer/advanced/onchain-randomness.mdx
index 730a5e5a29d..fd8aecefd37 100644
--- a/docs/content/developer/advanced/onchain-randomness.mdx
+++ b/docs/content/developer/advanced/onchain-randomness.mdx
@@ -135,7 +135,7 @@ In many cases this is not an issue, like when selecting a raffle winner, lottery
     - Use [profile-transaction](../../references/cli/client.mdx#profile-a-transaction) on Testnet transactions to verify the costs of different flows.
 - Split the logic in two: one function that fetches a random value and stores it in an object, and another function that reads that stored value and completes the operation. The latter function might indeed fail, but now the random value is fixed and cannot be modified using repeated calls.
 
-See [random_nft](https://github.com/iotaledger/iota/blob/main/examples/move/random/random_nft) for examples.
+See [random_nft](https://github.com/iotaledger/iota/blob/develop/examples/move/random/random_nft) for examples.
 
 Other limited resources per transaction are:
 
diff --git a/docs/content/developer/getting-started/local-network.mdx b/docs/content/developer/getting-started/local-network.mdx
index 8451b219379..1bbf52e86e6 100644
--- a/docs/content/developer/getting-started/local-network.mdx
+++ b/docs/content/developer/getting-started/local-network.mdx
@@ -225,7 +225,7 @@ After you build your local version of IOTA Wallet, you can add the extension to
 3. Click the **Load unpacked** button and select your `apps/wallet/dist` directory in your local copy of the [IOTA repository](../advanced/iota-repository.mdx).
 
 Consult the IOTA
-Wallet [Readme](https://github.com/iotaledger/iota/blob/main/apps/wallet/README.md#install-the-extension-to-chrome) for
+Wallet [Readme](https://github.com/iotaledger/iota/blob/develop/apps/wallet/README.md#install-the-extension-to-chrome) for
 more information on working with a locally built wallet on Chrome is needed.
 
 ## Generate example data
diff --git a/docs/content/developer/iota-101/move-overview/patterns/hot-potato.mdx b/docs/content/developer/iota-101/move-overview/patterns/hot-potato.mdx
index 0ba77b4c015..dace6aa798b 100644
--- a/docs/content/developer/iota-101/move-overview/patterns/hot-potato.mdx
+++ b/docs/content/developer/iota-101/move-overview/patterns/hot-potato.mdx
@@ -15,6 +15,6 @@ This approach is particularly useful in scenarios like implementing flash loans.
 ```move file=<rootDir>/docs/examples/move/move-overview/patterns/hot-potato.move
 ```
 
-The [Flash Loan](https://github.com/iotaledger/iota/blob/main/examples/move/flash_lender/sources/example.move) example specifically illustrates the hot potato pattern described in this topic.
+The [Flash Loan](https://github.com/iotaledger/iota/blob/develop/examples/move/flash_lender/sources/example.move) example specifically illustrates the hot potato pattern described in this topic.
 
 <Quiz questions={questions} />
\ No newline at end of file
diff --git a/docs/content/developer/iota-101/move-overview/patterns/id-pointer.mdx b/docs/content/developer/iota-101/move-overview/patterns/id-pointer.mdx
index c85b6dbb214..db5a929719e 100644
--- a/docs/content/developer/iota-101/move-overview/patterns/id-pointer.mdx
+++ b/docs/content/developer/iota-101/move-overview/patterns/id-pointer.mdx
@@ -27,6 +27,6 @@ such as a marketplace listing.
 ```move file=<rootDir>/docs/examples/move/move-overview/patterns/id-pointer.move
 ```
 
-This pattern is demonstrated in the [Hero](https://github.com/iotaledger/iota/blob/main/examples/move/hero/sources/example.move) example.
+This pattern is demonstrated in the [Hero](https://github.com/iotaledger/iota/blob/develop/examples/move/hero/sources/example.move) example.
 
 <Quiz questions={questions} />
diff --git a/docs/content/developer/iota-101/move-overview/patterns/transferable-witness.mdx b/docs/content/developer/iota-101/move-overview/patterns/transferable-witness.mdx
index a78f8c85809..b673fff15c9 100644
--- a/docs/content/developer/iota-101/move-overview/patterns/transferable-witness.mdx
+++ b/docs/content/developer/iota-101/move-overview/patterns/transferable-witness.mdx
@@ -54,7 +54,7 @@ This carrier can be sent to authorized users, who can then extract the witness w
 
 ## Related Examples
 
-For more insights and practical implementations of advanced authorization patterns in Move, consider exploring the [Hero](https://github.com/iotaledger/iota/blob/main/examples/move/hero/sources/example.move) example.
+For more insights and practical implementations of advanced authorization patterns in Move, consider exploring the [Hero](https://github.com/iotaledger/iota/blob/develop/examples/move/hero/sources/example.move) example.
 This example demonstrates how transferable witnesses and similar patterns can be applied to build secure and robust smart contracts on the IOTA platform.
 
 <Quiz questions={questions} />
\ No newline at end of file
diff --git a/docs/content/developer/iota-101/objects/object-model.mdx b/docs/content/developer/iota-101/objects/object-model.mdx
index 9e7b86b46a6..8572bafa36d 100644
--- a/docs/content/developer/iota-101/objects/object-model.mdx
+++ b/docs/content/developer/iota-101/objects/object-model.mdx
@@ -67,6 +67,6 @@ such as those owned by a single address.
 IOTA imposes certain limits on transactions and the data used within them,
 including maximum sizes and the number of objects involved.
 
-The `ProtocolConfig` struct in the [`iota-protocol-config` crate](https://github.com/iotaledger/iota/blob/main/crates/iota-protocol-config/src/lib.rs) itemizes these limits. Expand the following code to see the `ProtocolConfig` struct and the comments that explain each parameter.
+The `ProtocolConfig` struct in the [`iota-protocol-config` crate](https://github.com/iotaledger/iota/blob/develop/crates/iota-protocol-config/src/lib.rs) itemizes these limits. Expand the following code to see the `ProtocolConfig` struct and the comments that explain each parameter.
 
 <Quiz questions={questions} />
diff --git a/docs/content/developer/iota-101/objects/object-ownership/immutable.mdx b/docs/content/developer/iota-101/objects/object-ownership/immutable.mdx
index 572cc3bdbf5..570f0fded88 100644
--- a/docs/content/developer/iota-101/objects/object-ownership/immutable.mdx
+++ b/docs/content/developer/iota-101/objects/object-ownership/immutable.mdx
@@ -25,7 +25,7 @@ Once frozen, the object can no longer be mutated.
 You should only freeze an object when you are sure it no longer requires any modifications.
 
 For example,
-the [color_object example module](https://github.com/iotaledger/iota/blob/main/examples/move/color_object/sources/example.move) includes a test
+the [color_object example module](https://github.com/iotaledger/iota/blob/develop/examples/move/color_object/sources/example.move) includes a test
 that creates a new `ColorObject`,
 then calls `public_freeze_object` to make it immutable:
 
diff --git a/docs/site/docusaurus.config.js b/docs/site/docusaurus.config.js
index df5b62b56b3..13c95c94996 100644
--- a/docs/site/docusaurus.config.js
+++ b/docs/site/docusaurus.config.js
@@ -256,7 +256,7 @@ const config = {
           alt: "IOTA Wiki Logo",
           src: "/logo/iota-logo.svg",
         },
-        copyright: `Copyright © ${new Date().getFullYear()} <a href='https://www.iota.org/'>IOTA Stiftung</a>, licensed under <a href="https://github.com/iotaledger/iota/blob/main/docs/site/LICENSE">CC BY 4.0</a>. 
+        copyright: `Copyright © ${new Date().getFullYear()} <a href='https://www.iota.org/'>IOTA Stiftung</a>, licensed under <a href="https://github.com/iotaledger/iota/blob/develop/docs/site/LICENSE">CC BY 4.0</a>. 
                     The documentation on this website is adapted from the <a href='https://docs.sui.io/'>SUI Documentation</a>, © 2024 by <a href='https://sui.io/'>SUI Foundation</a>, licensed under <a href="https://github.com/MystenLabs/sui/blob/main/docs/site/LICENSE">CC BY 4.0</a>.`,
       },
       socials: [
diff --git a/nre/validator_tasks.md b/nre/validator_tasks.md
index ce7c4c1ee43..9384d2c4111 100644
--- a/nre/validator_tasks.md
+++ b/nre/validator_tasks.md
@@ -418,13 +418,13 @@ This release process will be different and we expect to announce the directory f
 <!-- Our public key to verify these binaries would be stored [here](https://<TODO_SECURITY_FIXES_URL>/iota_security_release.pem) -->
 
 You can download all the necessary signed binaries and docker artifacts incorporating the security fixes by using
-the [download_private.sh](https://github.com/iotaledger/iota/blob/main/nre/download_private.sh)
+the [download_private.sh](https://github.com/iotaledger/iota/blob/develop/nre/download_private.sh)
 
 Usage
 `./download_private.sh <directory-name>`
 
 You can also download and verify specific binaries that may not be included by the above script using
-the [download_and_verify_private_binary.sh](https://github.com/iotaledger/iota/blob/main/nre/download_and_verify_private_binary.sh)
+the [download_and_verify_private_binary.sh](https://github.com/iotaledger/iota/blob/develop/nre/download_and_verify_private_binary.sh)
 script.
 
 Usage:
diff --git a/sdk/typescript/README.md b/sdk/typescript/README.md
index 3bc7758c018..9018fc5c12a 100644
--- a/sdk/typescript/README.md
+++ b/sdk/typescript/README.md
@@ -10,7 +10,7 @@ For more complete docs, visit the
 > **Note**: This package is currently supported **only in Testnet and Devnet**, it is **not yet supported in Mainnet**.
 
 This is the IOTA TypeScript SDK built on the IOTA
-[JSON RPC API](https://github.com/iotaledger/iota/blob/main/docs/content/references/iota-api.mdx).
+[JSON RPC API](https://github.com/iotaledger/iota/blob/develop/docs/content/references/iota-api.mdx).
 It provides utility classes and functions for applications to sign transactions and interact with
 the IOTA network.
 
@@ -22,7 +22,7 @@ upcoming TestNet launch.
 
 The SDK will be published to [npm registry](https://www.npmjs.com/package/@iota/iota-sdk) with the
 same bi-weekly release cycle as the Devnet validators and
-[RPC Server](https://github.com/iotaledger/iota/blob/main/docs/content/references/iota-api.mdx). To
+[RPC Server](https://github.com/iotaledger/iota/blob/develop/docs/content/references/iota-api.mdx). To
 use the SDK in your project, you can do:
 
 ```bash
@@ -43,7 +43,7 @@ npm install @iota/iota-sdk@experimental
 ```
 
 Refer to the
-[JSON RPC](https://github.com/iotaledger/iota/blob/main/docs/content/references/iota-api.mdx) topic
+[JSON RPC](https://github.com/iotaledger/iota/blob/develop/docs/content/references/iota-api.mdx) topic
 for instructions about how to start a local network and local RPC server.
 
 ## Building Locally