Choose the correct data source for an OP Ecotone batcher transaction
A blob transaction can also contain calldata. A derivation tool that processes both inputs may invent frames the protocol never consumes.
Select data by transaction type
After confirming that the transaction qualifies as batcher data, check the fork and transaction type. Under Ecotone, an eligible type-3 blob transaction supplies blob data; its calldata is ignored for this purpose.
transaction type: 0x03
calldata: nonempty
blob hashes: H0, H1
For the example, retrieve the blobs matching H0 and H1, verify the correspondence to the advertised versioned hashes, and process valid blob payloads in the specified order. Do not concatenate the calldata ahead of them.
Distinguish missing data from an empty batch
A local beacon data source may no longer serve an older sidecar. Record the missing hash and obtain the required historical blob from a suitable source before deciding what the batch contained. A normal execution block response alone carries no blob payload. specs.optimism.io OP Stack specification