{"signature": "0x313c399f3a220753ea73bad33634b52669f0c864e13be067d277374fec8cd9d65e6b5c48cff9409c06a3f856bc3733569514587d0ca77af1ade6be2e61f9e0f81c", "application": {"round": "0xd2d99614321becd7cd0636715bbb4c94968e6271", "answers": [{"type": "email", "hidden": true, "question": "Email Address", "questionId": 0, "encryptedAnswer": {"ciphertext": "MlxD3PiTgrDnZ3xE78KFZaW/Lt5vhp8ZXHgl6vMo/K5NyDJJqfv4MQ6tEN4PFZZY", "encryptedSymmetricKey": "bb6a03d0a794646c6031375c21e2ffbb0697ebc5bc08a9123f8b5d98f22c0025ca8525d9272dc13e0b4be1c742f81218783b2821c4aeb4dfc0d9cea35e7a3c46ccc7c977ba11e9ded4a97c7780f4cbb1327aed2acd0d529b419769687d65a2b482384cb02cfe7c64c8269c098ae5ae7cf114000fedd2f99de7e50cf8b82a5954000000000000002023d2a3032340c493410dfc03c8d3a6effb9d30c9598d225d7c1e05618d456be3e5b2fa04d26e705fdbf81b4471103bb3"}}, {"type": "short-answer", "answer": "@peersky", "hidden": true, "question": "Telegram Handle", "questionId": 1}, {"type": "short-answer", "answer": "https://github.com/peeramid-labs/eds", "hidden": true, "question": "Project GitHub Repo", "questionId": 2}, {"type": "short-answer", "answer": "https://discord.gg/EddGgGUuWC", "hidden": true, "question": "Link to your Public Group Chat", "questionId": 3}, {"type": "short-answer", "answer": "Yes I did, I don't know how to get builder profile share link. They all are submitted from 0x2e8d906A63D15E110037DB42dD24FE69bEc4aFAf", "hidden": true, "question": "Have you participated in a previous Gitcoin Grants Round? If so, please name the rounds or link the builder profile associated with previous rounds.", "questionId": 4}, {"type": "paragraph", "answer": "The current landscape of smart contract distribution on the Ethereum network is fragmented and inefficient.\n\nServices like Ethereum Attestation Service (EAS), Aragon OSx, and others implement their own semantic versioning attempts.\n\nHowever, these solutions are not generalized, leading to a lack of uniformity and increased complexity.\n\nThis also results EIP712 built in versioning field largely underused.\n\nMoreover, projects generate numerous deployment artifacts that cannot be optimized in node memory because of built metadata affecting hashes.\n\nThis practice results in a significant increase in blockchain size for node operators, far beyond what is necessary.\n\nThe 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.\n\nEDS 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.", "hidden": true, "question": "Provide a brief overview of your tool, library, or framework. What specific problem or inefficiency in the development process does it address?", "questionId": 5}, {"type": "paragraph", "answer": "#### Reducing Development Barriers\n- **Factory Framework**: Developers can create a distribution and register it instead of writing their own factory, simplifying the development process.\n- **Plug-n-Play Installation**: Easy customization for any target platform, allowing developers to install and use distributions effortlessly.\n- **On-Chain GitHub**: Uses [ERC7744](https://eips.ethereum.org/EIPS/eip-7744) to refer to bytecode instead of location, simplifying code management.\n\n#### Improving Efficiency\n- **Reuse of Deployment Artifacts**: Reduces the number of needed deployment artifacts by allowing the reuse of existing packages.\n- **Semantic Versioning**: Built-in version control system allows developers to manage versions and avoid the complexity of upgradability patterns.\n- **Efficient Bytecode Usage**: Extensive reuse of the same bytecode reduces gas costs, increasing efficiency across the industry.\n\n#### Enhancing Security\n- **Security Oracles**: Allows the disconnection of vulnerable code from users instantly.\n- **User-Owned Upgradability**: Users can decide when to upgrade, increasing trust and reducing potential security risks.\n- **Isolated Contract Sets**: Baked-in runtime checks enable a trust chain between developers, distributors, and users, enhancing overall security.\n\nBy addressing these key areas, EDS significantly contributes to reducing development barriers, improving efficiency, and enhancing the security of Web3 projects.", "hidden": true, "question": "How does your project reduce development barriers, improve efficiency, or enhance the security of Web3 projects? Please provide specific examples or metrics if available.", "questionId": 6}, {"type": "paragraph", "answer": "### Current Usage and Support for Ethereum Distribution System (EDS)\n\n- **GitHub Stars**: 4 stars\n- **Forks**: 1 fork\n- **Watchers**: 4 watchers\n- **Open Issues**: 7 issues\n- **License**: MIT License\n\n### Feedback \n\n_Assaf (Ironblocks CTO):_ i absolutley love that and think that it's a great registry mechanism, i will definitly look into it more and share my thoughts_\n\n_Dimitry | SecurFi_: This looks very interesting and innovative!\n\nhttps://ethresear.ch/t/can-ethereum-distribution-system-reduce-disk-space-usage-enable-object-passing/20560 \n\n\n\n\n\nFor more details, you can visit the [EDS GitHub Repository](https://github.com/peeramid-labs/eds).", "hidden": true, "question": "Describe the current usage and support for your tool within the developer community. This could include GitHub stars, downloads, or testimonials from developers.", "questionId": 7}, {"type": "paragraph", "answer": "Our roadmap is to get it deployed and start getting usage feedback early  Q1 2025. \n\nOur development consists of a major milestone to develop major version migration system: \n\nhttps://github.com/peeramid-labs/eds/milestone/2 ", "hidden": true, "question": "Outline your project's roadmap and how the grant funds will be used to achieve your development goals.", "questionId": 8}, {"type": "paragraph", "answer": "0x5F997aAb4F6757FAa48e008faa599841947959F1", "hidden": true, "question": "For any project deploying smart contracts on blockchain networks, please list all your deployer addresses and their corresponding blockchain networks. Use this format for each entry: [deployer_address], [chain_id]—for example, 0x123abc..., 42161 (This represents a deployer address on the Arbitrum network). Please include a separate line for each unique deployer address and blockchain combination.", "questionId": 9}], "project": {"id": "0xd4427d0ffc2b8f58c4ef28410deed1158a7d5e405d6cd5bedb0487441d2ba452", "title": "Ethereum Distribution System", "logoImg": "bafkreidgazt4uywma7sb2ok7xmws5sqokbwtryzp7vmuvj35fnhdoflssm", "metaPtr": {"pointer": "bafkreihni3353iagvahpceyrvnxu2pazbsjwpvhgudvnpd44qx45wvvj64", "protocol": "undefined"}, "website": "https://github.com/peeramid-labs/eds", "bannerImg": "bafkreigrptkxzann6upc6lh5ragj6a2mb4m2zpoiw7xrrwh6hiz7nfteoy", "createdAt": 1723052779970, "userGithub": "peersky", "credentials": {"github": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..tbYwYYXjqVD2ThRoH5mkBOZbkUiIBbzHXw6flHgzx5n_7ZGLR2c8Wvcj5c7ifpV1_kVKm7BbG7aVHotMw4q0Cg", "type": "Ed25519Signature2018", "created": "2024-08-07T17:46:08.105Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2024-08-07T17:46:08.105Z", "expirationDate": "2024-11-05T17:46:08.105Z", "credentialSubject": {"id": "did:pkh:eip155:1:0x2e8d906A63D15E110037DB42dD24FE69bEc4aFAf", "hash": "v0.0.0:zCilqRLMJ+Zr/0dUufetkRFOmC7NMoQMXad5KHweg18=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextGithubOrg#peeramid-labs#61459744"}}, "twitter": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..crpw1I3TibKFrxsu0hp38nHwhWR1biMuvYDPZqJLNeet4RJ1WB5L9wfJ-cS_HuRUBMVPwV0yk3iabKzLkzwhCg", "type": "Ed25519Signature2018", "created": "2024-08-07T17:46:02.123Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2024-08-07T17:46:02.123Z", "expirationDate": "2024-11-05T17:46:02.123Z", "credentialSubject": {"id": "did:pkh:eip155:1:0x2e8d906A63D15E110037DB42dD24FE69bEc4aFAf", "hash": "v0.0.0:6kl0jXAyf0oPUpVFVR2mdnqmW/YnAPynu/LFvHt6Toc=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextTwitter#peeramid_labs"}}}, "description": "# Ethereum Distribution System\n\nThe Ethereum Distribution System (EDS) is an open and decentralized, fully on-chain distribution (factory) system for Ethereum smart contracts. \nUsing 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. \n\nSystem provisions for generic interfaces for distributors, developers and installers, each with their own responsibilities and constraints. \n\n### Problem Statement\n\nThe current landscape of smart contract distribution on the Ethereum network is fragmented and inefficient. \n\nServices like Ethereum Attestation Service (EAS), Aragon OSx, and others implement their own semantic versioning attempts.\nHowever, these solutions are not generalized, leading to a lack of uniformity and increased complexity.\nThis also results EIP712 built in versioning field largely underused.\n\nMoreover, projects generate numerous deployment artifacts that cannot be optimized in node memory because of built metadata affecting hashes.\nThis practice results in a significant increase in blockchain size for node operators, far beyond what is necessary. \nThe 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.\n\nEDS 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.\n\n\n## Use cases \n\n- **Factory Framework**: Instead of writing own factory, just write a distribution and register it\n- **Ship faster**: Reduce the number of needed deployment artifacts in order to ship your project. Re-using others packages instead!\n- **Security oracles**: Disconnect vulnerable code from your users in O(1)\n- **Semantic versioning with EIP712**: Instead of having to figure out \"what to write in EIP712 constructor\" just use built in version control system!\n- **User owned upgradability**: Get more user trust by alllowing them to decide when to upgrade\n- **Improve user UX**: Configure trust within instance or distribution, so that you'r users do not need to set allowances and issue permits anymore!\n-  **On-chain github**: Refer bytecode instead of location using ([ERC7744](https://eips.ethereum.org/EIPS/eip-7744))\n-  **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! \n\n\n![image](https://github.com/user-attachments/assets/52fa7028-177c-4de2-9259-3f883491a3d3)", "lastUpdated": 0, "projectGithub": "peeramid-labs", "projectTwitter": "peeramid_labs"}, "recipient": "0x65E5028dF322066e93A01C6fFA67739Eac6BF1dE"}}