LIT-Protocol · awisniew207 · Jul 22, 2024 · Jul 19, 2024 · Jul 22, 2024 · Jul 22, 2024
diff --git a/docs/connecting-to-a-lit-network/connecting.md b/docs/connecting-to-a-lit-network/connecting.md
@@ -15,23 +15,23 @@ await litNodeClient.connect();
 ## Available Lit Networks
 
 :::warning
-With the release of [Chronicle Yellowstone](./lit-blockchains/chronicle-yellowstone.md), [Chronicle Vesuvius](./lit-blockchains/chronicle-vesuvius), and their Datil networks, the [Chronicle](./lit-blockchains/chronicle) based Lit networks: `habanero`, `manzano`, and `cayenne` are going to be deprecated.
+With the release of [Chronicle Yellowstone](./lit-blockchains/chronicle-yellowstone) and the Datil networks, the [Chronicle](./lit-blockchains/chronicle) based Lit networks: `habanero`, `manzano`, and `cayenne` are going to be deprecated.
 
 If you are currently using these networks, please review the [Migrating to Datil](./migrations/migrating-to-datil) guide to migrate your application and Lit assets to a Datil network.
 :::
 
 ### Mainnets
 
-| Name     | Lit SDK Network Identifier | Doc Page Link | Network is Live           |
-|----------|----------------------------|---------------|---------------------------|
-| Datil    | `datil`                    | n/a           | ❌                         |
-| Habanero | `habanero`                 | n/a           | ⚠️ Going to be deprecated |
+| Name       | Lit SDK Network Identifier | Doc Page Link | Network is Live           |
+|------------|----------------------------|---------------|---------------------------|
+| Datil-prod | `datil-prod`               | n/a           | ❌                        |
+| Habanero   | `habanero`                 | n/a           | ⚠️ Going to be deprecated |
 
 ### Testnets
 
