Litentry this week: NFT Pallet display and SubstraTEE development progress

Litentry
Litentry
Aug 2 · 5 min read

✨ The development of the NFT pallet that everyone is eyeing is progressing smoothly!

Litentry’s NFT pallet will facilitate the construction of identity racetracks and DAO governance and will be applied to Litentry’s technical architecture for identity score computing. At present, the back-end of the NFT pallet has the basic functions related to NFT, and we have also built the corresponding API to debug the existing functions.

Overview of the Litentry Github WebApp development

The basic NFT features that have been put into internal testing include:

  • Mint NFT. A simple function of NFT generation and distribution of NFT. The user needs to put in an NFT class (such as CryptoKitties) and the number of NFT to generate, input the address that receives NFT, upload an NFT image file and a name, then one can immediately generate an NFT.
Front-end interface of Mint NFT. In the figure is Step 1: Input the NFT class ID
  • Simple NFT. This function is mainly for the need of airdrop or batch generation of NFT, where users can paste or batch import address and the system will automatically generate Merkle tree roots (learn more about Merkle airdrop). In the development plan, it is planned to support the automatical identification of address for the import of JSON and CSV documents.
Simple NFT front-end interface. The figure shows step 2: Creating the Merkle Tree root
  • Transfer NFT. As the name implies, this function has the ability to move a particular NFT asset to another address. A list of NFT assets will be added to the development plan for users to easily select the NFT instances.
Transfer NFT front-end interface
  • Merge NFT. Users can merge two NFTs to produce a new NFT. Application scenarios could be, for example, two low-level NFT collectible flashcards are merged to generate a higher-level flashcard. More gameplay can be explored by the project side.
Merge NFT’s front-end interface
  • Burn NFT. The project party or user may choose to burn their NFT assets. Similar to burning cryptocurrencies, the main incentive is to maintain the stability of NFT asset prices in the market.
Burn NFT’s front-end interface

At the same time, the Litentry product and development team are also actively investigating issues regarding NFT data storage, Merkel tree data storage for production among other important issues. Current tasks to be tackled for the NFT pallet include defining ticketing, creating the wireframe for back-end collaboration, building the Merkle Tree components, creating the NFT classes and the NFT claiming interface, etc.

🌉 The SubstraTEE sidechain development progress

The principal of the Litentry Account Linker is stored on the worker in the SubstraTEE sidechain. The SubstraTEE framework ensures that the private data in the Account Linker will not be exposed because the data stored in Enclave cannot be read even by the Intel server itself.

At this stage, the main thing Litentry does is technology docking and integrating the SubstraTEE framework with the Litentry mainnet. Progress will be relatively slow at first due to inconsistent dependencies on both sides. The next phase will be deploying and running the networks, porting the Account Linker to SubstraTEE so we can call it when needed.

Currently, the worker running SubstraTEE needs to rent a server with Software Guard Extension (SGX) computing configuration, which is not supported by all Intel computers, so the operation threshold is high. Litentry currently has SGX servers in China, France, and Germany, forming multiple nodes. With the development of Litentry mainnet, we encourage communities to set up their own SGXs to participate in the operation of network nodes of Litentry’s TEE sidechain and we plan to set up reward and punishment mechanisms such as mining.

Testnet: Added deposit function and nonfungibles Traits to NFT pallet

  • Added deposit function in NFT pallet
  • Implemented nonfungibles Trait for NFT pallet
  • Added FMT to parachain and pallets
  • Investigated SubstraTEE compilation issue
  • Fixed SubstraTEE node dependency issue

Litentry App: Created Council and Treasury panels for Dashboard

  • Created Council and Treasury panels for the dashboard
  • Updated Dashboard to latest mockups
  • Implemented NFT Giveaway
  • Added support for creating, storing, and retrieving a MerkleTree
  • Configured automated updates with Dependabot

Misc: Setup Zenhub as our parachain project management tool

  • Upgraded Kusama-registrar and staking-payout job
  • Investigated Rundeck account system
  • Investigated load balancer and VPN
  • Setup Zenhub as parachain project management tool

👋 See y’all next time!

Co-Authored by

About Litentry

Litentry is a Decentralized Identity Aggregator that enables linking user identities across multiple networks. Featuring a DID indexing protocol and a Substrate-built distributed DID validation blockchain, Litentry provides a decentralized, interoperable identity aggregation service that mitigates the difficulty of resolving agnostic DID mechanisms. Litentry provides a secure vehicle through which users manage their identities and dApps obtain real-time DID data of an identity owner across different blockchains.

Stay in touch with us through

Litentry

Cross-chain identity aggregation

Litentry

Litentry is a Decentralized Identity Aggregator that enables linking user identities across multiple networks. Featuring a DID indexing protocol and a Substrate-built distributed DID validation blockchain, Litentry provides a decentralized, interoperable identity aggregation serv

Litentry

Written by

Litentry

Build a user-centric world with blockchain

Litentry

Litentry is a Decentralized Identity Aggregator that enables linking user identities across multiple networks. Featuring a DID indexing protocol and a Substrate-built distributed DID validation blockchain, Litentry provides a decentralized, interoperable identity aggregation serv