Encrypt The Mempool #001
Transcript
- jochem-brouwer
gm
- normad | pbsf
gm
- Fireflies.ai Notetaker Loring
Loring invited Fireflies.ai here to record & take notes. View Security & Privacy info: https://fireflies.ai/policy Type: '/ff leave' - Remove Fireflies View Realtime notes here: https://app.fireflies.ai/live/01KJQH7S8WS64CE5FR1ZBASZKC?ref=live_chat
- Luis Pinto | Besu
pwned
- Justin Florentine (Besu)
- admin
/ff leave
- Justin Florentine (Besu)
- Anders Elowsson
- jochem-brouwer
To check, EIP-8105 is being withdrawn and being replaced by this PR to EIPs?
- —
Łukasz Rozmej: I could use 5 min pitch of LUCID and another 5 min for its biggest issues and pitfalls ;) I see CL RPC as a definitive nuisance.
- Luis Pinto | Besu
Reacted to "I could use 5 min pi..." with ➕
- jochem-brouwer
Heeft gereageerd op "I could use 5 min ..." met ➕
- Łukasz Rozmej
oh there is an EIP finally? :)
- Anders Elowsson
Replying to "oh there is an EIP f..." Yup 🙂
- jochem-brouwer
Antwoord verzenden naar "I could use 5 min ..." Yes and maybe the changes of EIP-8105 to this new PR, the PR dropped 40 mins ago 😅
- Luis Pinto | Besu
I feel the meeting should be more about LUCID as a proposal as a headliner and why do people think it’s not ready for Hegotá
- Anders Elowsson
Replying to "I could use 5 min pi..." Easier to review changes relative to the LUCID research post. The biggest changes: The ToB fee is moved to be public within the ST ticket The transaction is executed against the previous block header
- soispoke
One pitfall is the 1 slot delay no?
- Ameziane Hamlat
Any overhead on the network side ?
- Fabio Di Fabio
what happens if the encryption key is not revealed?
- Łukasz Rozmej
Reacted to "what happens if the ..." with 👍
- mark
If we do this in Hegota and we also do Frames how do the proposals interact.
- mark
i.e. do encrypted tx's go into frames ?
- soispoke
Replying to "i.e. do encrypted tx..." I’m working on a post that explores this specifically (wip but will publish soon)
- Łukasz Rozmej
I dislike the explosion of tx types, do you have any ideas how to avoid it?
- soispoke
Replying to "I dislike the explos..." Frame txns
- Luis Pinto | Besu
Are we allowing normal and encrypted txs at the same time? Would that make sense?
- FLCL
sounds like blob txs
- Anders Elowsson
Also we are limiting how much of the block space that can be taken up by STs in the EIP
- Anders Elowsson
Yup 1/8. Just as a starter
- Luis Pinto | Besu
Ok so as a fallback
- Anders Elowsson
Yeah
- admin
The most common concerns on the ACDE were 1) not mature enough, 2) too complex, 3) unsure how it works with the rest of the roadmap. Maybe we could quickly address those?
- Łukasz Rozmej
why there is a reserved space rather than some kind of gas auction mechanism?
- Anders Elowsson
Replying to "why there is a reser..." How do you mean? It is the maximum, but you need to pay the base fee still
- Anders Elowsson
Replying to "why there is a reser..." So it is max 1/8
- Anders Elowsson
Replying to "why there is a reser..." In the first EIP
- Łukasz Rozmej
Replying to "why there is a reser..." but do I need to pay more than compeating transactions (either private order flow or public mempool?) Like in FOCIL I need to pay
- FLCL
Thank you!
- Anders Elowsson
Thanks!
- admin
Wallets too!
- admin
Thank you!
Call summary
Highlights
- Eip Status:
- ·EIP-8105 (Universal Encrypted Enshrined Mempool) withdrawn; replaced by Lucid design - 00:02:43
- ·New Lucid EIP published (PR #11376); more engineering-specific than research post - 00:03:22
- Protocol Design:
- ·Lucid: two-slot design with tickets reserving block space, keys revealed post-inclusion - 00:09:07
- ·Prevents front-running; may reduce back-running efficiency by requiring full top-of-block backrun - 00:10:03
- ·Penalty mechanism: 1/64 of top-of-block fee retained if key not revealed - 00:13:02
- ·Ciphertext encapsulation uses AEAD per RFC 9180; extensible for post-quantum - 00:21:41
- ·Maximum 1/8 block gas for sealed transactions; expandable to 1/2 for catch-up - 00:33:12
- Ecosystem Considerations:
- ·Interaction with Frames unclear; needs investigation if both in Hegotá - 00:16:15
- ·FOCIL interaction: sealed transactions can go in inclusion lists (optional initially) - 00:16:32
- ·Optional feature; normal and encrypted transactions coexist; FOCIL prevents censorship - 00:27:01
- Implementation Requirements:
- ·Requires CL RPC API additions: new event for inclusion notification, key reveal method - 00:04:38
- ·PTC votes on key availability; builders must adhere to vote results - 00:15:02
- ·Bundling supported: multiple transactions in one commitment with single/multiple keys - 00:23:26
Action Items
- •All teams - Review Lucid EIP PR #11376 and provide feedback - 00:03:59
- •Justin, Julian, Anders - Engage MEV ecosystem (builders, searchers, wallets) for feedback on Lucid - 00:35:56
Key decisions
EIP-8105 (Universal Encrypted Enshrined Mempool) withdrawn; replaced by Lucid design
New Lucid EIP published (PR #11376); more engineering-specific than research post
Penalty mechanism: 1/64 of top-of-block fee retained if key not revealed
Requires CL RPC API additions: new event for inclusion notification, key reveal method
PTC votes on key availability; builders must adhere to vote results
Bundling supported: multiple transactions in one commitment with single/multiple keys
Interaction with Frames unclear; needs investigation if both in Hegotá
FOCIL interaction: sealed transactions can go in inclusion lists (optional initially)
Optional feature; normal and encrypted transactions coexist; FOCIL prevents censorship