Network Topology
The Brixs Network utilizes a multi-tiered architecture to maximize performance, ensuring that consensus nodes are not bogged down by read requests from decentralized applications.
Node Roles Detailed
Validator Nodes
High-performance servers that participate in consensus. Require significant BRX staking.
Full Nodes (RPC)
Serve client requests (wallets, dApps). Do not participate in consensus.
Archive Nodes
Store the complete historical state of the blockchain for deep querying.
Pro-Tip
If you are building a dApp, you should connect your RPC endpoints to a Full Node, NOT a Validator Node. Validator nodes are aggressively firewalled to protect consensus.
Network Security Configurations
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.