-| Name      | Lit SDK Network Identifier | Doc Page Link                 | Network is Live           |
-|-----------|----------------------------|-------------------------------|---------------------------|
-| Datil     | `datil-test`               | [Link](./testnets#datil-test) | ✅                         |
-| Datil-dev | `datil-dev`                | [Link](./testnets#datil-dev)  | ✅                         |
-| Manzano   | `manzano`                  | n/a                           | ⚠️ Going to be deprecated |
-| Cayenne   | `cayenne`                  | n/a                           | ⚠️ Going to be deprecated |
+| Name       | Lit SDK Network Identifier | Doc Page Link                 | Network is Live           |
+|------------|----------------------------|-------------------------------|---------------------------|
+| Datil-test | `datil-test`               | [Link](./testnets#datil-test) | ✅                        |
+| Datil-dev  | `datil-dev`                | [Link](./testnets#datil-dev)  | ✅                        |
+| Manzano    | `manzano`                  | n/a                           | ⚠️ Going to be deprecated |
+| Cayenne    | `cayenne`                  | n/a                           | ⚠️ Going to be deprecated |
diff --git a/docs/connecting-to-a-lit-network/lit-blockchains/chronicle-vesuvius.md b/docs/connecting-to-a-lit-network/lit-blockchains/chronicle-vesuvius.md
diff --git a/docs/connecting-to-a-lit-network/lit-blockchains/chronicle.md b/docs/connecting-to-a-lit-network/lit-blockchains/chronicle.md
@@ -5,9 +5,9 @@ import AddRollupButton from "@site/src/components/AddRollupButton";
 # Chronicle
 
 :::warning
-With the release of [Chronicle Vesuvius](./chronicle-vesuvius), Chronicle is going to be deprecated, and **should no longer be used.**
+With the release of [Chronicle Yellowstone](./chronicle-yellowstone), Chronicle is going to be deprecated, and **should no longer be used.**
 
-Please check out the [Migrating From Chronicle to Chronicle Vesuvius](./migrations/migrating-to-datil) guide if you need to migrate you application to Chronicle Vesuvius.
+Please check out the [Migrating From Chronicle to Chronicle Yellowstone](../migrating-to-datil) guide if you need to migrate you application to Chronicle Yellowstone.
 :::
 
 Chronicle is Lit Protocol's custom EVM rollup testnet, which enhances the performance and scalability of our programmable decentralized threshold cryptography system.

diff --git a/docs/connecting-to-a-lit-network/migrating-to-datil.md b/docs/connecting-to-a-lit-network/migrating-to-datil.md
@@ -5,38 +5,34 @@ import TabItem from '@theme/TabItem';
 
 Lit is launching three new networks, Datil-dev, Datil-test, and Datil, to improve performance and stability for production users compared to previous Lit networks like Cayenne, Manzano, and Habanero.
 
-The Datil and Datil-test networks use a new rollup blockchain called [Chronicle Yellowstone](./lit-blockchains/chronicle-yellowstone.md), and Datil-dev uses a new rollup blockchain called [Chronicle Vesuvius](./lit-blockchains/chronicle-vesuvius); Both new blockchains replace the [Chronicle](./lit-blockchains/chronicle) blockchain that powered Lit's earlier networks. You will learn how to migrate data between these chains below.
+The Datil-dev and Datil-test networks use a new rollup blockchain called [Chronicle Yellowstone](./lit-blockchains/chronicle-yellowstone.md). These new blockchains replace the [Chronicle](./lit-blockchains/chronicle) blockchain that powered Lit's earlier networks. You will learn how to migrate data between these chains below.
 
 Depending on the existing Lit network you are using, you should migrate to its corresponding Datil network to take advantage of these improvements:
 
 | Currently Available | Requires Payment | Minimum Lit Package Version | Your Current Network | Network to Migrate to | Description                                                  |
 |---------------------|------------------|-----------------------------|----------------------|-----------------------|--------------------------------------------------------------|
-| ❌                   | ✅                | n/a                         | `habanero`           | `datil`               | Decentralized mainnet designed for production use cases      |
-| ✅                   | ✅                | `6.2.0`                     | `manzano`            | `datil-test`          | Decentralized testnet designed for pre-production deployment |
-| ✅                   | ❌                | `6.1.0`                     | `cayenne`            | `datil-dev`           | Centralized testnet designed for early-stage development     |
+| ❌                   | ✅                | n/a                         | `habanero`           | `datil-prod`               | Decentralized mainnet designed for production use cases      |
+| ✅                   | ✅                | `6.2.2`                     | `manzano`            | `datil-test`          | Decentralized testnet designed for pre-production deployment |
+| ✅                   | ❌                | `6.2.2`                     | `cayenne`            | `datil-dev`           | Centralized testnet designed for early-stage development     |
 
-Like their counterparts, `datil` and `datil-test` require developers to pay for usage of the Lit network via [Capacity Credits](../capacity-credits); however, `datil-dev` does not.
+Like their counterparts, `datil-prod` and `datil-test` require developers to pay for usage of the Lit network via [Capacity Credits](../capacity-credits); however, `datil-dev` does not.
 
 ## Breaking Changes and Important Updates
 
 - Chronicle Yellowstone's chain facts are available [here](./lit-blockchains/chronicle-yellowstone.md#connecting-to-chronicle-yellowstone).
-- Chronicle Vesuvius' chain facts are available [here](./lit-blockchains/chronicle-vesuvius.md#connecting-to-chronicle-vesuvius).
-
-Because Datil-dev uses Chronicle Vesuvius, and Datil-test using Chronicle Yellowstone, you will also need to follow the below migration steps when migrating between these networks.
 
 ### New Network, New PKPs
 
-PKPs minted on the existing Lit networks: `cayenne`, `manzano`, and `habanero` exist on the Chronicle blockchain. Because of this, when migrating to the new Datil networks: `datil-dev`, `datil-test`, and `datil`, your PKPs will need to be re-minted on the Chronicle Yellowstone/Vesuvius blockchain. This also means transferring ownership of assets owned by PKPs minted on Chronicle, to the newly minted ones on Chronicle Yellowstone/Vesuvius.
+PKPs minted on the existing Lit networks: `cayenne`, `manzano`, and `habanero` exist on the Chronicle blockchain. Because of this, when migrating to the new Datil networks: `datil-dev`, `datil-test`, and `datil-prod`, your PKPs will need to be re-minted on the Chronicle Yellowstone blockchain. This also means transferring ownership of assets owned by PKPs minted on Chronicle, to the newly minted ones on Chronicle Yellowstone.
 
 :::info
-If you're migrating from `habanero` or `manzano` to `Datil` or `Datil-test`, you will be migrating from Chronicle to Chronicle Yellowstone.
+If you're migrating from `habanero`, `manzano`, or `cayenne` to any of the Datil networks, you will be migrating from Chronicle to Chronicle Yellowstone.
 
-If you're migrating from `cayenne` to `Datil-dev`, you will be migrating from Chronicle to Chronicle Vesuvius.
 :::
 
-To reduce the friction of re-minting PKPs on Chronicle Yellowstone/Vesuvius, we've written a [migration script](https://github.com/LIT-Protocol/developer-guides-code/tree/wyatt/pkp-migration-script/pkp-migration/nodejs) that will take a list of PKP public keys, fetch their configured Auth Methods and Scopes, and mint new PKPs on a target Lit Network, setting the same Auth Methods and Scopes for each PKP.
+To reduce the friction of re-minting PKPs on Chronicle Yellowstone, we've written a [migration script](https://github.com/LIT-Protocol/developer-guides-code/tree/wyatt/pkp-migration-script/pkp-migration/nodejs) that will take a list of PKP public keys, fetch their configured Auth Methods and Scopes, and mint new PKPs on a target Lit Network, setting the same Auth Methods and Scopes for each PKP.
 
-After re-minting PKPs on Chronicle Yellowstone/Vesuvius, your users could use both the old Chronicle based network PKPs and the new Chronicle Yellowstone/Vesuvius PKPs with the same auth methods. However, the corresponding Ethereum address for each PKP will be different. Your users may have things tied to the old PKP Ethereum address, like assets, or Account Abstraction wallets that see that PKP as an authorized signer. So the next step is to migrate these items for your users, or notify them they need to migrate to the new Ethereum address themselves.
+After re-minting PKPs on Chronicle Yellowstone, your users could use both the old Chronicle based network PKPs and the new Chronicle Yellowstone PKPs with the same auth methods. However, the corresponding Ethereum address for each PKP will be different. Your users may have things tied to the old PKP Ethereum address, like assets, or Account Abstraction wallets that see that PKP as an authorized signer. So the next step is to migrate these items for your users, or notify them they need to migrate to the new Ethereum address themselves.
 
 :::caution
 The migration script **will not** handle migration of any assets the existing PKPs own such as tokens. Assets held by existing PKPs will need to be manually transferred to a new PKP's Ethereum address (or some another address of your choosing) using a blockchain transaction.
@@ -61,11 +57,10 @@ For latest on which Datil networks are available to connect to, please refer to
 The only code changes required to make use of the new Datil networks are as follows:
 
 - Upgrade the Lit packages to the latest version that supports Datil
-  - `6.2.0` is the minimum version of the packages that supports `datil-test`
-  - `6.1.0` is the minimum version of the packages that supports `datil-dev`
+  - `6.2.2` is the minimum version of the packages that support `datil-test` and `datil-dev`
 - Specify the Datil network when instantiating Lit node clients from the SDK
   - This is done by specifying the `litNetwork` property when [connecting a Lit client](./connecting) to one of the following Datil networks:
-    - `datil`
+    - `datil-prod`
     - `datil-test`
     - `datil-dev`
 

diff --git a/docs/connecting-to-a-lit-network/testnets.md b/docs/connecting-to-a-lit-network/testnets.md
@@ -9,18 +9,18 @@ Here is an overview of the Lit testnets:
 
 | Name       | Lit Blockchain                                                   | Description                                                                                                                                                                         | Minimum Lit SDK Version | Lit SDK Network Identifier | Requires Payment |
 |------------|------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------------------|------------------|
-| Datil-test | [Chronicle Yellowstone](./lit-blockchains/chronicle-yellowstone) | Centralized testnet designed for pre-production development. No persistency guarantees. Payment is enforced.                                                                        | `^6.2.0`                | `datil-test`               | ✅                |
-| Datil-dev  | [Chronicle Vesuvius](./lit-blockchains/chronicle-vesuvius)       | Centralized testnet designed for early-stage development. Keys are not persistent and will be deleted. This network does not enforce payment and can be used for free, for testing. | `^6.1.0`                | `datil-dev`                | ❌                |
+| Datil-test | [Chronicle Yellowstone](./lit-blockchains/chronicle-yellowstone) | Centralized testnet designed for pre-production development. No persistency guarantees. Payment is enforced.                                                                        | `^6.2.2`                | `datil-test`               | ✅                |
+| Datil-dev  | [Chronicle Yellowstone](./lit-blockchains/chronicle-yellowstone) | Centralized testnet designed for early-stage development. Keys are not persistent and will be deleted. This network does not enforce payment and can be used for free, for testing. | `^6.2.2`                | `datil-dev`                | ❌                |
 | Cayenne    | [Chronicle](./lit-blockchains/chronicle)                         | Centralized testnet designed for early-stage development. Keys are not persistent and will be deleted. This network does not enforce payment and can be used for free, for testing. | `^4.0.0`                | `cayenne`                  | ❌                |
 | Manzano    | [Chronicle](./lit-blockchains/chronicle)                         | Decentralized test network. No persistency guarantees. Mirrors Habanero code and configuration. Payment is enforced.                                                                | `^4.0.0`                | `manzano`                  | ✅                |
 
 ## Datil-test
 
 The Lit network, Datil-test, utilizes the Lit blockchain: Chronicle Yellowstone. It's a centralized testnet designed for pre-production development, and is superseding the Manzano testnet. Like Manzano, usage of the network **does** require payment using [Capacity Credits](../sdk/capacity-credits).
 
-If you are currently on one of the Lit networks that utilize the Chronicle blockchain (i.e. Cayenne, Manzano, and/or Habanero), or are migrating from Datil-dev which uses the Chronicle Vesuvius blockchain, please refer to [this guide](./migrating-to-yellowstone) to learn how to migrate to Chronicle Yellowstone.
+If you are currently on one of the Lit networks that utilize the Chronicle blockchain (i.e. Cayenne, Manzano, and/or Habanero), please refer to [this guide](./migrating-to-datil) to learn how to migrate to Chronicle Yellowstone.
 
-The minimum version of the Lit SDK that supports `datil-test` is `6.2.0`, and the latest SDK version will be installed from NPM by default:
+The minimum version of the Lit SDK that supports `datil-test` is `6.2.2`, and the latest SDK version will be installed from NPM by default:
 
 <Tabs
 defaultValue="npm"
@@ -51,11 +51,11 @@ To connect to Datil-test, please follow the [Connecting to a Lit Network](./conn
 
 ## Datil-dev
 
-The Lit network, Datil-dev, utilizes the Lit blockchain: Chronicle Vesuvius. It's a centralized testnet designed for early-stage development, and is superseding the Cayenne testnet. Like Cayenne, usage of the network does **not** require payment using [Capacity Credits](../sdk/capacity-credits).
+The Lit network, Datil-dev, utilizes the Lit blockchain: Chronicle Yellowstone. It's a centralized testnet designed for early-stage development, and is superseding the Cayenne testnet. Like Cayenne, usage of the network does **not** require payment using [Capacity Credits](../sdk/capacity-credits).
 
-If you are currently on one of the Lit networks that utilize the Chronicle blockchain (i.e. Cayenne, Manzano, and/or Habanero), please refer to [this guide](./migrating-to-datil) to learn how to migrate to Chronicle Vesuvius.
+If you are currently on one of the Lit networks that utilize the Chronicle blockchain (i.e. Cayenne, Manzano, and/or Habanero), please refer to [this guide](./migrating-to-datil) to learn how to migrate to Chronicle Yellowstone.
 
-The minimum version of the Lit SDK that supports `datil-dev` is `6.1.0`, and a latest SDK version will be installed from NPM by default:
+The minimum version of the Lit SDK that supports `datil-dev` is `6.2.2`, and a latest SDK version will be installed from NPM by default:
 
 <Tabs
 defaultValue="npm"