Struct cfxcore::consensus::consensus_inner::consensus_executor::ConsensusExecutionHandler

pub struct ConsensusExecutionHandler { /* private fields */ }

Implementations

impl ConsensusExecutionHandler

pub fn before_block_execution( &self, state: &mut State, block_number: BlockNumber, block: &Block ) -> DbResult<U256>

impl ConsensusExecutionHandler

pub fn new( tx_pool: SharedTransactionPool, data_man: Arc<BlockDataManager>, config: ConsensusExecutionConfiguration, verification_config: VerificationConfig, machine: Arc<Machine>, pos_verifier: Arc<PosVerifier> ) -> Self

pub fn epoch_executed_and_recovered( &self, epoch_hash: &H256, epoch_block_hashes: &Vec<H256>, on_local_pivot: bool, reward_execution_info: &Option<RewardExecutionInfo>, epoch_height: u64 ) -> bool

pub fn compute_epoch( &self, epoch_hash: &H256, epoch_block_hashes: &Vec<H256>, start_block_number: u64, reward_execution_info: &Option<RewardExecutionInfo>, on_local_pivot: bool, debug_record: Option<&mut ComputeEpochDebugRecord>, force_recompute: bool, recover_mpt_during_construct_pivot_state: bool )

Compute the epoch epoch_hash, and skip it if already computed. After the function is called, it’s assured that the state, the receipt root, and the receipts of blocks executed by this epoch exist.

TODO Not sure if this difference is important. One different between skipped execution in pivot chain is that the transactions packed in the skipped epoch will be checked if they can be recycled.

pub fn call_virtual( &self, tx: &SignedTransaction, epoch_id: &H256, epoch_size: usize, request: EstimateRequest ) -> CoreResult<(ExecutionOutcome, EstimateExt)>

pub fn collect_blocks_geth_trace( &self, epoch_id: H256, epoch_num: u64, blocks: &Vec<Arc<Block>>, opts: GethDebugTracingOptions, tx_hash: Option<H256> ) -> CoreResult<Vec<GethTraceWithHash>>

Execute transactions in the blocks to collect traces.