Ethereum Distribution System

The Ethereum Distribution System (EDS) is an open and decentralized, fully on-chain distribution (factory) system for Ethereum smart contracts. Using EDS enables developers to publish and reuse each other's code in a trustless manner. Built-in system for semantic versioning, managing versions and combining into higher level distributions allows developers to avoid using upgradability patterns, instead relying on version control.

System provisions for generic interfaces for distributors, developers and installers, each with their own responsibilities and constraints.

Problem Statement

The current landscape of smart contract distribution on the Ethereum network is fragmented and inefficient.

Services like Ethereum Attestation Service (EAS), Aragon OSx, and others implement their own semantic versioning attempts. However, these solutions are not generalized, leading to a lack of uniformity and increased complexity. This also results EIP712 built in versioning field largely underused.

Moreover, projects generate numerous deployment artifacts that cannot be optimized in node memory because of built metadata affecting hashes. This practice results in a significant increase in blockchain size for node operators, far beyond what is necessary. The absence of a trusted ecosystem to exchange functional code pieces (distributions) exacerbates the problem, making it difficult to manage and verify deployment artifacts efficiently and blocks novel applications built on ethereum, which trust each other by-design.

EDS aims to address these challenges by providing a generalized, decentralized, and fully on-chain distribution system. By leveraging semantic versioning, efficient factory frameworks, and robust security measures, EDS seeks to create a more streamlined and secure environment for distributing and managing smart contracts on the Ethereum network.

Use cases

• Factory Framework: Instead of writing own factory, just write a distribution and register it
• Ship faster: Reduce the number of needed deployment artifacts in order to ship your project. Re-using others packages instead!
• Security oracles: Disconnect vulnerable code from your users in O(1)
• Semantic versioning with EIP712: Instead of having to figure out "what to write in EIP712 constructor" just use built in version control system!
• User owned upgradability: Get more user trust by alllowing them to decide when to upgrade
• Improve user UX: Configure trust within instance or distribution, so that you'r users do not need to set allowances and issue permits anymore!
• On-chain github: Refer bytecode instead of location using (ERC7744)
• Better Monitize your apps and services: As your application becomes distributed, and wrapped, you may directly build in payment systems and subscription models on-chain!