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

Layered design

In order to facilitate future development and provide a good development environment for developers all over the world, Helicon adopts a layered design and consists of 5 layers:

• Data layer: This layer contains the basic data units and data structures of Helicon.

• Transport layer: P2P network protocols and algorithms used for connection, data transmission, load balancing and encryption.

• Consensus layer: the consensus algorithm embedded in Helicon.

• Cross-chain layer: Provide cross-chain liquidity for NFT on Helicon.

• Application layer: Configure programs or dAPPs developed by third-party developers to provide developers with SDK and API. Currently, Helicon's application layer includes Genesis Games.

PreviousMystery Box EventsNextAnti-quantum

Last updated 3 years ago