Litho
  • Lithosphere
  • Abstract
  • Design Concept
  • Design Objectives
  • Smart Contracts & Decentralized Finance (DeFi)
  • Positioning
  • Lithosphere Architecture and Technology
  • Myriad Distributed Key Management (MDKM)
  • Threshold signature
  • Litho Coin
  • LAX – Algorithmic Stablecoin
  • Consensus Mechanism
  • Cross-Chain Integration
  • Cross-Chain Transactions
  • Deep Neural Networks (DNN)
  • LEP100 Multi-chain Token Standard
  • Validators
  • Linear-communication BFT Consensus
  • Myriad Distributed Key Management
  • LEP100 Token Standard
  • Why should your DeFi project use the LEP100 Token Standard?
  • LEP100 Token Features
  • Verification Nodes
  • Locked Account Generation Scheme
    • Introduction
    • General Nodes
    • Design Description
    • Scheme Generation
    • Advantages
      • Easy Integration and Efficient Data Storage
      • Smart Contract Token Transaction Anonymity
      • Fully Decentralized without Third-Party Participation
      • Secure and stable
      • One-Time Account System
      • Ring Signature Scheme
      • Cryptography Based Security Guarantee
      • Smart Contracts
        • Contract multi-triggering mechanism Diversity of triggering conditions
        • Enhancements and compatibility
        • Contract enclosed call
        • Contract development
        • Timing and trigger conditions
        • Rapid development and interface
        • To use multiple triggers to realize complex financial functions
  • Community operation plan
  • Project promotion method
  • A movement to Promote Blockchain Technology
  • The Standardization of Blockchain Interfaces Movement
  • Lithosphere Applications
  • Current Lithosphere Features
    • Lithosphere Products
    • Lithosphere Project Governance
    • Funding for the project
  • Roadmap
  • Conclusion
  • Disclaimer
  • Glossary
Powered by GitBook
On this page
  1. Locked Account Generation Scheme

Scheme Generation

The private key is never produced or reconstructed throughout the whole network during the Locked Account creation procedure. The involvement of at least k validators is required to generate the signature of the Locked Account. They compute signature shares independently using the key shares they own and then use signature shares to reconstruct the complete signature. The Signature Scheme for Locked Accounts is as follows:

Calculate the Signature Shares in Step 1 Using key shares, several n Lithosphere Validators compute signature shares of the message.

Step 2: Distribute the signatures.

Each Validator transmits his or her signature share to the others.

Step 3: Reassemble and broadcast the whole signature.

When a Validator gets more than k signature shares, it reconstructs the signature in its entirety and broadcasts it to other Validators:

signature=Construct Sig(signature share1,. ,signature sharek)

Step 4: They produce the Locked Account’s complete signature, which includes the following information: signature sharej=Generate Sig(m,key sharej)

PreviousDesign DescriptionNextAdvantages

Last updated 3 years ago