Demos Network Specifications
  • Introduction
    • What is Demos Network
    • Demos Network Architecture
  • FAQ
  • Cookbook
    • Project setup
      • Run the project (MacOS)
      • Run the project (Windows)
        • WSL 2 Setup on Windows (10 and 11 only)
        • Issue Troubleshooting
      • Run the project (Ubuntu)
  • SDK
    • Getting Started
    • WebSDK
      • Authentication
        • FIDO2 Passkeys
          • Under the Hood: FIDO2 Passkeys
      • NodeCalls
      • Transactions
        • Creating a transaction
        • Signing a transaction
        • Broadcasting a transaction
      • L2PS SDK
        • The l2ps module
        • Interacting with the L2PS
        • L2PS Messaging System
      • Instant Messaging
        • What is the Instant Messaging Protocol?
        • Architecture Overview
        • Encryption
        • Quickstart
        • Message Types
        • API Reference
        • FAQ
    • Cross Chain
      • General layout of the XM SDKs
      • EVM
      • BTC
      • Solana
      • MultiversX (EGLD)
      • NEAR
      • IBC
      • TON
      • XRPL
      • The XMScript
      • Identities
    • Demoswork
    • Cookbook
      • Demoswork
        • Creating work steps
        • Conditional Operation
        • Base Operation
        • Signing and broadcasting
      • Transactions
        • Crosschain Transaction
        • Native Transactions
      • SWAP
        • Crosschain SWAP
    • Web2
      • Quick Start
      • DAHR API Reference
        • Types
      • Making Requests
      • Identities
        • Twitter
        • GitHub
    • API Reference
    • Bridges
      • Rubic Bridge Test
    • Post Quantum Cryptography
  • Backend
    • Internal Mechanisms
      • Network Time Synchronization
      • Cross Context Identities
    • Global Change Registry
      • GCR Structure
      • How is GCR Synced?
    • Consensus Mechanism
      • Unparalleled Scalability
      • Decentralization in PoR-BFT
      • Enhanced Security
      • Comparative Advantage
      • Addressing Potential Criticisms
      • Conclusion
    • Communications Stack
    • L2PS (Subnet) Framework
      • How are L2PS transactions handled?
    • Miscellaneous
      • Browsing the Postgres DB via psql
    • Bridges
      • Rubic Bridge
    • Developers Testbed
      • Setting up the environment
      • Setting up the repository
      • Installing dependencies
      • Node Configuration
      • Running the node
  • Frontend
    • Demos Providers Discovery Mechanism
Powered by GitBook
On this page
  1. Backend
  2. Developers Testbed

Node Configuration

Environment

Demos nodes use a .env file and a few additional configuration files to provide a customizable and replicable setup. For convenience, a precompiled .env file is already included.

In most cases, you won't need to edit it — just double-check that the listed ports are free on your system. Besides the ones listed, Demos nodes also launch a Postgres Docker container that listens by default on port 5332 (you'll see how to change this in the next chapter).

Note: You don't need to configure the Twitter and GitHub sections of the .env yet, even if they are present depending on the branch.


Keys

To generate your initial keypair, simply run:

./run

The node will crash due to a missing peerlist (expected at this stage), but it will create a file named like publickey_1234567890 inside your node directory. Inside that file, you'll find your public key.


Peerlist

Demos nodes use a demos_peerlist.json file to define peers. First, create it by copying the example file:

cp demos_peerlist.example.json demos_peerlist.json

Then open it with your favorite text editor.

  • Solo mode (local testing): Replace the identity key with your generated public key.

  • Connecting to other nodes: Add lines in the following format:

    "1234567890...": "http://url:port"

Replace 1234567890... with the actual public key of the peer and http://url:port with its URL.

PreviousInstalling dependenciesNextRunning the node

Last updated 1 month ago