Repository navigation
Conversation
| - **Networks:** live on Gnosis Chain; Ethereum integration planned | ||
| - **Networks:** Gnosis Chain mainnet (encrypted mempool, 7 keypers with a threshold of 4); Shutter API on Gnosis Chain and Chiado | ||
| - **Ethereum:** an out-of-protocol proof of concept with Primev's mev-commit was announced for the Hoodi testnet in December 2025 (3-of-5 keypers, builders commit before keys are released). The mainnet launch had not happened as of September 2026. | ||
| - **Enshrinement:** Shutter authored [EIP-8105](https://eips.ethereum.org/EIPS/eip-8105) (Draft), an enshrined encrypted mempool. Its bid to headline the Hegotá upgrade was withdrawn in February 2026 in favour of LUCID ([EIP-8184](https://eips.ethereum.org/EIPS/eip-8184)), which the team now supports for the upgrade after Hegotá. |
There was a problem hiding this comment.
the february 2026 shutter post backs lucid as a Hegotá headliner. the september 2026 brainbot update says only that the team decided to pursue LUCID with validator allowlisted proposers. neither source names the upgrade after hegotá.
suggestion: drop the fork claim.
| - **Enshrinement:** Shutter authored [EIP-8105](https://eips.ethereum.org/EIPS/eip-8105) (Draft), an enshrined encrypted mempool. Its bid to headline the Hegotá upgrade was withdrawn in February 2026 in favour of LUCID ([EIP-8184](https://eips.ethereum.org/EIPS/eip-8184)), which the team now supports for the upgrade after Hegotá. | |
| - **Enshrinement:** Shutter authored [EIP-8105](https://eips.ethereum.org/EIPS/eip-8105) (Draft), an enshrined encrypted mempool. Its bid to headline the Hegotá upgrade was withdrawn in February 2026 in favour of LUCID ([EIP-8184](https://eips.ethereum.org/EIPS/eip-8184)), which the team now supports. |
There was a problem hiding this comment.
The Brainbot update set “Have an EM EIP ready to propose as I* Headliner” as a goal, so I kept the sentence, but updated it with the source.
Wrt to everything else, agreed on all your comments, see 6d5bf17.
oskarth
left a comment
There was a problem hiding this comment.
Thanks David, nice work. I agree with moving encrypted mempools to cr: medium, and it's consistent across the pattern, the approach, the table and the pre-trade card now. Private Relay as the default makes sense for L1 too, since there's no encrypted mempool live there yet.
I left three comments I'd like fixed before merge (Shutter on Gnosis, the 88% number, the OTC rating) and three small nits.
| ## What it is | ||
|
|
||
| Shutter Network provides encrypted-mempool infrastructure that prevents MEV extraction and front-running by encrypting transactions until they are included in blocks, using threshold cryptography for decryption. It is live on Gnosis Chain, with Ethereum integration planned. | ||
| Shutter Network provides encrypted-mempool infrastructure that prevents MEV extraction and front-running by encrypting transactions until their ordering is committed, using threshold cryptography for decryption. Brainbot develops it. Shutterized Gnosis Chain has been live since July 2024, opt-in through a Shutter RPC. On Ethereum mainnet no Shutter encrypted mempool is live as of October 2026. |
There was a problem hiding this comment.
Gnosis archived its Shutter docs on 3 September. The archived page says Shutter is "no longer part of Gnosis Chain". Brainbot's September update still says the keypers are running, though, so I'd mention both instead of just saying "in production".
The same wording is also in shutter.md:32, :43, :51, pattern-threshold-encrypted-mempool.md:50, :59, pattern-pretrade-privacy-encryption.md:64 and approach-private-broadcasting.md:24, :133, :213. Maybe check maturity: production on line 4 too.
Also, the docs link at pattern-threshold-encrypted-mempool.md:116 now goes to an empty page. The spec is in gnosischain/specs.
| Shutter Network provides encrypted-mempool infrastructure that prevents MEV extraction and front-running by encrypting transactions until their ordering is committed, using threshold cryptography for decryption. Brainbot develops it. Shutterized Gnosis Chain has been live since July 2024, opt-in through a Shutter RPC. On Ethereum mainnet no Shutter encrypted mempool is live as of October 2026. | |
| Shutter Network provides encrypted-mempool infrastructure that prevents MEV extraction and front-running by encrypting transactions until their ordering is committed, using threshold cryptography for decryption. Brainbot develops it. Shutterized Gnosis Chain went live in July 2024, opt-in through a Shutter RPC. In September 2026 Gnosis archived its Shutter docs, saying Shutter is no longer part of Gnosis Chain ([Gnosis docs](https://github.com/gnosischain/documentation/blob/main/archives/Shutter/README.md)); Brainbot's September update still reports an active keyper set. On Ethereum mainnet no Shutter encrypted mempool is live as of October 2026. |
There was a problem hiding this comment.
Done, with your text, and the same change everywhere you listed. pattern-private-transaction-broadcasting.md:50 had it too, so I changed that as well. The Gnosis docs link now points to gnosischain/specs. I kept maturity: production on the vendor card, since the Shutter API still runs (Brainbot's update: production API keyper set 5 of 5 online).
| |---|---|---|---|---| | ||
| | **Maturity** | production | production | prototyped | prototyped | | ||
| | **Context** | both | i2i | both | both | | ||
| | **CROPS** | CR:low O:part P:part S:med | CR:med O:y P:full S:med | CR:med O:part P:part S:med | CR:med O:part P:full S:med | |
There was a problem hiding this comment.
Line 100 now sends matched OTC trades through the Private Relay. So OTC can be censored the same way as the relay (a builder can just drop the bundle). But the relay is cr: low and OTC is still cr: medium, here and on line 93. Should OTC be low too? Or if the venue adds something for inclusion, could you say what?
| | **CROPS** | CR:low O:part P:part S:med | CR:med O:y P:full S:med | CR:med O:part P:part S:med | CR:med O:part P:full S:med | | |
| | **CROPS** | CR:low O:part P:part S:med | CR:low O:y P:full S:med | CR:med O:part P:part S:med | CR:med O:part P:full S:med | |
|
|
||
| **Threat model:** | ||
| - A relay or builder that sees the order can trade ahead of it; contracts and reputation are the only enforcement | ||
| - Inclusion waits for a reached builder to win a slot; three builders produced about 88% of MEV-Boost blocks in late September 2026 |
There was a problem hiding this comment.
I couldn't get 88% from relayscan. On the daily pages, Titan, BuilderNet and Quasar had between 90.6% and 95.9% of MEV-Boost blocks every day from 22 to 30 September (93.9% on the 25th). Linking a daily page also fixes Aaryamann's point that the front page changes over time. The same line is in pattern-private-transaction-broadcasting.md:96.
| - Inclusion waits for a reached builder to win a slot; three builders produced about 88% of MEV-Boost blocks in late September 2026 | |
| - Inclusion waits for a reached builder to win a slot; three builders produced over 90% of MEV-Boost blocks on each day from 22 to 30 September 2026 ([relayscan](https://www.relayscan.io/stats/day/2026-09-25)) |
There was a problem hiding this comment.
Fixed. For reference, the 88% figure comes from the EIPs post. I assume that number was current at that time.
| ## Intent | ||
|
|
||
| Prevent miner-extractable-value extraction by encrypting transaction content before mempool submission and releasing the decryption key only after block ordering is committed. A distributed committee holds threshold key shares, so no single party can decrypt prematurely. The result is cryptographic protection against front-running, back-running, and sandwich attacks, without handing trust to any one relay. | ||
| Prevent maximal extractable value (MEV) extraction by encrypting transaction content before mempool submission and releasing the decryption key only after block ordering is committed. A distributed committee holds threshold key shares, so no single party can decrypt prematurely. The result is cryptographic protection against front-running, back-running, and sandwich attacks, without handing trust to any one relay. Shutter runs this in production on Gnosis Chain. On Ethereum no encrypted mempool is live: LUCID ([EIP-8184](https://eips.ethereum.org/EIPS/eip-8184)), the leading proposal to enshrine one, is a Draft and is not scheduled for Hegotá. |
There was a problem hiding this comment.
Nit: encryption doesn't prevent back-running. After decryption anyone can trade right after the transaction, and LUCID and Shutter/mev-commit both allow this on purpose. I also put the Gnosis change in here.
| Prevent maximal extractable value (MEV) extraction by encrypting transaction content before mempool submission and releasing the decryption key only after block ordering is committed. A distributed committee holds threshold key shares, so no single party can decrypt prematurely. The result is cryptographic protection against front-running, back-running, and sandwich attacks, without handing trust to any one relay. Shutter runs this in production on Gnosis Chain. On Ethereum no encrypted mempool is live: LUCID ([EIP-8184](https://eips.ethereum.org/EIPS/eip-8184)), the leading proposal to enshrine one, is a Draft and is not scheduled for Hegotá. | |
| Prevent maximal extractable value (MEV) extraction by encrypting transaction content before mempool submission and releasing the decryption key only after block ordering is committed. A distributed committee holds threshold key shares, so no single party can decrypt prematurely. The result is cryptographic protection against front-running and sandwich attacks, without handing trust to any one relay; back-running after decryption stays possible. Shutter ran this on Gnosis Chain from July 2024; Gnosis archived its Shutter docs in September 2026. On Ethereum no encrypted mempool is live: LUCID ([EIP-8184](https://eips.ethereum.org/EIPS/eip-8184)), the leading proposal to enshrine one, is a Draft and is not scheduled for Hegotá. |
There was a problem hiding this comment.
Agreed, used your wording
| ## Intent | ||
|
|
||
| Prevent censorship of Ethereum transactions by sophisticated block builders. A committee of 16 validators per slot can force-include transactions in the next block; non-compliant blocks fail fork-choice and cannot reach finality. The pattern provides no privacy on its own: transactions remain fully visible in the mempool and on chain. It guarantees only that a transaction cannot be censored once it reaches the public mempool. | ||
| Prevent censorship of Ethereum transactions by sophisticated block builders. A committee of 16 validators per slot can force-include transactions in the next block; non-compliant blocks fail fork-choice and cannot reach finality. The pattern provides no privacy on its own: transactions remain fully visible in the mempool and on chain. It guarantees only that a transaction cannot be censored once it reaches the public mempool. FOCIL is scheduled for inclusion in the Hegotá upgrade, estimated for mid-2027. |
There was a problem hiding this comment.
Nit: I couldn't find a date for FOCIL in EIP-8081. I think mid-2027 comes from Forkcast, so maybe link it.
| Prevent censorship of Ethereum transactions by sophisticated block builders. A committee of 16 validators per slot can force-include transactions in the next block; non-compliant blocks fail fork-choice and cannot reach finality. The pattern provides no privacy on its own: transactions remain fully visible in the mempool and on chain. It guarantees only that a transaction cannot be censored once it reaches the public mempool. FOCIL is scheduled for inclusion in the Hegotá upgrade, estimated for mid-2027. | |
| Prevent censorship of Ethereum transactions by sophisticated block builders. A committee of 16 validators per slot can force-include transactions in the next block; non-compliant blocks fail fork-choice and cannot reach finality. The pattern provides no privacy on its own: transactions remain fully visible in the mempool and on chain. It guarantees only that a transaction cannot be censored once it reaches the public mempool. FOCIL is scheduled for inclusion in the Hegotá upgrade ([EIP-8081](https://eips.ethereum.org/EIPS/eip-8081)); no date is set, and [Forkcast](https://forkcast.org/upgrade/hegota) projects mid-2027. |
There was a problem hiding this comment.
Fixed, but the Forkcast link just says 2027, so I went with that.
|
|
||
| ## [Unreleased] | ||
|
|
||
| - fix(approach): Phase 1 review of [Private Transaction Broadcasting](approaches/approach-private-broadcasting.md) for the encrypted mempool cycle, with a new Private Relay sub-approach. |
There was a problem hiding this comment.
Nit: "Phase 1" and "cycle" are our internal terms. People reading the changelog won't know what they mean.
| - fix(approach): Phase 1 review of [Private Transaction Broadcasting](approaches/approach-private-broadcasting.md) for the encrypted mempool cycle, with a new Private Relay sub-approach. | |
| - fix(approach): review of [Private Transaction Broadcasting](approaches/approach-private-broadcasting.md), with a new Private Relay sub-approach ([#213](https://github.com/ethsystems/map/pull/213)). |
What are you adding?
Description
Phase 1 review of the Private Transaction Broadcasting approach and the cards it links, for the encrypted mempool approach cycle.
crfromhightomedium. The sender stays visible and builders can refuse ciphertexts; it reacheshighonce inclusion lists carry sealed transactions. Keys are released once the ordering is committed, not after finality.The
crchange is the main judgement call; happy to discuss.Checklist