Problem
ExecutableData passes block inputs to the processor as separate fields (injected_transactions, events, gas_allowance). This loses the ordering the malachite block sequenced its transactions in: the processor reconstructs a fixed pipeline (injected + events → tasks → queues) instead of replaying transactions in their original order.
Goal
- Carry MB transactions on
ExecutableData as a single ordered Vec<ProcessorTransaction>.
- Have
ethexe-compute map each malachite::Transaction 1:1 into a ProcessorTransaction, resolving AdvanceTillEthereumBlock into the concrete Ethereum events it pins.
- Have
Processor::process_programs apply each transaction in sequenced order (EthereumEvents / Injected / ProgressTasks / ProcessQueues).
Problem
ExecutableDatapasses block inputs to the processor as separate fields (injected_transactions,events,gas_allowance). This loses the ordering the malachite block sequenced its transactions in: the processor reconstructs a fixed pipeline (injected + events → tasks → queues) instead of replaying transactions in their original order.Goal
ExecutableDataas a single orderedVec<ProcessorTransaction>.ethexe-computemap eachmalachite::Transaction1:1 into aProcessorTransaction, resolvingAdvanceTillEthereumBlockinto the concrete Ethereum events it pins.Processor::process_programsapply each transaction in sequenced order (EthereumEvents/Injected/ProgressTasks/ProcessQueues).