Leviatom Docs
  • Leviatom Introduction
    • What is Leviatom
    • What We Do
    • Key Features
  • Technical Design
    • Blockchains
    • Trusted Computing
    • Roles
    • Service Deployment
    • Transaction Processing
  • Testnet
    • Testnet Introduction
Powered by GitBook
On this page
  • Accurate property-based routing
  • Consensus-based programing
  1. Leviatom Introduction

Key Features

Accurate property-based routing

Traditional Internet services and data routing are based on the TCP/IP protocol. Services found by IP addresses and port numbers cannot fully confirm “this service” or “that service”. Service information may be outdated, IP addresses and port numbers may be updated, and services may be offline, making it impossible to obtain the corresponding services. This ultimately leads to poor user experience and lack of service security.

Leviatom has innovatively proposed property-based routing, which provides accurate routing for service addressing. When a user accesses a service, they need to address the service based on its properties (hash, status, trust, etc.) and search for services that meet the properties in the Leviatom network. Among them, the most important attribute is the hash of the service. Based on the original information of the service from zero deployment, Leviatom records the hash of the service in an immutable decentralized ledger, ensuring that the user’s request is accurately delivered to the intended service. By comparing the hash of the response service with the hash of the requested service, it completely eliminates security and user experience issues caused by false responses from other services. At the same time, based on multiple attributes, users can choose services that are highly trusted, stable, and fast in response to provide services.

Accurate routing is an important feature of Leviatom, a basic function of the next-generation network, and an inevitable choice for integrating off-chain computing. Based on accurate routing, it will provide users with more efficient, secure, and convenient services, and lay a safe and efficient foundation for the prosperity of the on-chain ecosystem.

Consensus-based programing

Different services have different requirements for security and efficiency. Financial services and network services require strict security levels to ensure service accuracy and continuity. Start-up businesses need to respond quickly to user needs, constantly adjust product capabilities, and control costs.

For different needs, Leviatom has proposed a leading technical solution in the industry: consensus-based programming. Business providers can specify the number of services participating in the consensus and the standards for achieving consensus according to their needs. Here are two algorithm strategies created based on consensus-based programming:

  1. High-performance algorithm: The access request is processed by a service on a single node. Business personnel can choose to deploy services on high-trust and high-performance nodes. The correctness of the output result is ensured through the node trust value. During the output result process, a single node does not need to compare the output result with other nodes, reducing the impact of network performance and computing performance.

  2. High-consensus algorithm: The access request is processed by services on multiple nodes. Multiple nodes compare the output of the access request, and the comparison process combines the hash of the output content and the trust measurement value of each node to determine the output content and output node. This process is participated by multiple nodes, achieving maximum consensus on the output result and ensuring the correctness of the output result to the greatest extent. In this process, various factors such as network conditions and computing resources will affect the output result delay.

Businesses can create flexible consensus algorithms based on cloud computing cost expenses, network performance requirements, trust requirements, and other conditions.

PreviousWhat We DoNextBlockchains

Last updated 1 year ago