Nick Mudge 💎

New article about ERC-8109 Diamonds, Simplified: eip2535diamonds.substack.com/p/introducing-…

@Satyam561562154 Cool

Day 113 & 114 • Studied ERC-2535 (Diamond Proxy) • Learned how to avoid storage collisions • Attended Block Capital Cohort session • Designed my RWA project • Planning to implement Diamond Proxy + Chainlink Functions

We need more ❤️Love❤️ in the space, we blockchain builders. When we are building one projects, it doesn't mean we have to hate other projects. The sentiment outside of the blockchain and crypto builder community has been challenging enough for us to face. We don't have to be hating each other. Instead, we should embrace each other because, in the end, we're all building a blockchain future and we're all in this together.

The EF just released its Mandate. It's not a retreat. It's an invitation. CROPS — censorship resistance, open source, privacy, security — is what makes Ethereum Ethereum. Without these properties, you have a slow database. The Mandate makes this explicit, and stating clearly what you are *and are not* is an act of institutional clarity that is long overdue. Some raise concerns: is this a turnaround? Is the EF abandoning real-world adoption, rejecting institutional engagement, walking away from the pragmatic compromises that gave Ethereum product-market fit? These concerns would be valid, and devastating, *if* the EF were the whole of Ethereum. But it is not. And that is exactly the point. The EF is one steward, not the sole one. The Mandate is a scoping document for *one organization*, not a scoping document for the ecosystem. The moment we stop conflating EF with Ethereum, the Mandate reads not as a retreat, but as an invitation. We — the community, the builders, the standards authors, the enterprises, the wallets, the researchers — are going to fill these other roles. Individually and together. I am optimistic precisely because the EF is not trying to be everything. That is the precondition for the rest of us stepping up. And here is where the ERC community comes in. We will be supporting the adoption of ERCs grounded in CROPS principles. ERCs that preserve user agency. ERCs that are practically implementable. ERCs that engage wallets, exchanges, institutions, and application builders to find the path from where the world is today to where Ethereum can take it. The ERC process does not need the EF to carry it. It needs the community to own it. In fact, ERCs are the perfect embodiment of the model the Mandate envisions. ERCs are free to collaborate on and free to compete with. No one forces adoption — you adopt an ERC because it solves your problem. Governance happens through sovereign individuals making their own selections. You vote with your feet. You build together without coercion. This is CROPS in action at the standards layer: open, permissionless, forkable, and accountable to no one except the people who choose to use them. Let's build ERCs. Together, we will have a bright future for @Ethereum and the world. The call is open. Let's get to work. @ERCRef

gBlok builders ☘️ Missed the live cohort session this week? No worries, the full class recording from our Google Meet is now on our YouTube channel If you want to see what our builders are learning about real protocol architecture and smart contract systems, this is a good place to start. Catch up here 👇and stay in the loop. youtu.be/YhmIebvrVFQ Don’t forget, game night is tomorrow and it’s going to be a fun one. Make sure you’re around. Everyone deserves a garden.

@fulldecent Engineer B?

Apple had a choice between these two engineers. And here is what they said on their whiteboard interview, guess which one got hired? QUESTION: If you had to implement a full-disk search program where it provide instant results for everything on the Mac, how would you do it? ENGINEER A: I would create a search index, and name the product Spotlight, and it would return results immediately. ENGINEER B: I would create a search index, and name the product Spotlight, and it would return results immediately. But 2% of the time it wouldn't return any response at all. Literally just nothing.

Don't forget to fill the Solidity Survey. It's only open for one more week. And you have a chance to win a @EFDevcon ticket.

Cohort Session 2 went live yesterday and it was a strong one. Participants explored the Diamond Proxy standard with @mudgen breaking down how modular smart contract architecture works in real systems. Each session is focused on building developers who understand how real protocols are structured, secured and upgraded in practice. We’re not just teaching code, we’re training future protocol builders. gBlok

