Magi doesn't support sequencing

[gregdhill]

I may be off-base here as I'm still trying to understand exactly how OP stack works but it's my understanding that magi is an alternative to op-node which includes sequencing. I can see that they override NoTxPool here which would instrument op-geth via the Engine API to construct a block with the L2 transactions. The batcher I assume would collect those transactions directly and submit those to the L1. From what I can tell magi does not support sequencing, or at least no_tx_pool is always set to true, and it is my understanding that the driver is only advanced when it reads a new batch from the L1 - it does not automatically instruct the execution client to build a new block every two seconds. If someone could offer some insight that would be much appreciated!

[gregdhill]

I see now that #179 exists 🤦