Introduction to EIPs, ERCs, RIPs. EIP: Ethereum Improvement Proposal Protocol-level changes, enforced by the Ethereum clients. Activated via hardforks. Full nodes must upgrade, else fork to opt-out. ERC: Ethereum Request for Comments Application layer standards. Conventions for Solidity, calldata, storage, signatures. Opt-in. Adoption -> network effects. RIP: Rollup Improvement Proposal Provincial laws for rollup city-states. Opt-in for L2s. Opt-out for nodes within an L2. May lead to EIPs. The numbers are shared between EIPs, ERCs, RIPs, assigned sequentially by maintainers. To start one, you will first need to open an Ethereum Magicians forum thread, then make a draft which links to the thread. After which, the specific process depends. Examples: EIP-7939: Count Leading Zeros (CLZ) An opcode in the upcoming Fusaka hardfork that can speed up math operations with smaller bytecode. As a basic math operation that costs as much as a 256-bit `ADD`, this is most suitably implemented as an opcode, which is most suitably implemented as an EIP. ERC-7631: Dual Nature Token Pair Interfaces for how a co-joined fungible and and non-fungible token pair can signal their relationship. Opt-in standard. Allows for better discoverability, better UX. RIP-7767: Gas to Ether contract A contract that burns gas and returns a portion of the gas burned to the caller as the native currency. Due to the adventurous nature of this proposal, this could be piloted as a pre-compile / pre-deploy on rollups first. The tentative mainnet analog is EIP-7791 (GAS2ETH opcode). Difficulty to get adoption / inclusion: EIP > RIP > ERC (approximately) To explain why, each of these deserves their own elaboration in separate threads, best left for future content.

Really disappointing. Smart contracts are the lifeblood of Ethereum.

Milady motivated me to lose weight. I’m still quite fat atm.

Pudgy resonates with builders who are business first. They are a great and safe choice for big corps. Milady resonates with builders who deeply care about the engineering, brutal hard truths, freedom, privacy, open-source, and sustainable growth thru neochibi aesthetics.

Peak engineering often results in multi-functionality. It’s just nature. - The SR-71 used fuel as coolant. - EVs use battery casing as structure. - Bird feathers are used for flight and thermoregulation. - My code optimizations are also safety features. Trust me bro.

Peak engineering often results in multi-functionality. It’s just nature. - The SR-71 use fuel as coolant. - EVs use battery casing as structure. - Bird feathers are used for flight and thermoregulation. - My code optimizations are also safety features. Trust me bro.

Sometimes, I make technical decisions based on instincts that I can’t explain. What feels like an anti-pattern is actually a move 37: the benefits won’t be felt until way later. But by then, it’s already refactored out. Takeaway: need more cockyness to say “trust me bro”.

Come watch me explain the simplest EIP of modern times.

🎙️Upcoming PEEPanEIP Recordings – July 2025 Join @EthCatHerders as we dive into proposals shaping Ethereum’s next chapter. Mark your calendars! 🧵 1️⃣ PEEPanEIP-7939: Count Leading Zeros (CLZ) Opcode 🔹with @optimizoor 🔹Adds an #opcode to count the number of leading zero bits in a 256-bit word. 📅 Recording: July 15, 2025 at 18:30 UTC Don’t miss the deep dive! #PEEPanEIP #Ethereum #eip7939

Solidity aura tip: change it to `3d604052`.