Litentry Doc
English
Search
K

Rollout Plan

This page describes the launch plan of Litentry parachain

Phase 0 - Launch with Litentry genesis

Following winning a Polkadot parachain slot on Apr 25th , the Litentry parachain was launched on Jun 4th with the genesis wasm. The initial launch will only include the minimum viable functionality to keep the chain running. It means:
  • The parachain is running under the protection of a super-user (sudo pallet).
  • Most of the other pallets are deactivated, including governance, balance transfer and all other feature modules.
  • The users' activities are very limited in this phase.
What users can do
Users will be able to observe block production and finalization via explorer (e.g. polkadot-js endpoint), and perform the read-only RPC queries to the chain state and storage.

Phase 1 - Technical verification & Crowdloan distribution

Since Litentry went live, we keep track of the chain state and verify that everything goes fine, including block authorization and finalization, collator status, extrinsic testing, and runtime upgradability, etc. Most of Litmus features are available on Litentry, and we will make runtime upgrade for new features constantly in the future after Litmus confirm them as fully tested and robust.
After we confirm that the parachain is stable and running as expected, we will start distributing the crowdloan rewards in LIT, with a linearly unlocked, per-block base.
What users can do
Users can start to claim their crowdloan rewards. We will have a tutorial page later to explain how to claim it. Please note that the balance transfer has been activated, which means the crowdloan reward can now be transferred to another account.

Phase 2 - Token migration & XCM

A token migration mechanism with corresponding pallets has been activated, which allows the user to transfer ERC20 LIT tokens to Litentry parachain.
What users can do
Users can optionally migrate their ERC20 LIT tokens to Litentry parachain. A guidance page will be added later to demonstrate how to make such a transfer.
Please note the token migration in this phase is uni-directional: ERC20 -> Litentry. We will expand it to allow the other direction in the near future.
A cross-chain mechanism based on XCM with other parachains will be active. These parachains processing DEX features will make secondary market trading of LIT available.

Phase 3 - Collator Staking

Unlike Litmus, Litentry will have an extended staking mechanism based on Polkadot's Proof-of-Stake model as well as a delegation feature, making it a Delegated Proof of Stake(DPoS) setup.
Collators are initially maintained by Litentry team and users make a delegation request through staking, which allows users to participate in the block reward process.
Please refer toLitentry collator model for more information

Phase 4 - Sudo removal

After we confirm that the previous phases have been successfully carried out, we will start to activate the governance-related pallets in this phase with a subsequent sudo removal. From this point on, Litentry parachain will be fully governed by democracy, all on-chain state transitions that require sudo before will now have to go through a democratic way.
What users can do
When the sudo key has been completely removed from the Litmus parachain, users will be able to observe the activation of governance features, including council information, technical committee, and referendum. LIT token holders can then take part in on-chain governance activities.

Phase 5 - Balance transfer activation

Balance transfer has been enabled in this phase through a democratic runtime upgrade.
What users can do
Users will be able to freely transfer their funds between accounts.
Notice that Balance transfer and XCM are independent two mechanisms. So without balance transfer enabled, users can still use the XCM function freely.

Phase 6 - Feature pallets onboard

More feature pallets will be gradually onboarded in this phase. They are bound up with the Litentry products which widen the LIT token usage scenarios and bring the integrative service experience to the users.
The feature pallets are expected to contain but are not limited to:
What users can do
Users will be able to take part in the various products and services firsthand and discover the diverse LIT token utilities.
Depending on the development progress, some pallets could be experienced earlier than planned, in the form of internal/public testing.