NodeChain EN
  • NodeChain
  • Learn
    • About NodeChain
    • Infrastructure
      • Connector
        • Wrapper APIs
      • Nodes
      • Startup script
    • License
    • Ecosystem
      • Supported APIs
      • Integrations
      • Acknowledgments
  • Develop
    • Quick start
      • Initial setup
      • Using command-line script
        • Commands
    • How-to
      • Run tests locally
      • Lint automatically with hooks
      • Integrate a new Blockchain/API
      • Connect to a public node
    • Wrapper API definition file
    • Contributing
  • Reference
    • API Reference
      • Admin
      • General Endpoints
      • REST Wrapper API
        • Bitcoin Cash
        • Bitcoin
        • Ethereum
          • ERC-20
      • JSON-RPC Wrapper API
        • Bitcoin Cash
        • Bitcoin
        • Ethereum
          • ERC-20
      • Real-Time Wrapper API
        • Bitcoin
        • Ethereum
Powered by GitBook
On this page
  • Private nodes
  • Remote nodes
  1. Learn
  2. Infrastructure

Nodes

PreviousWrapper APIsNextStartup script

Last updated 3 years ago

Private nodes

NodeChain has the ability to initiate nodes on the blockchains it supports. Each node internally exposes its native JSON-RPC API to which the Wrapper APIs will make requests.

Each node is built through Docker-compose, being the node the grouping of several docker-compose services. These services depend on the architecture of each blockchain.

To keep the native component of the project as much as possible, official images are used. In case there is no official image for the service, a Dockerfile will be implemented to download and build the image from an official site.

Dockerfiles can be found at ./packages/<NAME_OF_SERVICE>. In this folder, we can also find the entrypoints for each package.

The docker-composes infrastructure is divided into networks:

  • Regtest: Network focused on local development. Allows full flexibility when interacting with the blockchain.

  • Testnet: Blockchain test network

  • Mainnet: Blockchain main network

The Connector must be started to build any node

Remote nodes

There is a possibility that the administrator wants to connect to a public node through a URL. This is possible due to the architecture of the Connector and the startup script.

Connect to a public node
Supported APIs
Network architecture