From b30eda688beef914891a85777f6a499b919fec89 Mon Sep 17 00:00:00 2001 From: alt <84208222+a1ttech@users.noreply.github.com> Date: Fri, 19 Jul 2024 15:22:07 -0700 Subject: [PATCH 1/6] Update LearnCode.jsx --- src/components/CardSectionsV3/LearnCode.jsx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/components/CardSectionsV3/LearnCode.jsx b/src/components/CardSectionsV3/LearnCode.jsx index 58fa1ac9..79c990ad 100644 --- a/src/components/CardSectionsV3/LearnCode.jsx +++ b/src/components/CardSectionsV3/LearnCode.jsx @@ -13,9 +13,9 @@ export default function LearnCodeSection({ title, className }) { to="https://github.com/LIT-Protocol/awesome/blob/main/README.md" /> Date: Mon, 22 Jul 2024 14:07:47 -0700 Subject: [PATCH 2/6] Vesuvius -> Yellowstone --- .../connecting-to-a-lit-network/connecting.md | 4 +- .../lit-blockchains/chronicle-vesuvius.md | 54 ------------------- .../lit-blockchains/chronicle-yellowstone.md | 54 +++++++++++++++++++ .../lit-blockchains/chronicle.md | 4 +- ...esuvius.md => migrating-to-yellowstone.md} | 10 ++-- docs/connecting-to-a-lit-network/testnets.md | 6 +-- docs/resources/how-it-works.md | 2 +- sidebars.js | 4 +- ...ius.jsx => AddRollupButtonYellowstone.jsx} | 12 ++--- src/pages/state-of-the-network.md | 2 +- 10 files changed, 76 insertions(+), 76 deletions(-) delete mode 100644 docs/connecting-to-a-lit-network/lit-blockchains/chronicle-vesuvius.md create mode 100644 docs/connecting-to-a-lit-network/lit-blockchains/chronicle-yellowstone.md rename docs/connecting-to-a-lit-network/{migrating-to-vesuvius.md => migrating-to-yellowstone.md} (75%) rename src/components/{AddRollupButtonVesuvius.jsx => AddRollupButtonYellowstone.jsx} (56%) diff --git a/docs/connecting-to-a-lit-network/connecting.md b/docs/connecting-to-a-lit-network/connecting.md index 5593d7c5..fa7823ad 100644 --- a/docs/connecting-to-a-lit-network/connecting.md +++ b/docs/connecting-to-a-lit-network/connecting.md @@ -15,9 +15,9 @@ await litNodeClient.connect(); ## Available Lit Networks :::warning -With the release of [Chronicle Vesuvius](./lit-blockchains/chronicle-vesuvius) and the 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 From Chronicle to Chronicle Vesuvius](./migrations/migrating-to-vesuvius) guide to migrate your application and Lit assets to a Datil network. +If you are currently using these networks, please review the [Migrating From Chronicle to Chronicle Yellowstone](./migrations/migrating-to-yellowstone) guide to migrate your application and Lit assets to a Datil network. ::: ### Mainnets 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 deleted file mode 100644 index 536a9591..00000000 --- a/docs/connecting-to-a-lit-network/lit-blockchains/chronicle-vesuvius.md +++ /dev/null @@ -1,54 +0,0 @@ -import FeedbackComponent from "@site/src/pages/feedback.md"; - -import AddRollupButton from "@site/src/components/AddRollupButtonVesuvius"; - -# Chronicle Vesuvius - -Chronicle Vesuvius is Lit Protocol's custom EVM rollup which is superseding the [Chronicle](./chronicle.md) blockchain, allowing for a more performant and stable backend for Lit's infrastructure. - - - -## About Chronicle Vesuvius - -Chronicle Vesuvius is a custom EVM rollup using [Arbitrum Orbit](https://arbitrum.io/orbit), designed specifically for Lit Protocol. This rollup is the primary platform for coordination, minting PKPs (programmable key pairs), and managing PKP Permissions. Note that PKPs minted on Chronicle Vesuvius can still sign transactions on any chain supported by Lit, including EVM, Cosmos, and Bitcoin. - -## `tstLPX` Test Token - -The `tstLPX` test token serves as the gas for transactions on Chronicle Vesuvius. Please note that this is a test token with no real-world value. Its purpose is exclusively for testing and development on the Lit Protocol platform. - -To obtain the `tstLPX` test token, please use [the faucet](https://chronicle-vesuvius-faucet.getlit.dev/). The `tstLPX` test token will be sent to your wallet address, allowing you to perform transactions on the rollup. - -Keep in mind that the official Lit Protocol token is scheduled to launch sometime in the future. This will be the actual token with real-world utility within the ecosystem. - -## Connecting to Chronicle Vesuvius - -To connect to Chronicle Vesuvius, you can click or manually add the network parameters below: - -:::note -The below and additional chain facts are available [here](https://app.conduit.xyz/published/view/vesuvius-as793xpg5g). -::: - -| Parameter Name | Value | -|--------------------|----------------------------------------------------| -| Chain ID | 2311 | -| Name | Chronicle Vesuvius - Lit Protocol Testnet | -| RPC URL | https://vesuvius-rpc.litprotocol.com/ | -| Block Explorer URL | https://vesuvius-explorer.litprotocol.com/ | -| Currency Symbol | tstLPX | -| Currency Decimals | 18 | - -**Note** You must have the `tstLPX` test token in your wallet when minting a pkp, as it is used to pay the gas cost. - -## Block Explorer - -A block explorer is available for Chronicle Vesuvius, providing valuable insights into the network. You can access it [here](https://explorer-vesuvius-as793xpg5g.t.conduit.xyz). The explorer allows you to track transactions, addresses, and other essential data on the rollup. - -## Special Features - -Chronicle Vesuvius includes BLS 12-381 precompiles, which means you can verify BLS signatures on-chain. This feature is not part of Ethereum yet and is only available on Chronicle Vesuvius. - -## Next Steps - -Now that you've learned about Chronicle Vesuvius, you can write your first Lit Action that uses a PKP to sign! Learn how to do that [here](../../sdk/serverless-signing/conditional-signing). - - diff --git a/docs/connecting-to-a-lit-network/lit-blockchains/chronicle-yellowstone.md b/docs/connecting-to-a-lit-network/lit-blockchains/chronicle-yellowstone.md new file mode 100644 index 00000000..2ce0b2b3 --- /dev/null +++ b/docs/connecting-to-a-lit-network/lit-blockchains/chronicle-yellowstone.md @@ -0,0 +1,54 @@ +import FeedbackComponent from "@site/src/pages/feedback.md"; + +import AddRollupButton from "@site/src/components/AddRollupButtonYellowstone"; + +# Chronicle Yellowstone + +Chronicle Yellowstone is Lit Protocol's custom EVM rollup which is superseding the [Chronicle](./chronicle.md) blockchain, allowing for a more performant and stable backend for Lit's infrastructure. + + + +## About Chronicle Yellowstone + +Chronicle Yellowstone is a custom EVM rollup using [Arbitrum Orbit](https://arbitrum.io/orbit), designed specifically for Lit Protocol. This rollup is the primary platform for coordination, minting PKPs (programmable key pairs), and managing PKP Permissions. Note that PKPs minted on Chronicle Yellowstone can still sign transactions on any chain supported by Lit, including EVM, Cosmos, and Bitcoin. + +## `tstLPX` Test Token + +The `tstLPX` test token serves as the gas for transactions on Chronicle Yellowstone. Please note that this is a test token with no real-world value. Its purpose is exclusively for testing and development on the Lit Protocol platform. + +To obtain the `tstLPX` test token, please use [the faucet](https://chronicle-yellowstone-faucet.getlit.dev/). The `tstLPX` test token will be sent to your wallet address, allowing you to perform transactions on the rollup. + +Keep in mind that the official Lit Protocol token is scheduled to launch sometime in the future. This will be the actual token with real-world utility within the ecosystem. + +## Connecting to Chronicle Yellowstone + +To connect to Chronicle Yellowstone, you can click or manually add the network parameters below: + +:::note +The below and additional chain facts are available [here](https://app.conduit.xyz/published/view/chronicle-yellowstone-testnet-9qgmzfcohk). +::: + +| Parameter Name | Value | +|--------------------|----------------------------------------------------| +| Chain ID | 175188 | +| Name | Chronicle Yellowstone - Lit Protocol Testnet | +| RPC URL | https://yellowstone-rpc.litprotocol.com | +| Block Explorer URL | https://yellowstone-explorer.litprotocol.com | +| Currency Symbol | tstLPX | +| Currency Decimals | 18 | + +**Note** You must have the `tstLPX` test token in your wallet when minting a pkp, as it is used to pay the gas cost. + +## Block Explorer + +A block explorer is available for Chronicle Yellowstone, providing valuable insights into the network. You can access it [here](https://yellowstone-explorer.litprotocol.com/). The explorer allows you to track transactions, addresses, and other essential data on the rollup. + +## Special Features + +Chronicle Yellowstone includes BLS 12-381 precompiles, which means you can verify BLS signatures on-chain. This feature is not part of Ethereum yet and is only available on Chronicle Yellowstone. + +## Next Steps + +Now that you've learned about Chronicle Yellowstone, you can write your first Lit Action that uses a PKP to sign! Learn how to do that [here](../../sdk/serverless-signing/conditional-signing). + + diff --git a/docs/connecting-to-a-lit-network/lit-blockchains/chronicle.md b/docs/connecting-to-a-lit-network/lit-blockchains/chronicle.md index fc8af964..bae26e26 100644 --- 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-vesuvius) guide if you need to migrate you application to Chronicle Vesuvius. +Please check out the [Migrating From Chronicle to Chronicle Yellowstone](./migrations/migrating-to-yellowstone) 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-vesuvius.md b/docs/connecting-to-a-lit-network/migrating-to-yellowstone.md similarity index 75% rename from docs/connecting-to-a-lit-network/migrating-to-vesuvius.md rename to docs/connecting-to-a-lit-network/migrating-to-yellowstone.md index 02c5550b..27e08f10 100644 --- a/docs/connecting-to-a-lit-network/migrating-to-vesuvius.md +++ b/docs/connecting-to-a-lit-network/migrating-to-yellowstone.md @@ -5,7 +5,7 @@ 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 networks use a new rollup blockchain called [Chronicle Vesuvius](./lit-blockchains/chronicle-vesuvius), which replaces 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 networks use a new rollup blockchain called [Chronicle Yellowstone](./lit-blockchains/chronicle-yellowstone), which replaces 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: @@ -19,15 +19,15 @@ Like their counterparts, `datil` and `datil-test` require developers to pay for ## Breaking Changes and Important Updates -Chronicle Vesuvius' chain facts are available [here](../chronicle-vesuvius#connecting-to-chronicle-vesuvius). +Chronicle Yellowstone's chain facts are available [here](../chronicle-yellowstone#connecting-to-chronicle-yellowstone). ### 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 Vesuvius blockchain. This also means transferring ownership of assets owned by PKPs minted on Chronicle, to the newly minted ones on Chronicle 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`, 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. -To reduce the friction of re-minting PKPs on Chronicle 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 Vesuvius, your users could use both the old Chronicle based network PKPs and the new Chronicle 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. diff --git a/docs/connecting-to-a-lit-network/testnets.md b/docs/connecting-to-a-lit-network/testnets.md index 6961fa98..1868bffe 100644 --- a/docs/connecting-to-a-lit-network/testnets.md +++ b/docs/connecting-to-a-lit-network/testnets.md @@ -9,15 +9,15 @@ Here is an overview of the Lit testnets: | Name | Lit Blockchain | Description | Minimum Lit SDK Version | Lit SDK Network Identifier | Requires Payment | |-----------|------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|----------------------------|------------------| -| 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-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.1.0` | `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-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-vesuvius) 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-yellowstone) to learn how to migrate to Chronicle Yellowstone. The minimum version of the Lit SDK that supports `datil-dev` is `6.1.0`, and it will be installed from NPM by default: diff --git a/docs/resources/how-it-works.md b/docs/resources/how-it-works.md index d18c8de1..463f1ba2 100644 --- a/docs/resources/how-it-works.md +++ b/docs/resources/how-it-works.md @@ -87,7 +87,7 @@ The Lit Protocol token, LITKEY, will be used by node operators to meet their sta :::info The LITKEY token is NOT live, and currently a test token (tstLPX) is being used for staking and payment. The official LITKEY token will be released when the v1 network launches later this year. You can subscribe to updates [here](https://spark.litprotocol.com/). -If you're a developer building on Lit, test tokens can be claimed from the [verified faucet](https://chronicle-vesuvius-faucet.getlit.dev/). +If you're a developer building on Lit, test tokens can be claimed from the [verified faucet](https://chronicle-yellowstone-faucet.getlit.dev/). ::: diff --git a/sidebars.js b/sidebars.js index 9f058969..f45b86b7 100644 --- a/sidebars.js +++ b/sidebars.js @@ -99,13 +99,13 @@ const sidebars = { }, items: [ 'connecting-to-a-lit-network/testnets', - 'connecting-to-a-lit-network/migrating-to-vesuvius', + 'connecting-to-a-lit-network/migrating-to-yellowstone', { type: 'category', label: 'Lit Blockchains', collapsed: true, items: [ - 'connecting-to-a-lit-network/lit-blockchains/chronicle-vesuvius', + 'connecting-to-a-lit-network/lit-blockchains/chronicle-yellowstone', 'connecting-to-a-lit-network/lit-blockchains/chronicle', ], }, diff --git a/src/components/AddRollupButtonVesuvius.jsx b/src/components/AddRollupButtonYellowstone.jsx similarity index 56% rename from src/components/AddRollupButtonVesuvius.jsx rename to src/components/AddRollupButtonYellowstone.jsx index fafc5808..33c2ee77 100644 --- a/src/components/AddRollupButtonVesuvius.jsx +++ b/src/components/AddRollupButtonYellowstone.jsx @@ -4,16 +4,16 @@ export default function AddRollupButton() { const addNetwork = () => { const params = [ { - chainId: '0x907', - chainName: 'Chronicle Vesuvius - Lit Protocol Testnet', + chainId: '175188', + chainName: 'Chronicle Yellowstone - Lit Protocol Testnet', nativeCurrency: { - name: 'Lit Protocol - Chronicle Vesuvius Testnet Token (tstLPX)', + name: 'Lit Protocol - Chronicle Yellowstone Testnet Token (tstLPX)', symbol: 'tstLPX', decimals: 18, }, - rpcUrls: ['https://vesuvius-rpc.litprotocol.com'], + rpcUrls: ['https://yellowstone-rpc.litprotocol.com'], blockExplorerUrls: [ - 'https://explorer-vesuvius-as793xpg5g.t.conduit.xyz', + 'https://yellowstone-explorer.litprotocol.com', ], }, ]; @@ -25,6 +25,6 @@ export default function AddRollupButton() { }; return ( - + ); } diff --git a/src/pages/state-of-the-network.md b/src/pages/state-of-the-network.md index f7377cb9..48019021 100644 --- a/src/pages/state-of-the-network.md +++ b/src/pages/state-of-the-network.md @@ -1,3 +1,3 @@ :::info -The [Datil-dev](connecting-to-a-lit-network/testnets#datil-dev) testnet is now live and is superseding the Cayenne testnet. Check out the [docs on migration](connecting-to-a-lit-network/migrating-to-vesuvius) to learn how you can start building on Datil-dev today. +The [Datil-dev](connecting-to-a-lit-network/testnets#datil-dev) testnet is now live and is superseding the Cayenne testnet. Check out the [docs on migration](connecting-to-a-lit-network/migrating-to-yellowstone) to learn how you can start building on Datil-dev today. ::: From 681c4aa6335b30030b14460beb89b051abcc4ab4 Mon Sep 17 00:00:00 2001 From: awisniew207 Date: Mon, 22 Jul 2024 14:24:08 -0700 Subject: [PATCH 3/6] Updated broken links --- docs/connecting-to-a-lit-network/connecting.md | 2 +- docs/connecting-to-a-lit-network/lit-blockchains/chronicle.md | 2 +- docs/connecting-to-a-lit-network/migrating-to-yellowstone.md | 2 +- src/pages/state-of-the-network.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/connecting-to-a-lit-network/connecting.md b/docs/connecting-to-a-lit-network/connecting.md index fa7823ad..40eb1e19 100644 --- a/docs/connecting-to-a-lit-network/connecting.md +++ b/docs/connecting-to-a-lit-network/connecting.md @@ -17,7 +17,7 @@ await litNodeClient.connect(); :::warning 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 From Chronicle to Chronicle Yellowstone](./migrations/migrating-to-yellowstone) guide to migrate your application and Lit assets to a Datil network. +If you are currently using these networks, please review the [Migrating From Chronicle to Chronicle Yellowstone](./migrating-to-yellowstone) guide to migrate your application and Lit assets to a Datil network. ::: ### Mainnets diff --git a/docs/connecting-to-a-lit-network/lit-blockchains/chronicle.md b/docs/connecting-to-a-lit-network/lit-blockchains/chronicle.md index bae26e26..5518fb64 100644 --- a/docs/connecting-to-a-lit-network/lit-blockchains/chronicle.md +++ b/docs/connecting-to-a-lit-network/lit-blockchains/chronicle.md @@ -7,7 +7,7 @@ import AddRollupButton from "@site/src/components/AddRollupButton"; :::warning 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 Yellowstone](./migrations/migrating-to-yellowstone) guide if you need to migrate you application to Chronicle Yellowstone. +Please check out the [Migrating From Chronicle to Chronicle Yellowstone](.././migrating-to-yellowstone) 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-yellowstone.md b/docs/connecting-to-a-lit-network/migrating-to-yellowstone.md index 27e08f10..6f2a494b 100644 --- a/docs/connecting-to-a-lit-network/migrating-to-yellowstone.md +++ b/docs/connecting-to-a-lit-network/migrating-to-yellowstone.md @@ -19,7 +19,7 @@ Like their counterparts, `datil` and `datil-test` require developers to pay for ## Breaking Changes and Important Updates -Chronicle Yellowstone's chain facts are available [here](../chronicle-yellowstone#connecting-to-chronicle-yellowstone). +Chronicle Yellowstone's chain facts are available [here](./lit-blockchains/chronicle-yellowstone#connecting-to-chronicle-yellowstone). ### New Network, New PKPs diff --git a/src/pages/state-of-the-network.md b/src/pages/state-of-the-network.md index 48019021..99f3cc83 100644 --- a/src/pages/state-of-the-network.md +++ b/src/pages/state-of-the-network.md @@ -1,3 +1,3 @@ :::info -The [Datil-dev](connecting-to-a-lit-network/testnets#datil-dev) testnet is now live and is superseding the Cayenne testnet. Check out the [docs on migration](connecting-to-a-lit-network/migrating-to-yellowstone) to learn how you can start building on Datil-dev today. +The [Datil-dev](connecting-to-a-lit-network/testnets#datil-dev) testnet is now live and is superseding the Cayenne testnet. Check out the [docs on migration](../../docs/connecting-to-a-lit-network/migrating-to-yellowstone) to learn how you can start building on Datil-dev today. ::: From 967805a2f95c98d80140c311cf20653bf8af80ef Mon Sep 17 00:00:00 2001 From: awisniew207 Date: Mon, 22 Jul 2024 14:50:21 -0700 Subject: [PATCH 4/6] Changed latest datil dev version --- docs/connecting-to-a-lit-network/migrating-to-yellowstone.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/connecting-to-a-lit-network/migrating-to-yellowstone.md b/docs/connecting-to-a-lit-network/migrating-to-yellowstone.md index 6f2a494b..b7e0fb0b 100644 --- a/docs/connecting-to-a-lit-network/migrating-to-yellowstone.md +++ b/docs/connecting-to-a-lit-network/migrating-to-yellowstone.md @@ -13,7 +13,7 @@ Depending on the existing Lit network you are using, you should migrate to its c |---------------------|------------------|-----------------------------|----------------------|-----------------------|--------------------------------------------------------------| | ❌ | ✅ | n/a | `habanero` | `datil` | Decentralized mainnet designed for production use cases | | ❌ | ✅ | n/a | `manzano` | `datil-test` | Decentralized testnet designed for pre-production deployment | -| ✅ | ❌ | `6.1.0` | `cayenne` | `datil-dev` | Centralized testnet designed for early-stage development | +| ✅ | ❌ | `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. From d320fc0599610b25741c9dcec210fbdc2fcc98cf Mon Sep 17 00:00:00 2001 From: Wyatt Barnes Date: Mon, 22 Jul 2024 12:36:24 -1000 Subject: [PATCH 5/6] Update docs/connecting-to-a-lit-network/migrating-to-datil.md --- docs/connecting-to-a-lit-network/migrating-to-datil.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/connecting-to-a-lit-network/migrating-to-datil.md b/docs/connecting-to-a-lit-network/migrating-to-datil.md index fe19f41a..4e942090 100644 --- a/docs/connecting-to-a-lit-network/migrating-to-datil.md +++ b/docs/connecting-to-a-lit-network/migrating-to-datil.md @@ -5,7 +5,7 @@ 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-dev and Datil-test networks use a new rollup blockchain called [Chronicle Yellowstone](./lit-blockchains/chronicle-yellowstone.md). This new blockchains replaces 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: From 95d5761a495149d3710ee3750151788584d547d8 Mon Sep 17 00:00:00 2001 From: Wyatt Barnes Date: Mon, 22 Jul 2024 12:36:30 -1000 Subject: [PATCH 6/6] Update docs/connecting-to-a-lit-network/migrating-to-datil.md --- docs/connecting-to-a-lit-network/migrating-to-datil.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/connecting-to-a-lit-network/migrating-to-datil.md b/docs/connecting-to-a-lit-network/migrating-to-datil.md index 4e942090..a29ced10 100644 --- a/docs/connecting-to-a-lit-network/migrating-to-datil.md +++ b/docs/connecting-to-a-lit-network/migrating-to-datil.md @@ -57,8 +57,7 @@ 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.2` is the minimum version of the packages that supports `datil-test` - - `6.2.2` 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-prod`