Update script name

Author: raymondkfcheung

…ity/multi-hop-with-set-topic-result.html …reserve-asset-with-set-topic-result.html.snippets/code/tutorials/interoperability/xcm-observability/multi-hop-with-set-topic-result.html renamed to .snippets/code/tutorials/interoperability/xcm-observability/deposit-reserve-asset-with-set-topic-result.html .snippets/code/tutorials/interoperability/xcm-observability/multi-hop-with-set-topic-result.html renamed to .snippets/code/tutorials/interoperability/xcm-observability/deposit-reserve-asset-with-set-topic-result.html

@@ -28208,7 +28208,7 @@ In complex XCM flows, such as multi-hop transfers that span multiple parachains,
 - **Topic assignment**: Manually set via `SetTopic` instruction
 - **Goal**: Transfer DOT and trace the XCM using the manually assigned `message_id`
 
-Create a new script, `multi-hop-with-set-topic.ts`
+Create a new script, `deposit-reserve-asset-with-set-topic.ts`
 
 ```ts
 import {Binary, createClient, Enum} from "polkadot-api";
@@ -28441,7 +28441,7 @@ main().catch(console.error);
 Run it locally:
 
 ```bash
-npx tsx multi-hop-with-set-topic.ts
+npx tsx deposit-reserve-asset-with-set-topic.ts
 ```
 
 #### Forwarded XCM (Destination Chain: Hydration)
@@ -40501,7 +40501,43 @@ Let's start by setting up Hardhat for your Storage contract project:
 6. Configure Hardhat by updating the `hardhat.config.js` file:
 
     ```javascript title="hardhat.config.js"
-    Error fetching snippet from https://raw.githubusercontent.com/polkadot-developers/polkavm-hardhat-examples/refs/tags/v0.0.7/storage-hardhat/hardhat.config.js
+    require("@nomicfoundation/hardhat-toolbox");
+
+require("@parity/hardhat-polkadot");
+
+const { vars } = require("hardhat/config");
+
+/** @type import('hardhat/config').HardhatUserConfig */
+module.exports = {
+  solidity: "0.8.28",
+  resolc: {
+    version: "1.5.2",
+    compilerSource: "npm",
+  },
+  networks: {
+    hardhat: {
+      polkavm: true,
+      nodeConfig: {
+        nodeBinaryPath: 'INSERT_PATH_TO_SUBSTRATE_NODE',
+        rpcPort: 8000,
+        dev: true,
+      },
+      adapterConfig: {
+        adapterBinaryPath: 'INSERT_PATH_TO_ETH_RPC_ADAPTER',
+        dev: true,
+      },
+    },
+    localNode: {
+      polkavm: true,
+      url: `http://127.0.0.1:8545`,
+    },
+    passetHub: {
+      polkavm: true,
+      url: 'https://testnet-passet-hub-eth-rpc.polkadot.io',
+      accounts: [vars.get("PRIVATE_KEY")],
+    },
+  },
+};
     ```
 
     Ensure that `INSERT_PATH_TO_SUBSTRATE_NODE` and `INSERT_PATH_TO_ETH_RPC_ADAPTER` are replaced with the proper paths to the compiled binaries. 
@@ -40531,7 +40567,27 @@ Let's start by setting up Hardhat for your Storage contract project:
 1. Create a new folder called `contracts` and create a `Storage.sol` file. Add the contract code from the previous tutorial:
 
     ```solidity title="Storage.sol"
-    Error fetching snippet from https://raw.githubusercontent.com/polkadot-developers/polkavm-hardhat-examples/refs/tags/v0.0.7/storage-hardhat/contracts/Storage.sol
+    // SPDX-License-Identifier: MIT
+pragma solidity ^0.8.28;
+
+contract Storage {
+    // State variable to store our number
+    uint256 private number;
+
+    // Event to notify when the number changes
+    event NumberChanged(uint256 newNumber);
+
+    // Function to store a new number
+    function store(uint256 newNumber) public {
+        number = newNumber;
+        emit NumberChanged(newNumber);
+    }
+
+    // Function to retrieve the stored number
+    function retrieve() public view returns (uint256) {
+        return number;
+    }
+}
     ```
 
 2. Compile the contract:
@@ -40557,9 +40613,28 @@ Testing is a critical part of smart contract development. Hardhat makes it easy
 1. Create a folder for testing called `test`. Inside that directory, create a file named `Storage.js` and add the following code:
 
     ```javascript title="Storage.js" 
