Repository navigation
Conversation
rymnc
reviewed
Oct 29, 2026
| - **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á. |
Member
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.
Suggested change
| - **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. |
Contributor
Author
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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