On this page
Consensus: Decentralized Sequencer & ZK-SNARK Prover
The core engine securing the Brixs Network is the Decentralized Sequencer (DPoS) combined with our highly advanced ZK-SNARK Prover Engine.
Testnet Environment
The Sequencer is currently running in Testnet. During this phase, validators are tested, and ZK proofs are verified locally before being deployed to the Ethereum L1 Mainnet.
Key Characteristics
Decentralized Sequencer (DPoS)
A staking manager allowing anyone to stake BRIXS to propose blocks, eliminating centralized sequencer failure points.
Encrypted Mempool
Protects users against MEV (Miner Extractable Value) sandwich attacks by encrypting transactions before they are ordered.
ZK-SNARK Prover
Generates mathematical proofs of block execution, making the chain infinitely scalable while inheriting Ethereum's security.
EVM Rollup
Transactions are processed natively via @ethereumjs/vm and batched sequentially into secure rollups.
Deep Dive: How the Sequencer Works
Phase 1: Transaction Encryption
When a user submits a transaction (e.g. via our Account Abstraction Paymaster), it enters the Encrypted Mempool. This guarantees that block proposers cannot front-run or sandwich user trades.
Phase 2: DPoS Block Proposal
Validators who have staked $BRIXS are selected dynamically to propose the next block. This removes the "single sequencer" risk present in older L2s like Optimism and Arbitrum. The node processes the transactions natively using our optimized @ethereumjs/vm gateway.
Phase 3: ZK Proof Generation
Once the block is assembled and state transitions are finalized locally, our Prover Engine generates a zero-knowledge cryptographic proof of the execution. This proof guarantees mathematically that all state changes were valid.
// Connect to the Testnet RPC to observe blocks
const provider = new ethers.providers.JsonRpcProvider("http://localhost:8545");
const block = await provider.getBlock("latest");
console.log(`Current Sequencer Block: ${block.number}`);