metadata: {"signature": "0x96873cac4b5bd86ec3ecabbf3f56c7e6a02f29f592c3a140ab35f70acd0819323767fdc0928e1649ec1df51e75a4cc122b23488a32c694464c784b8d2a61bc571b", "application": {"round": "0xda3b55a9bcf58bb2d9f673836beab3ae47ca9184", "answers": [{"type": "email", "hidden": true, "question": "Email Address", "questionId": 0, "encryptedAnswer": {"ciphertext": "NrhUcLZz70STvHI71iIIPmLrJDyWBe1AmtkWhpkprL4=", "encryptedSymmetricKey": "17d72a5fab52326070fc0254100de949196d189834a60b2d713810a069314702deab12879b6d579df76bb79c07b3710333b996a99333e170542cffe5e17535b34f956bdfd36aa577888695c7c66387fd6c79ebc0dee34a6e481ace0521c5b2a4ec8845c8578090e51a3afe4844b63b2ba242083040bb60460bd0cada562345d0000000000000002018a2c7d4a712c799f8526b1c202abc74fa4e0e650866dfec5b69d071def2850fb5555e4e689a3aa120e680347e391b98"}}, {"type": "short-answer", "hidden": true, "question": "Telegram Handle We Can Use To Contact You(you can answer N/A)", "questionId": 1, "encryptedAnswer": {"ciphertext": "N6JjXRpBDvDKu2eB8NBwlwGK6cLLR6HZnFhqCtAAEAa4/4YRYKn8Y9KOBK5B+ZlS", "encryptedSymmetricKey": "12874d7fe9e67ff15e0d3543bd31cc457f2e0d20a13ae5d35373c5d927f23b2d87a45140283d7a7d5ed0fcc5ee772b07d124cfa573c8535433d440789459cc2ab79774cdba24786f458a8423d28ef279ec77119508a06d431bd13454fd8ab6a6f9939075788dfb3aa3bff102e9542c3757d072a8ada4c500b5df82487fc7efaa000000000000002045805c5974a0b02e1ea5664050ed0f68021d5cac90eb6181a7d96ab2bb5b99c72dd7dbea6452b889bdeaac3ac78fdeaa"}}, {"type": "link", "answer": "https://github.com/ethlimo", "hidden": false, "question": "Project GitHub Repo (Not Team Page): ", "questionId": 2}, {"type": "number", "answer": "3", "hidden": false, "question": "Total Team Size", "questionId": 3}, {"type": "paragraph", "answer": "Github: https://github.com/eth-limo sydmead.eth \nGithub: https://github.com/eth-limo cerealsabre.eth \nGithub:https://github.com/Dwiib  ", "hidden": false, "question": "List the Github Handles and Wallet Addresses of Each Team Member (e.g. owocki - 0x123, kbw  - 0x456):", "questionId": 4}, {"type": "paragraph", "answer": "https://twitter.com/cerealsabre\nhttps://twitter.com/eth_limo", "hidden": true, "question": "Social profiles (Twitter, Farcaster, Lens, etc.) of other main team members publicly associated with the project (N/A for solo founders): ", "questionId": 5}, {"type": "link", "answer": "https://discord.com/invite/zf8NxW94rB", "hidden": false, "question": "Link to your Public Group Chat (e.g. Discord or Telegram)", "questionId": 6}, {"type": "paragraph", "answer": "https://docs.google.com/document/d/10h7SEwr1ANJFwzWDsdfWc67nFjprMafWZZVKkUGrf0Q/edit?usp=sharing", "hidden": false, "question": "If you've participated in past grant rounds, please share any new updates or milestones from the prior months (N/A if you haven\u2019t participated previously). ", "questionId": 7}, {"type": "address", "hidden": true, "question": "If you participated in past grant rounds using a different project payout wallet address, please share it here:", "questionId": 8}, {"type": "paragraph", "answer": "https://docs.google.com/document/d/10h7SEwr1ANJFwzWDsdfWc67nFjprMafWZZVKkUGrf0Q/edit?usp=sharing", "hidden": false, "question": "Where should we look to see the impact of your project? Please provide links to public websites and/or the latest values for key metrics you track privately. This might be used in future impact reports", "questionId": 9}, {"type": "paragraph", "answer": "800,000", "hidden": false, "question": "Total Prior Funding for the project in USD", "questionId": 10}, {"type": "checkbox", "answer": ["Grants"], "hidden": false, "question": "Which of the following funding sources do you have? Check all that apply", "questionId": 11}, {"type": "number", "answer": "32", "hidden": false, "question": "How old (in Months) is the project?  ", "questionId": 12}, {"type": "multiple-choice", "answer": "North America", "hidden": false, "question": "Location/Region where the project is based ", "questionId": 13}, {"type": "multiple-choice", "answer": "Yes", "hidden": true, "question": "Have you read and confirmed your grant abides by the Program General Eligibility Policy? ", "questionId": 14}, {"type": "short-answer", "answer": "No", "hidden": true, "question": "Are you applying for any other OSS rounds in GG20? (Reminder: you can only be accepted into one) ", "questionId": 15}, {"type": "paragraph", "answer": "ETH.LIMO is a free and public ENS gateway that enables users to access Ethereum-native dApps and content. Since September 2021, we have been responsible for the maintenance, operation, and ongoing development of the eth.limo gateway. We\u2019ve dedicated efforts to enhance the performance and reliability of our service, incorporating new features based on valuable feedback from the community. The eth.limo gateway is the default resolver for app.ens.domains and numerous other ENS projects. The ENS ecosystem and community operates best when all projects align and synergize their respective strengths. The eth.limo project extends broad name resolution for ENS, allowing builders to focus on their work and develop a user base. This positive feedback loop benefits both builders and the eth.limo gateway, driving increased traffic and engagement.", "hidden": false, "question": "How does your project significantly contribute to the Ethereum network\u2019s infrastructure, addressing foundational needs and innovative solutions to current challenges?", "questionId": 16}, {"type": "paragraph", "answer": "Zero-configuration is required in order to access or host a site or dApp on ETH.LIMO, making ETH.LIMO an excellent no-cost solution for providing Web 2.0 access to any project. \nThe LIMO project enforces strong origin isolation policies for all resources by default. Projects accessed through ETH.LIMO automatically receive security hardened browser headers and all client data is encrypted with TLSv1.3 (default) or TLSv1.2 using the latest ciphersuites. All log data is fully anonymized, which prevents the ability to uniquely identify any single user.", "hidden": false, "question": "How does your project promise to elevate the Ethereum ecosystem, particularly in enhancing privacy, interoperability, and/or user experience?", "questionId": 17}, {"type": "paragraph", "hidden": false, "question": "Anything else you'd like to share about your project, previous work, or other project affiliations? Anything you'd like to add that may help in determining project eligibility?", "questionId": 18}, {"type": "multiple-choice", "answer": "Yes", "hidden": true, "question": "Would you like to opt-in to future messages from Gitcoin for updates, information, and/or interviews? ", "questionId": 19}, {"type": "multiple-choice", "answer": "No", "hidden": true, "question": "Would you like to opt-in to us sharing your information with select third-parties for investment opportunities? ", "questionId": 20}], "project": {"id": "0xdaf7588714a0008d7ee1fe317a87c80a6f64cb8881c016a1d87bc704eb3b115f", "title": "eth.limo", "logoImg": "bafkreico7g6kvn62eil32momfk7qjrcnrsdmhalvsz6iy4bhncov4i5d64", "metaPtr": {"pointer": "bafkreigero36mf7z73d7rqozdrrqud2genwwqj4h7kibqk2622qpijoasi", "protocol": "undefined"}, "website": "https://eth.limo", "bannerImg": "bafkreif635dr3ajnljk43vrm3xeyqgv5mkflab7cdnmuhtapc36djfjfrq", "createdAt": 1673371881638, "userGithub": "eth-limo", "credentials": {"github": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..Avuv6pTly_Y4tTGTqRkbOGyP2E5Ol9yO-SjabDP84HoVk7Aft5QZa4-TcphWgK_n168Sm60pbJM-uwHq3hIiAA", "type": "Ed25519Signature2018", "created": "2024-04-03T15:27:20.172Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2024-04-03T15:27:20.172Z", "expirationDate": "2024-07-02T15:27:20.172Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xB352bB4E2A4f27683435f153A259f1B207218b1b", "hash": "v0.0.0:inQf6AVWNaH++Kr4rdccfpdE4iFXQiU5yoSvpbwwvoI=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextGithubOrg#ethlimo#91141622"}}, "twitter": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..EVUEwni_HZQ2-EMtQjIPi7FNASrKT57Y0eQgqtAs5Ix3Z6DhHuh5TraxJDLCyxjuo3vkRDPQH4IhBBgh-ylfCw", "type": "Ed25519Signature2018", "created": "2024-04-03T15:23:46.481Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2024-04-03T15:23:46.480Z", "expirationDate": "2024-07-02T15:23:46.480Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xB352bB4E2A4f27683435f153A259f1B207218b1b", "hash": "v0.0.0:bov4zfo5mwbvDqTxnB7dYM6P3BkCCOXpx+Bwm/QeuYE=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextTwitter#eth_limo"}}}, "description": "### **eth.limo is a privacy-preserving ENS gateway, enabling users to access Ethereum-native dApps and content. LIMO represents a shift in dweb adoption by providing an alternative means of accessing ENS resolvable domains.**\n![eth.limo visual](https://substackcdn.com/image/fetch/w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fbucketeer-e05bbc84-baa3-437e-9518-adb32be77984.s3.amazonaws.com%2Fpublic%2Fimages%2Fb73ad984-fa36-4819-9b83-0e81dfd0121f_1167x937.png)\n\u2705 eth.limo supports every ENS compatible storage layer! Users can utilize IPFS, Arweave and Swarm contenthashes.\n\n\u2705 CCIP-Read for L2 and off-chain lookups are also supported!\n\n\u2705Emoji and unicode domains supported! [\ud83d\ude02\ud83d\ude02\ud83d\ude02.eth.limo](https://xn--g28haa.eth.limo/)\n\n\u2705 Limo now supports on-demand @ensdomains subdomain certificates!\nWhat does this mean? You can now automatically issue a certificate for ENS subdomains without requesting one from us! \nHow does this work? Once you submit an HTTP request for your name (i.e. app.myname.eth. limo), we'll attempt to issue the certificate in the background. Usually this process takes 1-2m and during that time you might need to keep refreshing the page in your browser. Once the certificate has been issued you'll be able to visit your subdomain on eth.limo.\n\n\n\u2705 DNS over HTTPS (DoH) Resolver DNS over HTTPS (DoH) resolver. We now offer an easy to use DNS resolver for ENS domains. The DoH resolver can be integrated with applications for native ENS resolution, or even your browser! We feature both JSON and DNS wire format responses with DNSLink support. This means you can configure your local IPFS client to resolve ENS domains directly from us with the following command:\n`ipfs config --json DNS.Resolvers '{\"eth.\": \"https://dns.eth.limo/dns-query\"}'`\nFor example if you then requested vitalik.eth, a DNS query would be constructed (https://dns.eth.limo/dns-query?name=vitalik.eth&type=TXT) which would return:\n>dnslink=/ipfs/QmQhCuJqSk9fF58wU58oiaJ1qbZwQ1eQ8mVzNWe7tgLNiD/\nWhich would instruct your IPFS client to retrieve the CID above. Consult our documentation for implementation details.\n[Documentation](https://github.com/ethlimo/documentation)\n\n\u2705 Chauffeur - Run a local infrastructure stack for resolving ENS domains.  https://github.com/ethlimo/chauffeur\n\n\u2705HTTP Object Caching - Improving content retrieval times is always a priority for the eth.limo team. After several weeks of careful testing we have fully implemented static content object caching, globally for all eth.limo resolved names. This means that we will cache content retrieved from IPFS and save it for later retrieval. The result being much faster page load times for all static content.\n\n\u2705Base32 and Base36 Encoding for IPFS/IPNS - We have updated both the eth.limo gateway and our DNS over HTTPS service to explicitly use Base32 encoding for IPFS CIDs and Base36 for IPNS peer IDs.\n\n\u2705LIMO takes public gateway services a step further by enforcing strong privacy guarantees such as never logging IP addresses or engaging in TCP fingerprinting. Limo now actively blocks FLoC (Federated Learning of Cohorts). This is a Google developed algorithm that tracks and correlates users based on their browsing history. FLoC enables advanced fingerprinting capabilities and greatly undermines online privacy and anonymity.\n\nCheck out our latest substack article -\nhttps://ethlimo.substack.com/p/ethlimo-updates-overview-and-a-luxurious\n\n\n\ud83c\udf892024 Future endeavors\ud83c\udf89\n\nWe\u2019re busy working on the following updates & new features:\n\u25aa\ufe0fMulti-region CDN deployment (better performance and reliability)\n\u25aa\ufe0fENS resolution manager app\n\u25aa\ufe0fContinued work on ENS native DNS resolver in anticipation of the .eth TLD being welcomed into the ICANN gTLD namespace (limo-web3-dns)\n\u25aa\ufe0fGateway as a Service implementation of the eth.limo API\n\u25aa\ufe0fgno.limo for Gnosis ENS implementation \n\u25aa\ufe0fImproved IPv6 support\n\u25aa\ufe0fLight client fallback from Alchemy RPC API\n\u25aa\ufe0fResearch on HTTP Header Standards for ENS dWebsites\n\nHTTP headers are tricky to get right, even more so in decentralised environments. Certain browser features (like SharedArrayBuffer) can only be used in a \u201cSame-Origin\u201d context, which requires the use of certain server side headers to be returned to the client. With this in mind, we are investigating the best way for users to define their own header and value pairs at the ENS record level. This would be a new standard for ENS HTTP gateways and permit users to fully leverage all available browser features irrespective of how the content is accessed (i.e. gateway or web3 native browsers).\n\n\u25aa\ufe0fdAppNode Package\nWe plan to release a dAppNode package that will allow users to run a local instance of the eth.limo service at home. Similar to Chauffeur, a dAppNode deployment has the added benefit of serving all clients on a local network.\n\n\nWhy do we need ETH.LIMO?\n\n\u2714\ufe0fCore internet infrastructure is becoming increasingly centralized and as such, several existential threats have emerged that undermine the principles of an decentralized, open and free internet:\n\n\u2714\ufe0fLack of non-commercial infrastructure\n\n\u2714\ufe0fOpacity of terms of service agreements and moderation policies\n\n\u2714\ufe0fProliferation of proprietary browser extensions which require centralized services \n\n\u2714\ufe0fThe erosion of the \u201ccommons\u201d and \u201cpublic space\u201d\n\n\u2714\ufe0fWeb 3.0 adoption is still nascent\n\n\u2714\ufe0fMost browsers cannot natively access ENS/IPFS\n\n\nFor end users, this means a limited selection of poor quality services that increasingly resemble a cable TV package. Accessing the dWeb can be a frustrating experience. For dApp developers, this leads to a limited selection of platforms and services in addition to lost revenue.\n\nThe LIMO project brings additional resiliency to dApps by providing an alternative means of access as a public good. As the decentralized web continues to grow, it is imperative that community projects facilitate the transition from Web 2.0 to Web 3.0.\n\nThe LIMO project is organized around the following founding principles:\n\n1. Operate ETH.LIMO as a public good.\n\n2. Establish community governance and oversight.\n\na. Provide support and technical guidance for builders and users.\n\n3. Work towards building a truly decentralized ENS/IPFS gateway service and global CDN.\n\n4. Build a world-class developer platform for dweb sites, including integrated analytics reporting and traffic management deployment tooling for commonly used web2 patterns such as A/B testing, canary and blue/green deployments.\n\n5. A commitment to open source software and the advancement of web3 through education, best practices, evangelism, and public accessibility.\n\n\n[Documentation](https://github.com/ethlimo/documentation)\n[Discord](https://discord.gg/zf8NxW94rB)\n ", "lastUpdated": 0, "projectGithub": "ethlimo", "projectTwitter": "eth_limo"}, "recipient": "0xB352bB4E2A4f27683435f153A259f1B207218b1b"}}