How eigenfoundation/elips works
Project Type and Purpose
• This repository is not a full-blown application per se—it is a documentation and governance tracker for proposals that improve EigenLayer’s core contracts.
• The repository’s purpose is to maintain version-controlled documentation (the ELIPs) that detail the proposals’ motivation, technical specs, implementation path, and review stages. It also describes the ELIP lifecycle from a draft to final approval and execution by the Protocol Council, and touches on the supporting process (e.g., forum discussions, pull requests, timelock operations).
Key Components from the File Structure
• The “ELIPs” directory contains individual markdown files for each proposal. Each document is self-contained and follows a design proposal format.
• The “assets” directory holds additional media or support material related to some proposals.
• Files like “protocol-council-charter.md” and “template.md” provide governance instructions and templates for proposing changes.
• The top-level README summarizes the ELIP process, roles, and stages of review (draft, testing, final, approved, merged).
Main Elements
a. Core Proposal Documents:
• “ELIPs” as a central repository of proposals, with individual nodes for each proposal version (e.g., ELIP-001, ELIP-002, …).
b. Supporting Assets:
• “assets” folder, linking the media or resource files to the corresponding proposals.
c. Process Flow and Lifecycle:
d. Governance and Actors:
• Actors/components:
• Eigen Foundation and Eigen Labs (proposal management and technical oversight).
• Protocol Council (final review and decision-making).
• Operations Multisig (canceler role and execution oversight).
• External systems like the related core contracts repository (linked in README) and the forum (forum.eigenlayer.xyz) where discussions take place.
e. External Dependencies & Communication:
• Connections to external systems such as the GitHub pull request system and the on-chain timelock operations for executing approved proposals.
Architectural Patterns and Design Principles
• This repository follows a document versioning and review pattern often seen in decentralized governance systems.
• Separation of concerns: the documentation/artifact layer (ELIPs & assets) versus the governance flow (review, approval, and execution).
• That although this repository is information-centric, it acts as a coordination point interfacing with both on-chain processes (timelock and execution) and off-chain discussion (forum posts and PRs).