On this page
Chain Endpoints
This section documents the endpoints used to query the macro state of the Brixs blockchain.
Get Latest Epoch
Returns detailed information about the current consensus epoch, active validator set, and timestamp.
Method: brixs_getEpoch
Request Payload
{
"jsonrpc": "2.0",
"id": 1,
"method": "brixs_getEpoch",
"params": []
}
Expected Response
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"epoch": 420,
"validators": 100,
"startTimestamp": 1718224000,
"totalStake": "5000000000000"
}
}
Parsing Epoch Data
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.