Data Streams: Verifier Address Table + Supported Networks update (#3141)

* update table and feedlist to support accordian streams verifier table

* update stream pages to default collapsed verifier table

* update supported network page to show verifier address table, reflecting all supported networks

* lint fix

* reword

* styling updates

* table pagination update

* refactor, make reusable for any table

* ai-llm-gen

* more styling changes

* more styling changes

* undo extra llm gen

* fix warnings

Author: dev-dist

reports/llms-report.json

@@ -1,5 +1,5 @@
 {
-  "startedAt": "2025-11-05T17:13:26.623Z",
+  "startedAt": "2025-11-07T22:17:19.661Z",
   "siteBase": "https://docs.chain.link",
   "sections": [
     {
@@ -46,9 +46,9 @@
       "section": "data-streams",
       "pagesProcessed": 52,
       "outputPath": "src/content/data-streams/llms-full.txt",
-      "bytes": 468050,
+      "bytes": 467697,
       "prevBytes": 468050,
-      "deltaBytes": 0
+      "deltaBytes": -353
     },
     {
       "section": "dta-technical-standard",
@@ -63,8 +63,8 @@
       "pagesProcessed": 20,
       "outputPath": "src/content/datalink/llms-full.txt",
       "bytes": 136632,
-      "prevBytes": 134572,
-      "deltaBytes": 2060
+      "prevBytes": 136632,
+      "deltaBytes": 0
     },
     {
       "section": "chainlink-functions",
@@ -123,5 +123,5 @@
       "deltaBytes": 0
     }
   ],
-  "finishedAt": "2025-11-05T17:13:29.977Z"
+  "finishedAt": "2025-11-07T22:17:22.917Z"
 }

src/content/data-streams/backed-streams/index.mdx

@@ -11,4 +11,9 @@ isIndex: true
 
 import FeedPage from "@features/feeds/components/FeedPage.astro"
 
-<FeedPage dataFeedType="streamsBacked" initialNetwork="arbitrum" />
+<FeedPage
+  dataFeedType="streamsBacked"
+  initialNetwork="arbitrum"
+  allowNetworkTableExpansion={true}
+  defaultNetworkTableExpanded={false}
+/>

src/content/data-streams/crypto-streams/index.mdx

@@ -11,4 +11,9 @@ isIndex: true
 
 import FeedPage from "@features/feeds/components/FeedPage.astro"
 
-<FeedPage dataFeedType="streamsCrypto" initialNetwork="arbitrum" />
+<FeedPage
+  dataFeedType="streamsCrypto"
+  initialNetwork="arbitrum"
+  allowNetworkTableExpansion={true}
+  defaultNetworkTableExpanded={false}
+/>

src/content/data-streams/exchange-rate-streams/index.mdx

@@ -11,4 +11,9 @@ isIndex: true
 
 import FeedPage from "@features/feeds/components/FeedPage.astro"
 
-<FeedPage dataFeedType="streamsExRate" initialNetwork="arbitrum" />
+<FeedPage
+  dataFeedType="streamsExRate"
+  initialNetwork="arbitrum"
+  allowNetworkTableExpansion={true}
+  defaultNetworkTableExpanded={false}
+/>

src/content/data-streams/llms-full.txt

@@ -114,7 +114,7 @@ Automatic failover handles availability and traffic routing in the following sce
 # Data Streams Backed xStock streams
 Source: https://docs.chain.link/data-streams/backed-streams
 
-<FeedPage dataFeedType="streamsBacked" initialNetwork="arbitrum" />
+<FeedPage dataFeedType="streamsBacked" initialNetwork="arbitrum" allowNetworkTableExpansion={true} defaultNetworkTableExpanded={false} />
 
 ---
 
@@ -578,7 +578,7 @@ In these examples, Liquidity-Weighted Bid and Ask prices, along with the spread
 # Data Streams Crypto streams
 Source: https://docs.chain.link/data-streams/crypto-streams
 
-<FeedPage dataFeedType="streamsCrypto" initialNetwork="arbitrum" />
+<FeedPage dataFeedType="streamsCrypto" initialNetwork="arbitrum" allowNetworkTableExpansion={true} defaultNetworkTableExpanded={false} />
 
 ---
 
@@ -682,7 +682,7 @@ Developers are responsible for understanding and managing all additional risk fa
 # Data Streams Exchange Rate streams
 Source: https://docs.chain.link/data-streams/exchange-rate-streams
 
-<FeedPage dataFeedType="streamsExRate" initialNetwork="arbitrum" />
+<FeedPage dataFeedType="streamsExRate" initialNetwork="arbitrum" allowNetworkTableExpansion={true} defaultNetworkTableExpanded={false} />
 
 ---
 
@@ -822,7 +822,7 @@ For comprehensive guidance on managing risks related to market hours, market gap
 # Data Streams Net Asset Value streams
 Source: https://docs.chain.link/data-streams/nav-streams
 
-<FeedPage dataFeedType="streamsNav" initialNetwork="arbitrum" />
+<FeedPage dataFeedType="streamsNav" initialNetwork="arbitrum" allowNetworkTableExpansion={true} defaultNetworkTableExpanded={false} />
 
 ---
 
@@ -5310,7 +5310,7 @@ Chainlink NAV Data Streams streams adhere to the report schema outlined below.
 # Data Streams Real World Asset streams
 Source: https://docs.chain.link/data-streams/rwa-streams
 
-<FeedPage dataFeedType="streamsRwa" initialNetwork="arbitrum" />
+<FeedPage dataFeedType="streamsRwa" initialNetwork="arbitrum" allowNetworkTableExpansion={true} defaultNetworkTableExpanded={false} />
 
 ---
 
@@ -5366,14 +5366,11 @@ Source: https://docs.chain.link/data-streams/supported-networks
 
 Chainlink Data Streams provides data access directly via API or WebSocket for offchain use cases. It involves [verifying report integrity](/data-streams/tutorials/evm-onchain-report-verification) against onchain verifier proxy contracts.
 
-Data Streams is available on any network listed on the following pages, where you can find the necessary Verifier Proxy addresses:
-
-- [Cryptocurrency Streams](/data-streams/crypto-streams)
-- [Real World Asset (RWA) Streams](/data-streams/rwa-streams)
+The table below lists all networks supported by Data Streams, each with verifier proxy contracts deployed for onchain report verification. All [Data Streams report types](/data-streams/reference/report-schema-overview) share these verifier addresses across supported networks. Click any verifier proxy address to view the contract in the block explorer.
 
 ## Streams Trade implementation (Onchain Lookup)
 
-Streams Trade, the alternative implementation, allows smart contracts to access Data Streams onchain using the [`StreamsLookup`](/data-streams/getting-started) capability integrated with [Chainlink Automation](/chainlink-automation).
+[Streams Trade](streams-trade), the alternative implementation, allows smart contracts to access Data Streams onchain using the [`StreamsLookup`](/data-streams/getting-started) capability integrated with [Chainlink Automation](/chainlink-automation).
 
 Streams Trade is currently available on the following networks:
 
@@ -7704,11 +7701,13 @@ Before you begin, you should have:
 
 To complete this tutorial, you'll need:
 
-- **Rust and Cargo**: Install the latest version using [rustup](https://rustup.rs/). Run rustc --version to verify your installation.
+- **Rust and Cargo**: Install Rust 1.79.0 or later using [rustup](https://rustup.rs/). Run rustc --version to verify your installation.
 
-- **Solana CLI tools**: Install the latest version following the [official guide](https://docs.solana.com/cli/install-solana-cli-tools). Run solana --version to verify your installation.
+- **Solana CLI tools**: Install Solana CLI 2.0 or later following the [official guide](https://docs.solana.com/cli/install-solana-cli-tools). Run solana --version to verify your installation.
 
-- **Anchor Framework**: Follow the [official installation guide](https://www.anchor-lang.com/docs/installation). Run anchor --version to verify your installation.
+- **Anchor Framework**: Install Anchor 0.31.0 or later following the [official installation guide](https://www.anchor-lang.com/docs/installation). Run anchor --version to verify your installation.
+
+  **Important**: Using mismatched Anchor versions between your program and client can cause type incompatibilities and runtime errors.
 
 - **Node.js and npm**: [Install Node.js 20 or later](https://nodejs.org/). Verify your installation with node --version.
 
@@ -7768,11 +7767,9 @@ In your program's manifest file (`programs/example_verify/Cargo.toml`), add the
 
 ```toml
 [dependencies]
-chainlink_solana_data_streams = { git = "https://github.com/smartcontractkit/chainlink-solana", branch = "develop", subdir = "contracts/crates/chainlink-solana-data-streams" }
-data-streams-report = { git = "https://github.com/smartcontractkit/data-streams-sdk.git", subdir = "rust/crates/report" }
-
-# Additional required dependencies
-anchor-lang = "0.29.0"
+anchor-lang = "0.31.0"
+chainlink_solana_data_streams = { git = "https://github.com/smartcontractkit/chainlink-data-streams-solana" }
+chainlink-data-streams-report = "1.0.3"
 ```
 
 #### 4. Write the program
@@ -7788,7 +7785,7 @@ use anchor_lang::solana_program::{
     instruction::Instruction,
 };
 // NOTE: Adjust for your report version
-use data_streams_report::report::v3::ReportDataV3;
+use chainlink_data_streams_report::report::v3::ReportDataV3;
 use chainlink_solana_data_streams::VerifierInstructions;
 
 
@@ -7898,27 +7895,13 @@ Note how the `VerifierInstructions::verify` helper method automatically handles
 
 #### 5. Deploy your program
 
-1. Run the following command to build your program:
+1. Build your program:
 
    ```bash
    anchor build
    ```
 
-   **Note**: If you run into this error, set the `version` field at the top of your `cargo.lock` file to `3`.
-
-   ```bash
-   warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
-   note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
-   note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
-   note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
-   warning: .../example_verify/programs/example_verify/Cargo.toml: unused manifest key: dependencies.data-streams-report.subdir
-   error: failed to parse lock file at: .../example_verify/Cargo.lock
-
-   Caused by:
-   lock file version 4 requires `-Znext-lockfile-bump`
-   ```
-
-2. Deploy your program to a Solana cluster (devnet in this example) using:
+2. Deploy your program to devnet:
 
    ```bash
    anchor deploy
@@ -7965,11 +7948,7 @@ In this section, you'll write a client script to interact with your deployed pro
      anchor.setProvider(provider)
 
      // Initialize your program using the IDL and your program ID
-     const program = new Program<ExampleVerify>(
-       require("../target/idl/example_verify.json"),
-       "<YOUR_PROGRAM_ID>",
-       provider
-     )
+     const program = new Program<ExampleVerify>(require("../target/idl/example_verify.json"), provider)
 
      // Convert the hex string to a Uint8Array
      // This is an example report payload for a crypto stream
@@ -8079,7 +8058,14 @@ In this section, you'll write a client script to interact with your deployed pro
    yarn add snappy
    ```
 
-   `snappy` is a compression library that is used to compress the report data.
+   Also ensure you have the required TypeScript dependencies:
+
+   ```bash
+   yarn add @solana/web3.js
+   yarn add -D ts-node typescript @types/node
+   ```
+
+   **Note**: `snappy` is a compression library used to compress the report data before sending it to the verifier.
 
 4. Execute the test script to interact with your program:
 
@@ -8119,7 +8105,7 @@ In this section, you'll write a client script to interact with your deployed pro
 
 #### Program Derived Addresses (PDAs)
 
-The verification process relies on two important PDAs that are handled automatically by the [Chainlink Data Streams Solana SDK](https://github.com/smartcontractkit/chainlink-solana/tree/develop/contracts/crates/chainlink-solana-data-streams):
+The verification process relies on two important PDAs that are handled automatically by the [Chainlink Data Streams Solana SDK](https://github.com/smartcontractkit/chainlink-data-streams-solana):
 
 - **Verifier config account PDA**:
   - Derived using the verifier program ID as a seed
@@ -8158,13 +8144,13 @@ When working with different versions of [Data Stream reports](/data-streams/refe
    - For v3 schema (as used in this example):
 
      ```rust
-     use data_streams_report::report::v3::ReportDataV3;
+     use chainlink_data_streams_report::report::v3::ReportDataV3;
      ```
 
    - For v8 schema:
 
      ```rust
-     use data_streams_report::report::v8::ReportDataV8;
+     use chainlink_data_streams_report::report::v8::ReportDataV8;
      ```
 
 2. **Update the decode function to use the correct schema version.** Examples:

src/content/data-streams/nav-streams/index.mdx

@@ -11,4 +11,9 @@ isIndex: true
 
 import FeedPage from "@features/feeds/components/FeedPage.astro"
 
-<FeedPage dataFeedType="streamsNav" initialNetwork="arbitrum" />
+<FeedPage
+  dataFeedType="streamsNav"
+  initialNetwork="arbitrum"
+  allowNetworkTableExpansion={true}
+  defaultNetworkTableExpanded={false}
+/>

src/content/data-streams/rwa-streams/index.mdx

@@ -11,4 +11,9 @@ isIndex: true
 
 import FeedPage from "@features/feeds/components/FeedPage.astro"
 
-<FeedPage dataFeedType="streamsRwa" initialNetwork="arbitrum" />
+<FeedPage
+  dataFeedType="streamsRwa"
+  initialNetwork="arbitrum"
+  allowNetworkTableExpansion={true}
+  defaultNetworkTableExpanded={false}
+/>

src/content/data-streams/supported-networks.mdx

@@ -8,19 +8,22 @@ metadata:
 ---
 
 import DataStreams from "@features/data-streams/common/DataStreams.astro"
+import { StreamsNetworkAddressesTable } from "@features/feeds/components/Tables"
+import SectionWrapper from "~/components/SectionWrapper/SectionWrapper.tsx"
 
 <DataStreams section="dsNotes" />
 
 Chainlink Data Streams provides data access directly via API or WebSocket for offchain use cases. It involves [verifying report integrity](/data-streams/tutorials/evm-onchain-report-verification) against onchain verifier proxy contracts.
 
-Data Streams is available on any network listed on the following pages, where you can find the necessary Verifier Proxy addresses:
+The table below lists all networks supported by Data Streams, each with verifier proxy contracts deployed for onchain report verification. All [Data Streams report types](/data-streams/reference/report-schema-overview) share these verifier addresses across supported networks. Click any verifier proxy address to view the contract in the block explorer.
 
-- [Cryptocurrency Streams](/data-streams/crypto-streams)
-- [Real World Asset (RWA) Streams](/data-streams/rwa-streams)
+<SectionWrapper title="Streams Verifier Network Addresses" depth={2} client:idle>
+  <StreamsNetworkAddressesTable client:idle allowExpansion={false} />
+</SectionWrapper>
 
 ## Streams Trade implementation (Onchain Lookup)
 
-Streams Trade, the alternative implementation, allows smart contracts to access Data Streams onchain using the [`StreamsLookup`](/data-streams/getting-started) capability integrated with [Chainlink Automation](/chainlink-automation).
+[Streams Trade](streams-trade), the alternative implementation, allows smart contracts to access Data Streams onchain using the [`StreamsLookup`](/data-streams/getting-started) capability integrated with [Chainlink Automation](/chainlink-automation).
 
 Streams Trade is currently available on the following networks:
 

src/features/feeds/components/ExpandableTableWrapper.tsx

@@ -0,0 +1,91 @@
+/** @jsxImportSource preact */
+
+/**
+ * ExpandableTableWrapper - Internal component for making tables collapsible
+ *
+ * DEFAULT BEHAVIOR: Content is always visible with no header (allowExpansion=false)
+ *
+ * INTERNAL USAGE:
+ * <ExpandableTableWrapper
+ *   allowExpansion={true}
+ *   defaultExpanded={false}
+ *   title="Table Title"
+ *   description="Expand to view contents"
+ * >
+ *   {tableContent}
+ * </ExpandableTableWrapper>
+ */
+import { useState } from "preact/hooks"
+import { clsx } from "~/lib/clsx/clsx.ts"
+import tableStyles from "./Tables.module.css"
+
+interface ExpandableTableWrapperProps {
+  title?: string
+  description?: string
+  allowExpansion?: boolean
+  defaultExpanded?: boolean
+  scrollable?: boolean
+  children: preact.ComponentChildren
+}
+
+export const ExpandableTableWrapper = ({
+  title,
+  description,
+  allowExpansion = false,
+  defaultExpanded = true,
+  scrollable = false,
+  children,
+}: ExpandableTableWrapperProps) => {
+  const [isExpanded, setIsExpanded] = useState(defaultExpanded)
+
+  // If expansion is not allowed, still wrap content but without the header
+  if (!allowExpansion) {
+    return <div className={clsx(tableStyles.tableContainer, scrollable && tableStyles.scrollableTable)}>{children}</div>
+  }
+
+  const handleToggle = () => {
+    setIsExpanded(!isExpanded)
+  }
+
+  return (
+    <div
+      className={clsx(tableStyles.expandableWrapper, !isExpanded && tableStyles.expandableWrapperCollapsed)}
+      onClick={(e) => {
+        // If expanded and clicking anywhere in the wrapper (not inside interactive elements)
+        if (isExpanded && e.target === e.currentTarget) {
+          handleToggle()
+        }
+      }}
+    >
+      <div
+        className={tableStyles.expandableHeader}
+        onClick={handleToggle}
+        role="button"
+        tabIndex={0}
+        onKeyDown={(e) => {
+          if (e.key === "Enter" || e.key === " ") {
+            e.preventDefault()
+            setIsExpanded(!isExpanded)
+          }
+          if (e.key === "Escape" && isExpanded) {
+            setIsExpanded(false)
+          }
+        }}
+      >
+        <div className={tableStyles.expandableHeaderContent}>
+          {title && <h2>{title}</h2>}
+          {!isExpanded && description && (
+            <p className={tableStyles.expandableDescription}>
+              <em>{description}</em>
+            </p>
+          )}
+        </div>
+        <div className={clsx(tableStyles.expandableArrow, isExpanded && tableStyles.expandableArrowExpanded)} />
+      </div>
+
+      {isExpanded && (
+        <div className={clsx(tableStyles.tableContainer, scrollable && tableStyles.scrollableTable)}>{children}</div>
+      )}
+    </div>
+  )
+}