What is a Rollup Improvement Proposal (RIP)?

A Rollup Improvement Proposal (RIP) is a formal document that outlines new features, processes, or optimizations for rollup solutions in the Ethereum ecosystem. RIPs act as specifications to improve rollups, enhance interoperability, and standardize development processes.

All RIPs are optional. RIPs are and will always remain optional standards for Rollups and participants in the larger EVM ecosystem.

Why are RIPs Important?

RIPs help coordinate technical improvements for rollups in a transparent, collaborative way. They:

• Propose new features and optimizations.
• Collect community feedback on rollup-related issues.
• Serve as a historical record of design decisions.
• Help rollups track progress, especially for multi-client implementations.

By adopting RIPs, rollups can align on standards and ensure better interoperability across Layer 2 solutions. The goal of the RIP project is to standardize and provide high-quality documentation for Rollups in the Ethereum ecosystem.

What are the Different Types of RIPs?

Standards Track RIPs - Changes that impact most or all rollup implementations, including:

• Core: Changes to network rules, block validity, EVM opcodes, cryptographic updates.
• RRC (Rollup Request for Comments): Application-level standards like token or wallet formats.
• Other: Improvements relevant to core developer discussions.

Meta RIPs - Proposals related to rollup processes, governance, or the RIP process itself. These are not technical but focus on procedures, tools, or guidelines.

What is the RIP Process?

The RIP process follows these steps:

• Idea Stage: Share your proposal idea for initial feedback (e.g., Ethereum Magicians forum).
• Draft: Submit a formal RIP using the template provided.
• Review: Invite community discussion and peer review.
• Final: Once accepted, the RIP becomes the standard and is ready for implementation.
• Stagnant: RIPs inactive for 6+ months may be labeled as stagnant.
• Withdrawn: Proposals that authors decide to discontinue.
• Living: RIPs continually updated without reaching a final state.

Tip: For Core RIPs, presenting your proposal during Rollcall meetings is the best way to gather technical feedback and consensus from rollup core teams.

Who Can Submit a RIP?

Anyone! Whether you're a developer, researcher, or rollup enthusiast, you can submit an RIP. Before drafting:

• Discuss your idea on the Ethereum Magicians Forum.
• Collaborate with rollup teams early to build consensus.

What Makes a Successful RIP?

A strong RIP includes:

• Clear Specification: Detailed syntax and semantics of the proposed change.
• Motivation: Why the change is necessary.
• Rationale: Design decisions and alternatives considered.
• Security Considerations: Risks, mitigations, and guidance.
• Backwards Compatibility: Notes on how the proposal impacts existing implementations.

How Do I Format a RIP?

RIPs must follow a specific template and structure in Markdown format. Each RIP includes:

• Preamble: Metadata such as RIP number, title, author(s), and status.
• Abstract: A brief technical summary.
• Specification: A detailed technical description of the proposal.
• Rationale: Explanation of design choices.
• Security Considerations: Assessment of potential risks.
• Test Cases (if applicable): Mandatory for consensus changes.
• Reference Implementation (optional): Code to aid understanding.

Refer to the RIP Template for guidelines.

Who Oversees the RIP Process?

RIP Editors ensure proposals are well-formatted and ready for review. They do not decide the merits of a proposal. Current RIP editors include:

• Ansgar Dietrichs
• Carl Beekhuizen
• Yoav Weiss
• Nicolas Consigny

Where Can I Track RIPs and Rollup Progress?

• GitHub Repository: RIP Repository
• Discussions:Ethereum Magicians Forum
• Rollup Status: L2BEAT
• Comparison of Rollups: rollup.codes

What Happens After a RIP is Final?

Once an RIP is accepted and implemented by at least one rollup on their mainnet, it becomes a Final RIP. Care is taken to resolve any conflicts before deployment to avoid competing standards.

How Do I Stay Involved?

• Contribute: Submit your RIP or provide feedback on existing proposals.
• Discuss: Join community discussions on forums and GitHub.
• Engage: Present your RIP at Rollcall meetings to build consensus.

Where Can I Find More Information?

• RIP Template: Link to Template
• RIP Discussions: Ethereum Magicians Forum
• Rollup Specifications: rollup.codes

By collaborating through RIPs, we can drive innovation and ensure a shared, open-source approach to improving Ethereum rollup solutions.