We built Boom Town a fully onchain Wild West hot potato game for Monad Blitz Hachathon Here's what's under the hood: Diamond Pattern (EIP-2535) All game logic lives behind a single Diamond proxy. 10 facets. Lobby, gameplay, ERC-20 gold, ERC-1155 dynamite, payouts — all sharing one storage slot via delegatecall. Upgradeable without redeploying state. Oasis ROFL + TEE We use an Oasis ROFL backend running inside a hardware-attested Intel TDX enclave. The ROFL wallet's private key is derived inside the enclave and never exposed. Fast, secure, no oracle fees. 4-8 players, 10 GOLD ante, last one standing wins the pot. Here is BOOM TOWN Github Repo URL: github.com/itublockchain/… Demo: boom-town-one.vercel.app @monad_dev @ITUblockchain

@ZainanZhou Super interesting. Thanks.

Session 2 of our Cohort is live! @mudgen on Diamond Proxy! Get your knowledge base enhanced by the creator himself!

I just want to share what I’ve been up to last month and this month. I’ve been attending my ZK classes at @Web3Bridge and combining that with BLOK Capital. I’ll be sharing updates about my ZK journey soon, there’s a lot to unpack. Today is Day 2 of @blok_cap Cohort 1. We discussed the Diamond contract, how it works, and how its functions are structured. The session was led by @mudgen. Fellow cohort members, I hope you’re enjoying it as much as I am. We also touched on ERC-8153, which aims to make things easier and more understandable. It was motivated by the fact that ERC-2535 has perceived complexity, high gas costs when deploying diamonds, and complexity in managing function selectors. #blowthisup #ethereum #Web3 #الرياض_الان

@devjoshstevens @vicnaum Awesome. Thank you!

Separate events - Added, Replaced and Removed. The main reason is speed: when you only have a Set event, you have to do an INSERT … ON CONFLICT which is super slow. Added = use insert with binary copy = 50-100x faster than an insert on conflict Replaced = use a standard update = 2-5x faster than an insert on conflict Removed = a standard delete This now means your indexing will be as fast as it can be, and the separation of concerns is clean.

For ERC-8109 Diamonds, Simplified, should the events that track functions added to, replaced in, and removed from diamond contracts be three events like this: DiamondFunctionAdded(selector, facet) DiamondFunctionReplaced(selector, oldFacet, newFacet) DiamondFunctionRemoved(selector, oldFacet) Or one event like this: SetDiamondFacet(selector, facet) Or one event like this: DiamondFunctionSet(selector, oldFacet, newFacet) (When oldFacet is address(0) then it means adding a new function) (When newFacet is address(0) then it means removing a function) I am interested in feedback about this from developers, and people that work on indexers, block explorers and other tools that use events. The full draft ERC-8109 standard is here: eips.ethereum.org/EIPS/eip-8109 Discussion about this is here: ethereum-magicians.org/t/erc-8109-dia…

1/ New 3-part tutorial series just dropped 💎 Learn how to implement the Diamond Proxy Pattern (EIP-2535) on @Rootstock_io: Part 1: Core concepts & setup Part 2: Implementing facets Part 3: Upgrades & diamond cut

🚨Blok Capital Cohort is CLOSING SOON Time to level up from smart contract dev to true Protocol Builder! Hands on building, live sessions with OGs like @mudgen, @Timidan_x and @DrAndyWynn Don't miss out, spots won't last. Apply now:

1/Been reading upgradeable contracts for a while now. Most proxy patterns are duct tape with a bow on it. Then I found EIP-2535 - the Diamond Proxy by @mudgen This one's different. Here's why 🧵

Today, @DDX_Official is live. It is officially the first DAO-governed decentralized derivatives exchange to operate with a regulatory license.

1/ After years of building, @DDX_Official is live. It's the first and only DAO-governed decentralized derivatives exchange operating with a regulatory license anywhere. Some thoughts on what this means and why it matters:

@apalepu23 @DDX_Official I have waited for this day for years. Congrats @apalepu23 for persisting and pushing this through to completion. The next phase begins!