EIP-7793: TXINDEX precompile

[marchhill]

@shemnon cheers Danno that’s really helpful

[thegaram33]

@marchhill

In regards to encrypted mempools, the idea is to enforce with a smart contract that a transaction from the encrypted mempool must be included at the top of block or it will be invalid

This sounds useful, and I’m wondering if this EIP could come in handy for other mechanisms like ERC-4337 bundlers and the Ultra Tx proposal.

But as the EIP says:

If these rules are not enshrined as block validity conditions then they can be enforced by a smart contract.

Programmatically reverting can still be costly, and there’s no way to ensure that a transaction is top of the block. So for this use case to be practical, you might also need other mechanisms like inclusion lists and revert protection.

[sbacha]

You have convinced me ser, system contract makes more sense you are right.

[marchhill]

I shared a research post here that applies the TXINDEX precompile to an encrypted mempool design. Hopefully this can clarify why this precompile is useful for encrypted mempools.