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
  • BTC Full Node
  • Atomicals Full Node
  • ETH Full Node
  • Map Protocol Full Node (Validator)
  1. Features

BlockChain Full Node 200+

BTC Full Node

We provide support for the HTTP protocol

Link: After you deposit $KING in our dapp

Mainnet port 8333

Testnet port 18333

Json-RPC port 8332 This port is used for the JSON-RPC interface of the BTC full node. It allows users or applications to interact with the node programmatically using HTTP or local procedure calls (RPC). Through this interface, users can send commands to the node, query blockchain data, and perform various operations.

Atomicals Full Node

Mainnet port 8080

Link: After deposit $KING in our dapp

ETH Full Node

For Ethereum (ETH), we offer snap sync nodes. After studying the official documentation, we found that archive nodes do not have an impact on improving RPC speed. Therefore, we use a balanced approach with snap sync to achieve the best balance between performance and functionality.

Link: After deposit $KING in our dapp

Map Protocol Full Node (Validator)

We have staked 1,000,000 MAPO tokens to become a validator node, aiming to provide better node access speed.

Link: After deposit $KING in our dapp

ETC...

In the whitepaper, we will not list all the blockchain technologies. Instead, users can directly find the RPC links that can be used in the DApp.

PreviousWhy KnightNodeNextAbstract Node

Last updated 1 year ago

🍢