Skip to main content
Version: v3.x.x

Mainnet

Overview

info

STATE OF THE NETWORK

Lit V0, the Habanero Mainnet, is now live and available for teams building apps in production. Habanero supports ID encrypt, user wallets, and serverless signing.

Main networks should be used by applications that are currently live in production, supporting the storage of live assets. Mainnet keys are persistent and will not be deleted.

You can set your Lit Network in the LitNodeClient config of the Lit SDK, by passing the network name to the litNetwork parameter.

NameDescriptionSupported AlgorithmsSupported FeaturesStatusSDK VersionDevelopment statusContracts
JalapenoCentralized alpha network. Persistent, keys will not be deleted.BLSEncryptionLiveV1, V2Deprecated. Do not build new apps that use this network.n/a
HabaneroDecentralized mainnet. Persistent, keys will not be deleted.BLS, ECDSAEncryption, User Wallets (PKPs), Serverless Signing (Lit Actions)LiveV4+Good to usehabanero

Token Usage

If you'd like to use Habanero, you'll need some 'testLPX' tokens to pay for network fees and gas when minting PKPs. Habanero uses a test token for payments and gas that holds no real world value. You can acquire some tokens from the verified faucet.

Migration

In order to connect to the Habanero mainnet network, you'll need to ensure your application is compatible with the v3 version of the Lit SDK. This means if you were previously building on Jalapeno or Serrano using the v2 SDK, you'll need to update your app to use v3.

Upgrading to the v3 SDK can be done by following the migration guide, or checking out the related blog post on Spark.

If your app currently has users in production (on the v1 or v2 SDK), we recommend upgrading internally while keeping users on the current branch until after Habanero is live and fully functional. Once you've upgraded to v3 and Habanero is stable, you’ll just need to perform the necessary migration tasks dependent on the Lit tooling that you’re using:

  • If you’re using Lit for encryption (AKA decentralized access control): Perform re-encryption with Habanero keys.
  • If you’re building with PKPs (AKA user wallets): Re-mint PKPs on Habanero with the same auth methods.