Technologie & IA
Eureka announces BEX for offchain computation before a transaction enters an Ethereum block
The engine separates computation at the block builder from final execution on Ethereum. Its published limits do not represent an increase in the entire blockchain's computing capacity.

Computation during block construction
Eureka Labs announced the launch of BEX on Ethereum on October 29, 2026. The system lets developers have their logic evaluated by its block builder while the builder arranges transactions. The result can then inform an operation included in that block. The approach is particularly relevant to participants seeking to adapt an action to prices, balances or positions as they exist at the precise moment the block is being prepared.
The documentation separates two components. A read-only computation phase runs offchain against the state of the block under construction. A final transaction then uses the resulting data on Ethereum. The two stages do not impose the same workload on the network. The service can therefore devote more computation to preparing a decision without putting all that work into the transaction ultimately validated. This does not mean that every Ethereum validator performs the additional preparation for free.
Two limits that should not be confused
The production values published in the documentation specify a 500 million gas limit for computation and 2 million for the execution transaction. The provider also says the capabilities returned by its interface are authoritative when sizing a request. Comparing the first limit directly with Ethereum's block limit would be misleading: one concerns evaluation at a service provider, while the other covers operations actually subject to the network's rules and shared resources.
Requests target a block and expire if it is not built within the service's prescribed window. Execution is conditional: according to the documentation, the final transaction must deliver more value to the builder than its gas cost. Marketing that emphasizes computation without fees therefore does not describe a universal absence of execution costs. It distinguishes offchain preparation from an operation actually selected for inclusion. Applications need to examine inclusion and compensation conditions before treating BEX as Ethereum computation without any consideration.
Controlled access and a roadmap still to come
The documentation says most methods require an authorized signer on an allowlist. Querying capabilities is distinguished from submitting a request or simulation. The launch therefore does not automatically open every function to any address. Dependence on the builder also matters: logic submitted to this service relies on its access rules, infrastructure and ability to construct the target block, beyond the blockchain's own properties.
Eureka presents a second version for 2027, with external data and programs using WebAssembly. These remain announced developments, rather than features the first version already demonstrates. The verifiable point today is the documented separation between preparatory computation and the final transaction. Adoption indicators put forward by the company also need to be distinguished from an independent measurement of network capacity. The technical issue concerns work offered by a builder, without this announcement itself changing Ethereum's common rules.
