KnightNode Doc
  • INFO
    • 🛂Introduction
    • 📏Node Standard Formulation
    • ❔Why KnightNode
  • Features
    • 🍢BlockChain Full Node 200+
    • 🌏Abstract Node
    • 🚀Launchpad
    • ⛏️Node Mining
  • Business
    • 🏢Model
  • TOKENOMIC
    • 🎇Airdrop
    • 🪙Distribution
  • 🔗LINKS
    • Website
    • Twitter
    • Discord
Powered by GitBook
On this page
  • The implementation of the abstract node consists of two main components
  • Unified RPC
  • Automated Backend RPC Service
  1. Features

Abstract Node

User-unaware Node

The implementation of the abstract node consists of two main components

Unified RPC

In order to streamline the node access process, all blockchain networks are connected through a unified RPC link. This allows for a standardized and consistent way of interacting with different blockchain protocols. Our implementation utilizes our own full node, which acts as a central point of access for all supported blockchains. Through this unified RPC, developers and users can easily fetch relevant data, execute transactions, and access other functionalities of the blockchain network.

For example, you can use a shared RPC link in BTC, ETH, or any other chain, and we will automatically identify the correct network in the backend.

Automated Backend RPC Service

To optimize the performance and reliability of the node, we integrate various RPC services available in the market. This automated backend system automatically selects and connects to the RPC service with the lowest latency and highest stability. By leveraging multiple full nodes operated by different providers, we ensure a more robust and resilient infrastructure for our node. This approach not only enhances the speed of node access but also mitigates any potential downtime or disruptions that may occur with a single service provider.

However, please note that the backend implementation for this part is not our own built full node, but rather a shared node.

PreviousBlockChain Full Node 200+NextLaunchpad

Last updated 1 year ago

🌏