Update README.md

README.md

@@ -1,11 +1,30 @@
 # Ethereum Distribution System
 
-The Ethereum Distribution System (EDS) is a open and decentralized, fully on-chain distribution system for Ethereum smart contracts.
-EDS maps functionality, expressed as bytecode, to on-chain locations, using a global non-permissioned singleton indexer contract. Using this index, EDS provides developers with a built in system for [Semver](http://semver.org/) versioning, managing multiple versions and distribution of their smart contracts. System provisions for generic interfaces for distributors, developers and installers, each with their own responsibilities and constraints.
+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](http://semver.org/), 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. 
+
+## Why is EDS Important?
+
+- It enables developers to efficiently reuse each other's code, effectively reducing the number of needed deployment artifacts in order to get projects going. 
+
+- It enables distributors to act as a source of trust for users, packing the global permissionless domain of available packages into a distributor entity specific instantiation that may be parametrized in predictable ways.
+
+- It enables security firms to attest for security of deployed code and revoke such signatures in O(1) for every instance in case of vulnerabilities. 
+
+- It enables users (smart accounts) to manage their trusted distributions and distributors while delegating runtime security as needed. 
+
+- It paves the door for a better, more performant Ethereum ecosystem, provisioning software abstracted features such as objects passing between same distribution instances. (e.g., don’t need approve for ERC20 transfers between such)
 
 ## Overview
 
-This system acts as generalized and efficient factory which is designed in one-fits-all principle. It achieves this by referring bytecode instead of location, enabling code queries by bytecode hash (`address.codehash`). Developers when interacting with the system first must register their bytecode to the code indexer contract. After that, they may create a distribution contract that links multiple various required code hashes in one place. If the developer wants to manage multiple versions of the same resource, they can create a repository contract to add own index on top of global. In order to provide functionality to users, developers may pack their code to Distributions, which have hardcoded instructions for instantiation. Such hardcoded bytecode later can be itself consumed by Distributors, which are responsible for determining custom instantiation arguments and initializer interfaces that will wrap the Distribution. Finally, Installers are used by end-users to manage resources and permissions
+This system acts as generalized and efficient factory which is designed in one-fits-all principle. It achieves this by referring bytecode instead of location, enabling code queries by bytecode hash (`address.codehash`). Developers when interacting with the system first must register their bytecode to the code indexer contract which is defined by [ERC7744](https://eips.ethereum.org/EIPS/eip-7744).
+After that, they may create a distribution contract that links multiple various required code hashes in one place. 
+
+If the developer wants to manage multiple versions of the same resource, they can create a _Repository_ contract to add own index on top of global. 
+
+In order to provide functionality to users, developers may pack their code to _Distributions_, which have hardcoded instructions for instantiation. Such hardcoded bytecode later can be itself consumed by Distributors, which are responsible for determining custom instantiation arguments and initializer interfaces that will wrap the Distribution. Finally, Installers are used by end-users to manage resources and permissions
 
 ### Key Features
 
@@ -75,3 +94,22 @@ pnpm test # Run tests
 Examples of distributions usage can be found in [src/distributions](src/distributions) directory.
 Examples of repositories usage can be found in [src/repositories](src/repositories) directory.
 Examples of distributors usage can be found in [src/distributors](src/distributors) directory.
+
+Larger example of usage can be found in [Rankify project repo](https://github.com/peeramid-labs/contracts)
+
+
+## Support || Contribute
+
+If you want to support this project, please click "sponsor" button, or see our gitcoin page: 
+https://explorer.gitcoin.co/#/projects/0xd4427d0ffc2b8f58c4ef28410deed1158a7d5e405d6cd5bedb0487441d2ba452
+
+
+
+You can reach out us on Discord: https://discord.gg/EddGgGUuWC 
+
+
+
+
+
+
+