←
Shutter 🛡️⚔️4,706 posts
Shutter 🛡️⚔️ avatar

Shutter 🛡️⚔️

@ShutterNetwork

Encrypt the mempool. In the future, everyone will be protected against malicious MEV & real-time censorship—by default. That's what Shutter is building toward.

◷ Joined March 2021▧ 633 Photos and videos
Shutter 🛡️⚔️ avatar
Shutter 🛡️⚔️@ShutterNetwork·8h

Tune in to the Encrypt the Mempool coalition's livestream - discussing the latest progress on an EIP to bring an encrypted mempool to Ethereum! 📅 Tuesday, 24 Nov at 17:00 UTC

Meet the Encrypt the Mempool Coalition 🔐 Justin Florentine of Besu and Jannik Luhn of Shutter Network will share why they're working to encrypt Ethereum's public mempool. Join us Tuesday 24th November at 17:00 UTC 📅

Post attachment
Shutter 🛡️⚔️ avatar
Shutter 🛡️⚔️@ShutterNetwork·22h

All applications will undergo a public submission check by @SEEDGov to verify eligibility, evidence, and required disclosures The Shutter DAO retains final authority over grant awards through a Snapshot vote If you've already contributed meaningful work to Shutter, this is your opportunity to get it recognized and rewarded! 🧵 5/5

Shutter 🛡️⚔️ avatar
Shutter 🛡️⚔️@ShutterNetwork·22h

Round 2 timeline: ▸ Launch: Today ▸ Completed work and evidence deadline: Dec 21, 2026 ▸ DAO award vote: Jan 8, 2027 ▸ Award payments: Jan 15, 2027 Applications must follow the template and stay within the 600-word narrative limit Apply here and learn more: shutternetwork.discourse.gro… 🧵 4/5

Shutter 🛡️⚔️ avatar
Shutter 🛡️⚔️@ShutterNetwork·22h

Unlike Round 1, Round 2 rewards completed work, not future proposals. Applicants must provide: ▸ Evidence of completed work ▸ Clear authorship and contribution details ▸ A direct connection to Shutter's priorities ▸ Concrete results and what they make possible ▸ Compensation disclosures and a justified award request Work already funded elsewhere is not eligible for duplicate payment 🧵 3/5

Shutter 🛡️⚔️ avatar
Shutter 🛡️⚔️@ShutterNetwork·22h

For Round 2, contributions should advance one of 4 priority areas: ▸ Private Voting Deployments and Revenue ▸ Shutter API Conversion ▸ Encrypted Mempool Adoption ▸ Concorde and Shared Agent Deployments Exceptional contributions outside these areas may also qualify if they directly advance a current Shutter priority. 🧵 2/5

Shutter 🛡️⚔️ avatar
Shutter 🛡️⚔️@ShutterNetwork·22h

Shutter DAO 0x36 Impact Pilot Round 2 is now open! This round focuses on retroactive grants, rewarding contributors who have completed work that advances Shutter’s products, deployments, adoption, or ecosystem priorities Applications are now open 👇 🧵 1/5

Post attachment
Shutter 🛡️⚔️ avatar
Shutter 🛡️⚔️@ShutterNetwork·Nov 13

We’re excited to see @gnosischain preparing to become a rollup in the Ethereum Economic Zone - it’s a big step for the Gnosis team and for Ethereum! As part of the move, we’re decommissioning the Shutter encrypted mempool on Gnosis Chain on 25 November, as the upcoming protocol changes are incompatible with the current deployment Gnosis Chain was the first mainnet to run a Shutter encrypted mempool, and over two years in production showed the design works on a live chain If you have (erpc.gnosis.shutter.network) in your wallet, switch to a standard Gnosis Chain RPC before 25 November But we’re not done with encrypted mempools, far from it! We’re working with the Encrypt the Mempool coalition to bring an encrypted mempool to Ethereum, and this week we just contributed a new draft EIP that tackles one of the big open problems You can learn more about it here: ethereum-magicians.org/t/eip…

Octant avatar
⟳ Shutter 🛡️⚔️ retweeted
Octant@OctantApp·Nov 12

"We launched our vaults last year. (...) We've had two partners that have used our vaults, and have seen success with them. @ShutterNetwork is one of them, and they're an incredible team. They've been advocating for encrypting the mempool. (...) The other is @gitcoin, which is a name many are familiar with." 💬 @arlery

Shutter 🛡️⚔️ avatar
Shutter 🛡️⚔️@ShutterNetwork·Nov 11

The Shutter Impact 0x36 Round 1 vote concluded a few days ago with 8 votes and 31.4M SHU cast Unfortunately, no applicants received the required support to advance. Projects needed at least 50% of the participating SHU voting power to vote “YES” to qualify for funding We’d like to thank all of the applicants for the submissions, especially those that participated in Pitch Day as well as to delegates that have voted The program will now move ahead with Round 2, focused on Retroactive grants, to which we’ll share guidelines early next week

Post attachment
Shutter 🛡️⚔️ avatar
Shutter 🛡️⚔️@ShutterNetwork·Nov 10

This is an early draft and we’d love your feedback on Ethereum Magicians ethereum-magicians.org/t/eip… Also join Encrypt the Mempool Tech Working Group meeting tomorrow to discuss - Wed, 11 Nov, 15:00 UTC github.com/ethereum/pm/issue… 🧵 8/8

Shutter 🛡️⚔️ avatar
Shutter 🛡️⚔️@ShutterNetwork·Nov 10

Who makes the priority list A key publisher joins the priority list once validators holding more than half of all staked ETH have voted for it If a key publisher on the priority list holds back keys, everyone can see it, and validators can vote it off 🧵 7/8

Shutter 🛡️⚔️ avatar
Shutter 🛡️⚔️@ShutterNetwork·Nov 10

Anyone can create a voting list of key publishers Each validator picks one voting list, and that counts as a vote for every key publisher on it This lets validators rely on someone they trust instead of checking every key publisher themselves 🧵 6/8

Shutter 🛡️⚔️ avatar
Shutter 🛡️⚔️@ShutterNetwork·Nov 10

A key publisher that isn’t on the priority list can’t use that waiting trick to get ahead of transactions with trusted key publishers, because those transactions are already placed first No key publisher is shut out, their transactions still get in 🧵 5/8

Shutter 🛡️⚔️ avatar
Shutter 🛡️⚔️@ShutterNetwork·Nov 10

The new EIP lets validators choose key publishers they trust and put them on a priority list Transactions whose key publisher is on the priority list go first in the block Transactions with any other key publisher go after them 🧵 4/8

Shutter 🛡️⚔️ avatar
Shutter 🛡️⚔️@ShutterNetwork·Nov 10

The optionality problem One key concern is that a key publisher could hold back a key until they see how later transactions play out They could then release it only when it benefits them, opening the door to front running 🧵 3/8