Node Configuration

Deploying a Brixs node via Docker Compose is the fastest and most reliable way to get started. It guarantees environment consistency across Linux distributions.

Deployment Guide

The `docker-compose.yml` File

Create this file in your server's root directory. It maps ports for both JSON-RPC and internal P2P gossip.

Code

version: '3.8'
services:
  brixs-node:
    image: brixs/node:v2.1.0
    restart: unless-stopped
    ports:
      - "8080:8080" # JSON-RPC HTTP
      - "9000:9000" # P2P Gossip
    volumes:
      - ./brixs-data:/root/.brixs/data
      - ./config.yaml:/root/.brixs/config.yaml

Starting the Daemon

Code

docker-compose up -d

You can monitor the sync status by checking the logs: docker logs -f brixs-node.

Performance Tuning

Phase 1: Engine Initialization

The first phase requires a comprehensive setup of the execution environment. The Brixs Native EVM initializes the state and establishes secure connections with the P2P network. This ensures that when the DPoS Sequencer begins proposing blocks, there are no bottlenecks in transaction ingestion.

Transactions are ordered securely by the Encrypted Mempool to prevent MEV. The Native EVM processes transactions while the ZK-SNARK Prover Engine generates validity proofs. Once processed, the Sequencer commits the block to the Ethereum L1, achieving Rollup Finality and inheriting Ethereum's cryptographic security.