Skip to main content

Testnets

Test networks are designed for early-stage application development. Storing assets with real world value on these networks is highly discouraged and minted PKPs may be deleted. All test networks may be deprecated in the future.

Here is an overview of the Lit testnets:

NameLit BlockchainDescriptionMinimum Lit SDK VersionLit SDK Network IdentifierRequires Payment
Datil-devChronicle VesuviusCentralized 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.0datil-dev
CayenneChronicleCentralized 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.0cayenne
ManzanoChronicleDecentralized test network. No persistency guarantees. Mirrors Habanero code and configuration. Payment is enforced.^4.0.0manzano

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.

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 to learn how to migrate to Chronicle Vesuvius.

The minimum version of the Lit SDK that supports datil-dev is 6.1.0, and it will be installed from NPM by default:

npm install @lit-protocol/lit-node-client

There were no breaking changes to the API for v6 of the Lit SDK, so the code you were using for Cayenne should work without issue on Datil-dev. If you do run into issues after migrating to Datil-dev, please reach out to us on our Telegram for support.

To connect to Datil-Dev, please follow the Connecting to a Lit Network guide using datil-dev for the litNetwork property when instantiating an instance of the LitNodeClient.