-    Error fetching snippet from https://raw.githubusercontent.com/polkadot-developers/polkavm-hardhat-examples/refs/tags/v0.0.7/storage-hardhat/test/Storage.js
+    const { expect } = require('chai');
+const { ethers } = require('hardhat');
+
+describe('Storage', function () {
+  let storage;
+  let owner;
+  let addr1;
+
+  beforeEach(async function () {
+    // Get signers
+    [owner, addr1] = await ethers.getSigners();
+
+    // Deploy the Storage contract
+    const Storage = await ethers.getContractFactory('Storage');
+    storage = await Storage.deploy();
+    await storage.waitForDeployment();
+  });
+
+  describe('Basic functionality', function () {
         // Add your logic here
-    Error fetching snippet from https://raw.githubusercontent.com/polkadot-developers/polkavm-hardhat-examples/refs/tags/v0.0.7/storage-hardhat/test/Storage.js
+    });
+});
     ```
 
     The `beforeEach` hook ensures stateless contract execution by redeploying a fresh instance of the Storage contract before each test case. This approach guarantees that each test starts with a clean and independent contract state by using `ethers.getSigners()` to obtain test accounts and `ethers.getContractFactory('Storage').deploy()` to create a new contract instance.
@@ -40569,7 +40644,9 @@ Testing is a critical part of smart contract development. Hardhat makes it easy
     a. **Initial state verification** - ensures that the contract starts with a default value of zero, which is a fundamental expectation for the `Storage.sol` contract
 
     ```javascript title="Storage.js"
-    Error fetching snippet from https://raw.githubusercontent.com/polkadot-developers/polkavm-hardhat-examples/refs/tags/v0.0.7/storage-hardhat/test/Storage.js
+    it('Should return 0 initially', async function () {
+      expect(await storage.retrieve()).to.equal(0);
+    });
     ```
 
     Explanation:
@@ -40581,7 +40658,13 @@ Testing is a critical part of smart contract development. Hardhat makes it easy
     b. **Value storage test** - validate the core functionality of storing and retrieving a value in the contract
 
     ```javascript title="Storage.js"
-    Error fetching snippet from https://raw.githubusercontent.com/polkadot-developers/polkavm-hardhat-examples/refs/tags/v0.0.7/storage-hardhat/test/Storage.js
+    it('Should update when store is called', async function () {
+      const testValue = 42;
+      // Store a value
+      await storage.store(testValue);
+      // Check if the value was updated
+      expect(await storage.retrieve()).to.equal(testValue);
+    });
     ```
 
     Explanation:
@@ -40593,7 +40676,13 @@ Testing is a critical part of smart contract development. Hardhat makes it easy
     c. **Event emission verification** - confirm that the contract emits the correct event when storing a value, which is crucial for off-chain tracking
 
     ```javascript title="Storage.js"
-    Error fetching snippet from https://raw.githubusercontent.com/polkadot-developers/polkavm-hardhat-examples/refs/tags/v0.0.7/storage-hardhat/test/Storage.js
+    it('Should emit an event when storing a value', async function () {
+      const testValue = 100;
+      // Check if the NumberChanged event is emitted with the correct value
+      await expect(storage.store(testValue))
+        .to.emit(storage, 'NumberChanged')
+        .withArgs(testValue);
+    });
     ```
 
     Explanation:
@@ -40605,7 +40694,14 @@ Testing is a critical part of smart contract development. Hardhat makes it easy
     d. **Sequential value storage test** - check the contract's ability to store multiple values sequentially and maintain the most recent value
 
     ```javascript title="Storage.js"
-    Error fetching snippet from https://raw.githubusercontent.com/polkadot-developers/polkavm-hardhat-examples/refs/tags/v0.0.7/storage-hardhat/test/Storage.js
+    it('Should allow storing sequentially increasing values', async function () {
+      const values = [10, 20, 30, 40];
+
+      for (const value of values) {
+        await storage.store(value);
+        expect(await storage.retrieve()).to.equal(value);
+      }
+    });
     ```
 
     Explanation:
@@ -40618,7 +40714,55 @@ Testing is a critical part of smart contract development. Hardhat makes it easy
 
     ???--- code "View complete script"
         ```javascript title="Storage.js"
-        Error fetching snippet from https://raw.githubusercontent.com/polkadot-developers/polkavm-hardhat-examples/refs/tags/v0.0.7/storage-hardhat/test/Storage.js
+        const { expect } = require('chai');
+const { ethers } = require('hardhat');
+
+describe('Storage', function () {
+  let storage;
+  let owner;
+  let addr1;
+
+  beforeEach(async function () {
+    // Get signers
+    [owner, addr1] = await ethers.getSigners();
+
+    // Deploy the Storage contract
+    const Storage = await ethers.getContractFactory('Storage');
+    storage = await Storage.deploy();
+    await storage.waitForDeployment();
+  });
+
+  describe('Basic functionality', function () {
+    it('Should return 0 initially', async function () {
+      expect(await storage.retrieve()).to.equal(0);
+    });
+
+    it('Should update when store is called', async function () {
+      const testValue = 42;
+      // Store a value
+      await storage.store(testValue);
+      // Check if the value was updated
+      expect(await storage.retrieve()).to.equal(testValue);
+    });
+
+    it('Should emit an event when storing a value', async function () {
+      const testValue = 100;
+      // Check if the NumberChanged event is emitted with the correct value
+      await expect(storage.store(testValue))
+        .to.emit(storage, 'NumberChanged')
+        .withArgs(testValue);
+    });
+
+    it('Should allow storing sequentially increasing values', async function () {
+      const values = [10, 20, 30, 40];
+
+      for (const value of values) {
+        await storage.store(value);
+        expect(await storage.retrieve()).to.equal(value);
+      }
+    });
+  });
+});
         ```
 
 2. Run the tests:
@@ -40647,7 +40791,13 @@ Testing is a critical part of smart contract development. Hardhat makes it easy
 1. Create a new folder called`ignition/modules`. Add a new file named `StorageModule.js` with the following logic:
 
     ```javascript title="StorageModule.js"
