HeliconNFT
  • HeliconNFT
  • Preface
  • Market background
    • Market background
    • Market of games
    • Lack of liquidity in the NFT markets
  • HeliconNFT
    • HeliconNFT Vision
    • Helicon Ecosystem
      • Agora
        • Master NFTs
        • Regular NFT
        • Helicon Marketplace
        • Yield Aggregator
        • Decentralised Governance
        • Helicon AOS (Game Add-on System)
      • Helicon Drachma Token (HDT)
        • Token distribution
        • Appreciation model
      • Helicon Play
        • Helicon Titan
        • Hgold token
        • Helicon Game Interface
        • SDK
        • Game Partners/Helicon GPs
  • Promotional Campaigns
    • NFT Drops
    • Mystery Box Events
  • Technical Architecture
    • Layered design
    • Anti-quantum
    • MSS/LMS solution
    • BLISS solution
    • Smart Contract
    • Ring Confidential Transaction (RingCT)
    • Zero-knowledge proof
    • Cross-chain
  • Helicon roadmap
  • Conclusion
  • Disclaimer
  • Reference
Powered by GitBook
On this page
  1. Technical Architecture

MSS/LMS solution

The hash-based signature scheme starts with the one-time signature scheme (OTS), which means that each key pair in a signature scheme cannot be used to sign multiple messages. Currently the most effective OTS program is the Winternitz program (WOTS). The core idea of WOTS is to iteratively apply functions to secret inputs, and the number of iterations depends on the information to be signed.

The Merkle signature scheme (MSS) is applicable to any cryptographic hash function and any one-time signature scheme. MSS uses a Merkle tree to connect N = 2H OTS public keys together, where H is the height of the tree. The root of the Merkle tree is used as the public key of the MSS. The algorithm used to calculate the Merkle root is called Tree hash, see Algorithm 8.

In order to generate the signature of the message M, it is necessary to select the key of the next unused OTS public key and generate the OTS signature. The MSS signature includes the OTS signature, the OTS public key and the verification path used to prove the existence of the OTS public key in the Merkle tree. To verify the signature, first check the validity of the OTS signature to the OTS public key, and then verify that the OTS public key is a valid leaf of the Merkle tree with a verification path.

PreviousAnti-quantumNextBLISS solution

Last updated 3 years ago