EIPsInsight

Loading Experience

Preparing your insights...

Loading0%
All protocol calls
PreviousNext
ETM2026-06-10_005

Encrypt The Mempool #005

2026-06-10 2 decisions 377 transcript lines

Transcript

Call summary

Targets
  • •Encrypted Mempool Coalition website + tweet launch — June 11, 2026 (tomorrow) - 00:33:30
  • •Octant Epoch 12 participation — mid-June 2026 - 00:37:18
Decisions
  • •Lucid PM project to be hosted in Justin's GitHub repo; Yannick and others added as collaborators for roadmap artifacts - 00:06:42
  • •Initial $6k to be used primarily for marketing/bounties rather than direct engineering; social bounty model preferred to demonstrate community demand - 00:44:10
Highlights
  • Roadmap And Sfi Path:
    • ·Draft roadmap created: EIP draft → specs/tests (EL+CL) → client impl → devnet → testnet → fork; ecosystem tasks include RPC updates and decryptor standards - 00:06:10
    • ·Execution spec PR open (vibe-coded with Claude, 14k lines, based on Fusaka+FOCIL branch); very early draft, needs review - 00:11:44
    • ·No CL spec contributor yet; Loring/Anthony to reach out to consensus client teams, potentially with a funded bounty - 00:27:19
    • ·EL implementation planned in Besu; Erigon expressed interest and has its own CL — strong candidate for parallel impl - 00:29:17
  • Coalition And Funding:
    • ·Encrypted Mempool Coalition launching tomorrow with ~20 partners (incl. Besu, Erigon, Fairblocks, Web3 Privacy); website at encryptedmempool.org - 00:33:09
    • ·$6k confirmed from DAO Security Fund QF round; Octant Epoch 12 and Shutter Champions Melee 2 (~$10k) pending; social bounties proposed as dual engineering+marketing signal - 00:36:12
    • ·Bounty strategy: funding specific milestones (e.g., CL spec) signals community demand to core devs, not just pays for work - 00:45:05
  • Frame Transactions And Design:
    • ·Frame transactions enable two-signature enforcement (user + builder), preventing key-leaking attacks not addressable via slashing alone - 00:16:53
    • ·Gottfried: ticket signature (not decrypted tx) is the hard part — needs post-quantum sig support and unlinkable sender for true front-running protection - 00:18:57
    • ·Correct Lucid usage requires sending ticket from a one-time address unlinkable to real sender; account abstraction/frame transactions could greatly improve this UX - 00:21:40
  • Eip Criticism And Design Honesty:
    • ·Gottfried: at least one security-critical bug found in draft EIP (easy fix); consensus rule changes not yet fleshed out; marketing should not oversell Lucid as a complete solution - 00:46:37
    • ·Gottfried: 'future-proof agnosticism' claim is cryptographically incorrect — in an encrypted mempool, agnosticism gives adversary best-of-all options; should be toned down - 00:50:58
    • ·Lucid is best available design given current tech, but a purpose-built threshold IBE design would require starting from scratch - 00:51:53
Action Items
  • •Loring, Anthony - Loring/Anthony to reach out to consensus client teams (esp. Erigon) to recruit CL spec contributor, potentially with bounty incentive - 00:27:57
  • •Justin Florentine - Justin to create GitHub issue for next working group call so Anthony can link it from coalition website - 00:35:44
  • •Gottfried Herold - Gottfried to review coalition webpage and flag any claims to tone down before tomorrow's launch - 00:52:00

Key decisions

  • Lucid PM project to be hosted in Justin's GitHub repo; Yannick and others added as collaborators for roadmap artifacts

    Hosting the Lucid PM project in Justin's GitHub repo and adding collaborators for roadmap artifacts.

  • Initial $6k to be used primarily for marketing/bounties rather than direct engineering; social bounty model preferred to demonstrate community demand

    Using the initial $6k for marketing and bounties, with a focus on demonstrating community demand through social bounties.

Links