Add encrypted mempool (EIP-8184) - #5403
Conversation
|
Addressed all four review comments in a8d59ec codename gone, abbreviations expanded. |
| A *key publisher* is an off-protocol actor that holds decryption keys | ||
| for sealed transactions and releases them after the scheduling decision | ||
| is fixed. Key publishers are not validators and do not have any | ||
| in-protocol registration in this version of the encrypted mempool. A | ||
| sealed transaction's `key_publisher` field is an execution-layer | ||
| address; for bundles, the `SealedBundle.key_publisher_signature` | ||
| recovers the publisher's address over `(chain_id, bundle_root)`. |
There was a problem hiding this comment.
Why did we decide to go with an off-protocol actor here? I have an aversion to off-protocol things ever since mev-boost 😅 Would it be possible to do this -in-protocol? Maybe take advantage of the builder registry here? Maybe a "key builder" entity?
There was a problem hiding this comment.
The reason we went off-protocol is that senders can be their own key publisher self decryption is baked into the EIP as a first-class path and if a publisher
goes dark, only the senders who picked it lose their tob_fee burn, so we don't get the network-wide liveness hit that makes MEV-Boost scary, pulling this in protocol later is worth exploring, but I would be careful about tying it to the builder registry specifically, since that couples key custody to whoever wins the block.
3 participants
https://eips.ethereum.org/EIPS/eip-8184