trigger megabundle worker loop when new megabundle is received

[thegostep]

Rationale

The logic for generating a block using megabundles currently sits inside of the multi worker which is triggered by the recommit interval which defaults to 3 second intervals. This means that the megabundle worker may sit idle even if there is a megabundle pending construction.

mev-geth/miner/multi_worker.go

Lines 108 to 116 in 516e2c3

	for i := 0; i < len(config.TrustedRelays); i++ {
	workers = append(workers,
	newWorker(config, chainConfig, engine, eth, mux, isLocalBlock, init, &flashbotsData{
	isFlashbots: true,
	isMegabundleWorker: true,
	queue: queue,
	relayAddr: config.TrustedRelays[i],
	}))
	}

Implementation

The megabundle worker should instead begin assembling a megabundle block immediately after receiving a megabundle from one of the trusted relays. If the miner receives a second megabundle while it is still assembling the first block, it should wait until the first block has completed, then begin work on the second block irrespective of the recommit interval.