-    Error fetching snippet from https://raw.githubusercontent.com/polkadot-developers/polkavm-hardhat-examples/refs/tags/v0.0.7/storage-hardhat/ignition/modules/StorageModule.js
+    const { buildModule } = require('@nomicfoundation/hardhat-ignition/modules');
+
+module.exports = buildModule('StorageModule', (m) => {
+  const storage = m.contract('Storage');
+
+  return { storage };
+});
     ```
 
 2. Deploy to the local network:
@@ -40719,7 +40869,40 @@ To interact with your deployed contract:
 1. Create a new folder named `scripts` and add the `interact.js` with the following content:
 
     ```javascript title="interact.js"
-    Error fetching snippet from https://raw.githubusercontent.com/polkadot-developers/polkavm-hardhat-examples/refs/tags/v0.0.7/storage-hardhat/scripts/interact.js
+    const hre = require('hardhat');
+
+async function main() {
+  // Replace with your deployed contract address
+  const contractAddress = 'INSERT_DEPLOYED_CONTRACT_ADDRESS';
+
+  // Get the contract instance
+  const Storage = await hre.ethers.getContractFactory('Storage');
+  const storage = await Storage.attach(contractAddress);
+
+  // Get current value
+  const currentValue = await storage.retrieve();
+  console.log('Current stored value:', currentValue.toString());
+
+  // Store a new value
+  const newValue = 42;
+  console.log(`Storing new value: ${newValue}...`);
+  const tx = await storage.store(newValue);
+
+  // Wait for transaction to be mined
+  await tx.wait();
+  console.log('Transaction confirmed');
+
+  // Get updated value
+  const updatedValue = await storage.retrieve();
+  console.log('Updated stored value:', updatedValue.toString());
+}
+
+main()
+  .then(() => process.exit(0))
+  .catch((error) => {
+    console.error(error);
+    process.exit(1);
+  });
     ```
 
     Ensure that `INSERT_DEPLOYED_CONTRACT_ADDRESS` is replaced with the value obtained in the previous step.

…bservability/multi-hop-with-set-topic.ts …/deposit-reserve-asset-with-set-topic.ts.snippets/code/tutorials/interoperability/xcm-observability/multi-hop-with-set-topic.ts renamed to .snippets/code/tutorials/interoperability/xcm-observability/deposit-reserve-asset-with-set-topic.ts .snippets/code/tutorials/interoperability/xcm-observability/multi-hop-with-set-topic.ts renamed to .snippets/code/tutorials/interoperability/xcm-observability/deposit-reserve-asset-with-set-topic.ts

@@ -180,16 +180,16 @@ In complex XCM flows, such as multi-hop transfers that span multiple parachains,
 - **Topic assignment**: Manually set via `SetTopic` instruction
 - **Goal**: Transfer DOT and trace the XCM using the manually assigned `message_id`
 
-Create a new script, `multi-hop-with-set-topic.ts`
+Create a new script, `deposit-reserve-asset-with-set-topic.ts`
 
 ```ts
---8<-- 'code/tutorials/interoperability/xcm-observability/multi-hop-with-set-topic.ts'
+--8<-- 'code/tutorials/interoperability/xcm-observability/deposit-reserve-asset-with-set-topic.ts'
 ```
 
 Run it locally:
 
 ```bash
-npx tsx multi-hop-with-set-topic.ts
+npx tsx deposit-reserve-asset-with-set-topic.ts
 ```
 
 #### Forwarded XCM (Destination Chain: Hydration)
@@ -200,7 +200,7 @@ During execution, the runtime includes a `SetTopic` instruction with the customi
 
 #### Example: Message Trace Output
 
---8<-- 'code/tutorials/interoperability/xcm-observability/multi-hop-with-set-topic-result.html'
+--8<-- 'code/tutorials/interoperability/xcm-observability/deposit-reserve-asset-with-set-topic-result.html'
 
 ## Workaround for Older Runtimes