Merge branch 'master' into nhussein11/fix-foundry-guide

Author: nhussein11

.snippets/code/develop/parachains/get-started/install-polkadot-sdk/termynal-2.html

@@ -4,15 +4,9 @@
   <br />
   <span data-ty>active toolchain</span>
   <span data-ty>----------------</span>
-  <br />
-  <span data-ty>stable-x86_64-apple-darwin (default)</span>
-  <span data-ty>rustc 1.81.0 (eeb90cda1 2024-09-04)</span>
-  <br />
-  <span data-ty>...</span>
-  <br />
-  <span data-ty>active toolchain</span>
-  <span data-ty>----------------</span>
-  <br />
-  <span data-ty>nightly-x86_64-apple-darwin (overridden by +toolchain on the command line)</span>
-  <span data-ty>rustc 1.83.0-nightly (6c6d21008 2024-09-22)</span>
+  <span data-ty>name: stable-aarch64-apple-darwin</span>
+  <span data-ty>active because: it's the default toolchain</span>
+  <span data-ty>installed targets:</span>
+  <span data-ty>  aarch64-apple-darwin</span>
+  <span data-ty>  wasm32-unknown-unknown</span>
 </div>

.snippets/text/smart-contracts/polkaVM-warning.md

@@ -0,0 +1,2 @@
+!!! smartcontract "PolkaVM Alpha Release"
+    PolkaVM smart contracts with Ethereum compatibility are in **early-stage development and may be unstable or incomplete**.

develop/interoperability/send-messages.md

