Mission
BULK Exchange is designed to close the performance gap between centralized and decentralized trading venues. The goal is not incremental improvement but a fundamentally different execution environment - one that delivers colocation-grade speed with cryptographic guarantees that no centralized venue can offer.Design Goals
Low-Latency Matching and Propagation. Achieve matching plus propagation latency in the 5-20ms range within regional validator sets. Leaderless Decentralization. No single point of failure, no leader-based block production, no centralized sequencer. Every consensus round is leaderless - no single validator can censor or reorder transactions. Verifiable and Permissionless. The entire system state is cryptographically verifiable. Validator participation is open and secured by economic stake inherited from Solana. High-Performance Order Book. Infrastructure for internet-scale capital markets, with throughput far beyond current on-chain systems.Core Architecture
BULK is an L0 - a specialized execution layer that runs natively alongside Solana. Each BULK validator runs a dedicated binary (bulk-agave) alongside the standard Solana/Agave validator, inheriting its identity keys with proportional stake weight. BULK validators form their own consensus network while Solana handles deposits, withdrawals, and asset custody.
The architecture separates concerns cleanly:
- BULK Net - Authenticated transport layer for validator-to-validator communication. Transactions are broadcast, deduplicated, and disseminated across the validator set.
- BULKBFT Consensus - Leaderless Byzantine fault-tolerant consensus with a fast path that completes in a single vote-commit round under partial synchrony. Validators exchange compact sketches, reconcile transaction sets via minisketch, and commit batches that a supermajority agrees on.
- Executor - Deterministic execution engine. Every validator processes the identical committed batch through the identical matching engine and produces the identical output state.
- Solana Ledger - Settlement layer. Deposits and withdrawals are settled on Solana. Assets remain in Solana custody throughout.
Fair Ordering
BULK does not use FIFO ordering. Instead, it employs a multi-layered fairness design that prevents any single participant from controlling transaction ordering:- Quorum-controlled batch admission. The transaction set in each batch is the intersection of pending sets across a supermajority of validators, computed via minisketch reconciliation. No single validator controls what enters the batch.
- Deterministic shuffle. After commitment, transactions are shuffled using a Fisher-Yates algorithm seeded by the consensus-derived batch timestamp. The seed is a consensus output that no single validator can unilaterally determine.
- Structural priority queues. After the shuffle, transactions are separated by type: cancels execute first, then post-only maker orders, then regular orders. This guarantees that traders can always cancel before being filled and makers always seed the book before takers cross it.
- Price-time priority on the book. The order book itself uses standard price-time priority for matching.
Regional Books
BULK uses regional validator subsets to achieve low latency - the same architecture used by TradFi venues that process trillions in derivatives volume. Each region runs BULKBFT consensus among geographically close validators where sub-20ms round trips are achievable. When local liquidity is insufficient, orders route cross-region at higher latency. See BIP-2 (coming soon) for the full regional books specification.Censorship Resistance
Censorship resistance is the most critical property a decentralized application must offer. Without it, the system is self-custody with centralized execution. BULK’s architecture ensures censorship resistance through:- Leaderless consensus - No single validator proposes blocks or controls ordering.
- Quorum inclusion - Transaction inclusion requires supermajority agreement, not a single sequencer’s decision.
- Deterministic execution - Every validator produces the same output from the same input. Any attempt to alter execution is immediately detectable by any observer.
- No bridges, no sequencers - Eliminates entire categories of centralization risks that affect L2 and cross-chain systems.