metadata: {"signature": "0x12ff904016281fb30d822679ae32d6499fb6b36b73c45557000a96c7bd05eca0365a1371057aa55dc293c4f8c7031adbf0aa7e0ec5ef7776e94ac7f0952123191b", "application": {"round": "0xc1cffd1845deee83ab44cae123738a854593bcd2", "answers": [{"type": "checkbox", "answer": ["Core Infrastructure", "Developer Tooling", "dApps & Apps"], "hidden": false, "question": "How does your project contribute to the advancement of the Arbitrum ecosystem?", "questionId": 0}, {"type": "paragraph", "answer": "This work can help deploy & distribute apps more securely for a numerous users ", "hidden": true, "question": "Describe your previous work or plans related to the Arbitrum ecosystem. How does your project strengthen Arbitrum's foundational infrastructure, improve developer efficiency, or accelerate the adoption of novel applications?", "questionId": 1}, {"type": "paragraph", "answer": "We are heavily reliant on cheap gas :) ", "hidden": true, "question": "If applicable, describe how your project leverages Stylus or Arbitrum Orbit Chains. What unique capabilities or use cases does this enable?", "questionId": 2}, {"type": "paragraph", "answer": "We are pushing for two new ERCs that indicate our expertise under context of this project: \n\nhttps://github.com/ethereum/ERCs/pull/542\nhttps://github.com/ethereum/ERCs/pull/543", "hidden": true, "question": "Describe your team's expertise in your chosen focus area within the Arbitrum ecosystem. Include relevant experience, publications, or past projects.", "questionId": 3}, {"type": "short-answer", "answer": "https://gap.karmahq.xyz/project/ethereum-distribution-system", "hidden": true, "question": "Please provide a link to Karma GAP, where you are tracking and reporting on milestones.", "questionId": 4}, {"type": "paragraph", "hidden": true, "question": "List any contract addresses with the associated network(s), EOAs, or deployer addresses your project has deployed.", "questionId": 5}, {"type": "paragraph", "answer": "This project is result of further work on Rankify project that received gitcoin grant in GG20 previously, however this is TOTALLY new code which was not part of that grant directly. ", "hidden": true, "question": "Have you received any previous grants or support for your work in the Arbitrum ecosystem? If so, please provide details and estimated funding amounts.", "questionId": 6}, {"type": "dropdown", "answer": "Yes", "hidden": true, "question": "Please confirm that you have read and agree to comply with the ethical standards outlined in the eligibility criteria, including Gitcoin's Quid Pro Quo policy (https://support.gitcoin.co/gitcoin-knowledge-base/gitcoin-grants/general-questions/what-is-our-quid-pro-quo-policy)", "questionId": 7}, {"type": "paragraph", "answer": "None", "hidden": true, "question": "Do you have any potential conflicts of interest to disclose? If yes, please provide details.", "questionId": 8}, {"type": "paragraph", "answer": "This is public good stuff. ", "hidden": true, "question": "Would you like to share anything else about your project, team, or vision for the Arbitrum ecosystem that wasn't covered in the previous questions?", "questionId": 9}], "project": {"id": "0xd4427d0ffc2b8f58c4ef28410deed1158a7d5e405d6cd5bedb0487441d2ba452", "title": "Ethereum Distribution System", "logoImg": "bafkreidgazt4uywma7sb2ok7xmws5sqokbwtryzp7vmuvj35fnhdoflssm", "metaPtr": {"pointer": "bafkreigo2zccw2xdjcdcefy7hlqnlp6y5aflreztmijestokcs3kpfa34y", "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 a open and decentralized, fully on-chain distribution system for Ethereum smart contracts.\nEDS 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.\n\n## Overview\n\nThis 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\n\n### Key Features\n\n- **Verifiable:** Stateless distribution components are easily verifiable by anyone through their bytecode.\n- **Permission-less:** Anyone can deploy distribution components without requiring permissions.\n- **Inclusive:** Can accommodate already deployed on-chain functionality.\n- **Versionable:** [Semver](http://semver.org/) based versioning can be applied to manage resources.\n- **Plug-n-Play:** Installation procedures,easily customizable for any target platform are provisioned.\n- **Secure:** Isolated contract sets and baked-in runtime checks enable trust chain between developers, distributors and users.\n- **Efficient:** Extensive reuse of the same bytecode reduces gas costs, increasing efficiency across the industry.\n\n![image](https://github.com/user-attachments/assets/52fa7028-177c-4de2-9259-3f883491a3d3)\n\n### Key Components\n\nSystem components are broken down into four domains: Permission-less, Developer, Distributor and User. Each domain has its own set of contracts and interfaces, which are designed to work together to provide a seamless experience for developers and users.\n\n#### Permission-less Domain\n\n##### CodeIndex\n\nA stateful, permissionless contract allowing anyone to register associations between bytecode and its on-chain location. Any smart contract may be indexed by `CodeIndex` based on its bytecode.\nProposed `CREATE2` implementation with deterministic address : `0xc0d31D6A64D1BE49867158ed3c25152D240b5c0B`\n\n##### `Distribution`\n\nInterface for contracts that allow specific mechanics of instantiation of referred bytecode identifiers in the `CodeIndex`. It may be using different methods for instantiation, yet it is ultimately referred by it's bytecode hash and instantiation methods kept non-parametric, to promote hardcoding of instantiation logic by the distribution creator, ultimately making any distribution a unique part of code ecosystem.\nIt also allows distribution creators to associate own metadata with the distribution, such as URIs defined in [ERC-190](https://eips.ethereum.org/EIPS/eip-190) or [ERC-2678](https://eips.ethereum.org/EIPS/eip-2678)\n\n#### Developer Domain\n\n##### Repositories\n\nRepositories are interfaces provided for stateful, permissioned contracts allowing developers to manage resources and versions. Such repositories may return any kind of source code reference, including system-internal used ones, like `IDistribution`. It allows developers to increment versions according to [Semver](http://semver.org/) as well as implement version requirements lookup for the clients.\n\n##### Non-Stateless Distributions\n\nAny implementation of Distribution interface mentioned in the Permission-less Domain, that is stateful is considered as a Developer Domain component. It is possible in principle, yet will be used only for specific use-cases, where stateful distribution is required and will require distribution users to use direct location addressing, effectively excluding it from the global index system.\n\n#### Distributor Domain\n\n##### Distributor\n\nStateful, permissioned contract interface for managing distributions. It allows distributors, who may act as trusted source for many, to have their own index of trusted distributions coupled to any, parametric, initialization logic that they might need. This is a first point on instantiation chain that allows to configure distribution after it's been instantiated.\n\n##### Version Distributor\n\nSame as Distributor, but with additional functionality to manage versions of distributions. It allows to manage multiple versions of the same distribution and to provide version requirements lookup for the clients. Distributor may change the version of the repository, effectively disabling, in one go, every outdated version instances from operating in the system.\n\n#### User Domain\n\n##### Installer\n\nStateful, permissioned contracts for managing permissions and accessing targets from multiple distributors. Allows end-users to manage trusted sources for their installations.\n", "lastUpdated": 0, "projectGithub": "peeramid-labs", "projectTwitter": "peeramid_labs"}, "recipient": "0x65E5028dF322066e93A01C6fFA67739Eac6BF1dE"}}