{
  "id": 8105,
  "title": "EIP-8105: Universal Enshrined Encrypted Mempool",
  "status": "Draft",
  "type": "Standards Track",
  "category": "Core",
  "summary": "Note: withdrawn from Hegota headliner proposals [here](https://ethereum-magicians.org/t/hegota-headliner-proposal-eip-8105-universal-enshrined-encrypted-mempool-eem/27448/3) on 23 Feb, in favor of LUCID encrypted mempools.\n\nAdds a built-in encrypted mempool option: you can submit an encrypted transaction that stays unreadable until it's included in a block. This reduces front-running and sandwich attacks and can improve real-time censorship resistance. Regular plaintext transactions still work, and the chain continues even if key providers fail.",
  "impacts": [
    "Can submit encrypted transactions until inclusion, reducing front-running/sandwiching and strengthening weak censorship-resistance guarantees.",
    "May add support for encrypted transaction flows and key-provider selection; must handle payloads being skipped if keys missing.",
    "Need envelope/payload signing support, key-provider discovery, and UX for choosing encrypted vs plaintext submissions.",
    "Mempool/RPC/builders must relay encrypted txs, process decryption-key messages, and integrate key validation and ordering rules.",
    "No required L2 protocol changes; they may opt to use encrypted L1 transactions for their own L1 interactions.",
    "PTC members must listen for keys, validate them with a gas cap, and attest key availability per encrypted transaction.",
    "Must implement registry replication, extended payload attestations with a bitfield, and consensus processing of key availability.",
    "Must add encrypted tx type, envelope batch execution and fee accounting, decryption via registry, and skip-on-failure semantics.",
    "Protects users from front-running and sandwich attacks by hiding transaction contents until inclusion.",
    "Improves weak censorship resistance by blinding builders while encrypted transactions wait for inclusion.",
    "Supports diverse encryption schemes via arbitrary decryption key providers and a trust-graph mechanism.",
    "Keeps chain progressing even if key providers fail; plaintext transactions remain supported."
  ],
  "discussion_url": "https://ethereum-magicians.org/t/eip-8105-universal-enshrined-encrypted-mempool/27201",
  "source_markdown_url": "https://github.com/ethereum/EIPs/blob/master/EIPS/eip-8105.md",
  "canonical_url": "/latest/eips/8105.json",
  "markdown_url": "/latest/eips/8105.md",
  "citations": [
    {
      "recordId": "eip-8105",
      "artifactPath": "normalized/8105.json",
      "url": "/records/proposal/eip-8105/normalized/8105.json",
      "label": "EIP-8105: Universal Enshrined Encrypted Mempool",
      "snippet": "Note: withdrawn from Hegota headliner proposals [here](https://ethereum-magicians.org/t/hegota-headliner-proposal-eip-8105-universal-enshrined-encrypted-mempool-eem/27448/3) on 23 Feb, in favor of LUCID encrypted mempool"
    }
  ]
}