@@ -86,7 +86,7 @@ For further information about the `send` extrinsic, see the [`pallet-xcm` docume
 
 The [`XcmRouter`](https://paritytech.github.io/polkadot-sdk/master/pallet_xcm/pallet/trait.Config.html#associatedtype.XcmRouter){target=\_blank} is a critical component the XCM pallet requires to facilitate sending XCM messages. It defines where messages can be sent and determines the appropriate XCM transport protocol for the operation.
 
-For instance, the Kusama network employs the [`ChildParachainRouter`](https://paritytech.github.io/polkadot-sdk/master/polkadot_runtime_common/xcm_sender/struct.ChildParachainRouter.html){target=\_blank}, which restricts routing to [Downward Message Passing (DMP)](https://wiki.polkadot.network/docs/learn-xcm-transport#dmp-downward-message-passing){target=\_blank} from the relay chain to parachains, ensuring secure and controlled communication.
+For instance, the Kusama network employs the [`ChildParachainRouter`](https://paritytech.github.io/polkadot-sdk/master/polkadot_runtime_common/xcm_sender/struct.ChildParachainRouter.html){target=\_blank}, which restricts routing to [Downward Message Passing (DMP)](https://wiki.polkadot.network/learn/learn-xcm-transport/#dmp-downward-message-passing){target=\_blank} from the relay chain to parachains, ensuring secure and controlled communication.
 
 ```rust
 --8<-- 'https://raw.githubusercontent.com/polkadot-fellows/runtimes/refs/heads/main/relay/kusama/src/xcm_config.rs:122:125'

develop/interoperability/xcm-channels.md

@@ -7,7 +7,7 @@ description: Learn how Polkadot's cross-consensus messaging (XCM) channels conne
 
 ## Introduction
 
-Polkadot is designed to enable interoperability between its connected parachains. At the core of this interoperability is the [Cross-Consensus Message Format (XCM)](https://wiki.polkadot.network/docs/learn-xcm), a standard language that allows parachains to communicate and interact with each other.
+Polkadot is designed to enable interoperability between its connected parachains. At the core of this interoperability is the [Cross-Consensus Message Format (XCM)](/develop/interoperability/intro-to-xcm/){target=\_blank}, a standard language that allows parachains to communicate and interact with each other.
 
 The network-layer protocol responsible for delivering XCM-formatted messages between parachains is the Cross-Chain Message Passing (XCMP) protocol. XCMP maintains messaging queues on the relay chain, serving as a bridge to facilitate cross-chain interactions.
 

develop/interoperability/xcm-config.md

@@ -37,7 +37,7 @@ Each configuration item is explained below, detailing the associated type’s pu
     - `Dispatchable` - indicates it can be executed in the runtime
     - `GetDispatchInfo` - provides weight details, determining how long execution takes
 
-- [**`XcmSender`**](https://paritytech.github.io/polkadot-sdk/master/staging_xcm_executor/trait.Config.html#associatedtype.XcmSender){target=\_blank} - implements the [`SendXcm`](https://paritytech.github.io/polkadot-sdk/master/staging_xcm/v4/trait.SendXcm.html){target=\_blank} trait, specifying how the executor sends XCMs using transport layers (e.g., UMP for relay chains or XCMP for sibling chains). If a runtime lacks certain transport layers, such as [HRMP](https://wiki.polkadot.network/docs/learn-xcm-transport#hrmp-xcmp-lite){target=\_blank} (or [XCMP](https://wiki.polkadot.network/docs/learn-xcm-transport#xcmp-cross-consensus-message-passing-design-summary){target=\_blank})
+- [**`XcmSender`**](https://paritytech.github.io/polkadot-sdk/master/staging_xcm_executor/trait.Config.html#associatedtype.XcmSender){target=\_blank} - implements the [`SendXcm`](https://paritytech.github.io/polkadot-sdk/master/staging_xcm/v4/trait.SendXcm.html){target=\_blank} trait, specifying how the executor sends XCMs using transport layers (e.g., UMP for relay chains or XCMP for sibling chains). If a runtime lacks certain transport layers, such as [HRMP](https://wiki.polkadot.network/learn/learn-xcm-transport/#hrmp-xcmp-lite){target=\_blank} (or [XCMP](https://wiki.polkadot.network/learn/learn-xcm-transport/#xcmp-cross-consensus-message-passing-design-summary){target=\_blank})
     ```rust
     type XcmSender: SendXcm;
     ```
@@ -126,7 +126,7 @@ Each configuration item is explained below, detailing the associated type’s pu
     type PalletInstancesInfo: PalletsInfoAccess;
     ```
  <!-- I think `Holding Register` should be linked to https://wiki.polkadot.network/docs/learn/xcm/reference-glossary#holding-register, but since we will have our own glossary, I’m putting this as a TODO -->
-- [**`MaxAssetsIntoHolding`**](https://paritytech.github.io/polkadot-sdk/master/staging_xcm_executor/trait.Config.html#associatedtype.MaxAssetsIntoHolding){target=\_blank} - limits the number of assets in the [Holding register](https://wiki.polkadot.network/docs/learn/xcm/reference-glossary#holding-register){target=\_blank}. At most, twice this limit can be held under worst-case conditions
+- [**`MaxAssetsIntoHolding`**](https://paritytech.github.io/polkadot-sdk/master/staging_xcm_executor/trait.Config.html#associatedtype.MaxAssetsIntoHolding){target=\_blank} - limits the number of assets in the [Holding register](https://wiki.polkadot.network/learn/learn-xcm/#holding-register){target=\_blank}. At most, twice this limit can be held under worst-case conditions
     ```rust
     type MaxAssetsIntoHolding: Get<u32>;
     ```

develop/networks.md

@@ -271,4 +271,4 @@ Paseo is a decentralised, community run, stable testnet for parachain and dapp d
 
 ## Additional Resources
 
-- [**Polkadot Fellowship runtimes repository**](https://github.com/polkadot-fellows/runtimes){target=\_blank} - find a collection of runtimes for Polkadot, Kusama, and their system-parachains as maintained by the community via the [Polkadot Technical Fellowship](https://wiki.polkadot.network/docs/learn-polkadot-technical-fellowship){target=\_blank}
+- [**Polkadot Fellowship runtimes repository**](https://github.com/polkadot-fellows/runtimes){target=\_blank} - find a collection of runtimes for Polkadot, Kusama, and their system-parachains as maintained by the community via the [Polkadot Technical Fellowship](https://wiki.polkadot.network/learn/learn-polkadot-technical-fellowship/){target=\_blank}

develop/parachains/deployment/index.md

@@ -55,7 +55,7 @@ flowchart TD
 
 - **Acquire coretime** - to build on top of the Polkadot network, users need to acquire coretime (either on-demand or in bulk) to access the computational resources of the relay chain. This allows for the secure validation of parachain blocks through a randomized selection of relay chain validators
 
-If you’re building a standalone blockchain (solochain) that won’t connect to Polkadot as a parachain, you can skip the preceding step, as there’s no need to acquire coretime or implement [Cumulus](https://wiki.polkadot.network/docs/build-pdk#cumulus){target=\_blank}.
+If you’re building a standalone blockchain (solochain) that won’t connect to Polkadot as a parachain, you can skip the preceding step, as there’s no need to acquire coretime or implement [Cumulus](/develop/parachains/#cumulus){target=\_blank}.
 
 - **Launch and monitor** - once everything is configured, you can launch the blockchain, initiating the network with your chain spec and Wasm runtime. Validators or collators will begin producing blocks, and the network will go live. Post-launch, monitoring is vital to ensuring network health—tracking block production, node performance, and overall security
 

develop/parachains/deployment/obtain-coretime.md

@@ -52,7 +52,7 @@ Before obtaining coretime, ensure you have:
 Bulk coretime provides several advantages:
 
 - Monthly allocation of resources
-- Guaranteed block production slots (every 12 seconds, or 6 seconds with [Asynchronous Backing](https://wiki.polkadot.network/docs/learn-async-backing#asynchronous-backing){target=\_blank})
+- Guaranteed block production slots (every 12 seconds, or 6 seconds with [Asynchronous Backing](https://wiki.polkadot.network/learn/learn-async-backing/#asynchronous-backing){target=\_blank})
 - Priority renewal rights
 - Protection against price fluctuations
 - Ability to split and resell unused coretime
@@ -66,7 +66,7 @@ To purchase bulk coretime:
 
 After successfully obtaining coretime, your parachain will automatically start producing blocks at regular intervals.
 
-For current marketplaces and pricing, consult the [Coretime Marketplaces](https://wiki.polkadot.network/docs/learn-guides-coretime-marketplaces){target=\_blank} page on the Polkadot Wiki.
+For current marketplaces and pricing, consult the [Coretime Marketplaces](https://wiki.polkadot.network/learn/learn-guides-coretime-marketplaces/){target=\_blank} page on the Polkadot Wiki.
 
 ### On-demand Coretime
 

develop/parachains/install-polkadot-sdk.md

@@ -95,19 +95,12 @@ To install `openssl` and the Rust toolchain on macOS:
     rustup default stable
     rustup update
     rustup target add wasm32-unknown-unknown
+    rustup component add rust-src
     ```
 
-8. Add the `nightly` release and the `nightly` Wasm targets to your development
-   environment by running the following commands:
+8. [Verify your installation](#verifying-installation)
 
-    ```bash
-    rustup update nightly
-    rustup target add wasm32-unknown-unknown --toolchain nightly
-    ```
-
-9. [Verify your installation](#verifying-installation)
-
-10. Install `cmake` using the following command:
+9. Install `cmake` using the following command:
 
     ```bash
     brew install cmake
@@ -201,16 +194,11 @@ To install the Rust toolchain on Linux:
     ```bash
     rustup default stable
     rustup update
+    rustup target add wasm32-unknown-unknown
+    rustup component add rust-src
     ```
 
-9. Add the `nightly` release and the `nightly` Wasm targets to your development environment by running the following commands:
-
-    ```bash
-    rustup update nightly
-    rustup target add wasm32-unknown-unknown --toolchain nightly
-    ```
-
-10. [Verify your installation](#verifying-installation)
+9.  [Verify your installation](#verifying-installation)
 
 ## Windows (WSL)
 
@@ -237,7 +225,7 @@ To prepare a development environment using WSL:
 
     If you have Microsoft Windows 10, version 2004 (Build 19041 and higher), or Microsoft Windows 11, WSL is available by default and you can continue to the next step.
 
-    If you have an older version of Microsoft Windows installed, see the [WSL manual installation steps for older versions](https://docs.microsoft.com/en-us/windows/wsl/install-manual){target=\_blank}. If you are installing on an older version of Microsoft Windows, you can download and install WLS 2 if your computer has Windows 10, version 1903 or higher
+    If you have an older version of Microsoft Windows installed, see the [WSL manual installation steps for older versions](https://learn.microsoft.com/en-us/windows/wsl/install-manual){target=\_blank}. If you are installing on an older version of Microsoft Windows, you can download and install WLS 2 if your computer has Windows 10, version 1903 or higher
 
 2. Select **Windows PowerShell** or **Command Prompt** from the **Start** menu, right-click, then **Run as administrator**
 
@@ -262,7 +250,7 @@ To prepare a development environment using WSL:
 
     Restarting the computer is required to start the installation of the Linux distribution. It can take a few minutes for the installation to complete after you restart.
 
-    For more information about setting up WSL as a development environment, see the [Set up a WSL development environment](https://docs.microsoft.com/en-us/windows/wsl/setup/environment){target=\_blank} docs
+    For more information about setting up WSL as a development environment, see the [Set up a WSL development environment](https://learn.microsoft.com/en-us/windows/wsl/setup/environment){target=\_blank} docs
 
 ### Install Required Packages and Rust {: #install-required-packages-and-rust-windows }
 
@@ -311,24 +299,18 @@ To install the Rust toolchain on WSL:
     ```bash
     rustup default stable
     rustup update
+    rustup target add wasm32-unknown-unknown
+    rustup component add rust-src
     ```
 
-11. Add the `nightly` version of the toolchain and the `nightly` Wasm target to your development environment by running the following commands:
-
-    ```bash
-    rustup update nightly
-    rustup target add wasm32-unknown-unknown --toolchain nightly
-    ```
-
-12. [Verify your installation](#verifying-installation)
+11. [Verify your installation](#verifying-installation)
 
 ## Verifying Installation
 
 Verify the configuration of your development environment by running the following command:
 
 ```bash
 rustup show
-rustup +nightly show
 ```
 
 The command displays output similar to the following:

develop/parachains/maintenance/runtime-upgrades.md

@@ -9,7 +9,7 @@ description: This page covers how runtime versioning and storage migration suppo
 
 One of the defining features of Polkadot SDK-based blockchains is the ability to perform forkless runtime upgrades. Unlike traditional blockchains, which require hard forks and node coordination for upgrades, Polkadot networks enable seamless updates without network disruption.
 
-Forkless upgrades are achieved through WebAssembly (Wasm) runtimes stored on-chain, which can be securely swapped and upgraded as part of the blockchain's state. By leveraging decentralized consensus, runtime updates can be happen trustlessly, ensuring continuous improvement and evolution without halting operations.
+Forkless upgrades are achieved through WebAssembly (Wasm) runtimes stored on-chain, which can be securely swapped and upgraded as part of the blockchain's state. By leveraging decentralized consensus, runtime updates can happen trustlessly, ensuring continuous improvement and evolution without halting operations.
 
 This guide explains how Polkadot's runtime versioning, Wasm deployment, and storage migrations enable these upgrades, ensuring the blockchain evolves smoothly and securely. You'll also learn how different upgrade processes apply to solo chains and parachains, depending on the network setup.