metadata: {"signature": "0x5a7c6becfd229e0ed9ad57d8f2db045d3439fcfae538a6a6ae6cc7f5bc24d16d6db9f643a14e8ba88f015822c96f352c07c910b9e553a58ef4e45621f2e286181b", "application": {"round": "0x2d4d59757d5a7c3c376fc47b9f4501c347b9654d", "answers": [{"type": "email", "hidden": true, "question": "Email Address", "questionId": 0, "encryptedAnswer": {"ciphertext": "GNXc9mWYD66YGmeRLCXvwDw+vhlrHb9zSR1olFNjWHY=", "encryptedSymmetricKey": "c11fddd40345dfabf7caca854c3f82238bcc75d8517f1f649b0fa33574ca66cade37f61c25be573a8e935a26b76bf00f06102e962a169211cce87ef4adcb9b45caa32c52ee4ba00bf65b1370a81e9102fa5975e3cba612913be487f07394bfaf8ed096dc9fd5cb270c8c2faf7dffce08ef5f45b6495afc66b99980a9c83191c7000000000000002089770c6264901d0c17ec85a3afa895de3f6e8f04b2ace3e0c7be4bc2f6c5bce64b1e2faa37896401affb597fe4404f8c"}}, {"type": "short-answer", "answer": "ethdotlimo", "hidden": true, "question": "Telegram Handle", "questionId": 1}, {"type": "short-answer", "answer": "https://github.com/eth-limo", "hidden": true, "question": "Project GitHub Repo", "questionId": 2}, {"type": "short-answer", "answer": "https://discord.gg/8bbmPZUw", "hidden": true, "question": "Link to your Public Group Chat", "questionId": 3}, {"type": "short-answer", "answer": "Yes, we've been participating in various gitcoin rounds since at least late 2021, some include Ethereum Ecosystem rounds, Web 3 OSS, Web3 Infrastructure, ENS side rounds and MASK side rounds.", "hidden": true, "question": "Have you participated in a previous Gitcoin Grants Round? If so, please name the rounds or link the builder profile to prior rounds.", "questionId": 4}, {"type": "paragraph", "answer": "Here is a google doc that details some metrics and what we've achieved recently: https://docs.google.com/document/d/10h7SEwr1ANJFwzWDsdfWc67nFjprMafWZZVKkUGrf0Q/edit", "hidden": true, "question": "How does your project contribute significantly to the Ethereum network's infrastructure? Please provide specific examples and metrics if available.", "questionId": 5}, {"type": "paragraph", "answer": "Please see the attached article that we wrote earlier this year: https://ethlimo.substack.com/p/ethlimo-everything-youve-wanted-to ", "hidden": true, "question": "Describe any pioneering development work in your project, particularly in enhancing privacy, interoperability, or user experience.", "questionId": 6}, {"type": "paragraph", "answer": "Currently accessing dWebsites (Decentralized Websites)  is not an easy task for the average user. The content can be stored on various storage protocols such as IPFS, Arweave and Swarm. The average user is not running multiple nodes and able to access this content. eth.limo acts as a bridge to web3 enabling the average user to access decentralized content from any browser without special software or technical knowledge.", "hidden": true, "question": "What specific problems or challenges in the Ethereum ecosystem does your project address? How does your solution improve upon existing alternatives?", "questionId": 7}, {"type": "paragraph", "answer": "Here's a link to some recent achievements and our some of our future roadmap plans. https://discuss.ens.domains/t/eth-limo-update/19707\n\nPublish some interesting WASM tools we\u2019ve been developing internally to allow self-hosted serverless functions for ENS domains.\n\nContinue improvements of eth.limo and eth.link\n\nRelease an MVP of our in-browser, resolution service worker app that performs trustless IPFS content verification.", "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": "LIMO takes public gateway services a step further by enforcing strong privacy guarantees such as\nnever logging IP addresses or engaging in TCP fingerprinting. Limo now actively blocks FLoC\n(Federated Learning of Cohorts). This is a Google developed algorithm that tracks and correlates users\nbased on their browsing history. FLoC enables advanced fingerprinting capabilities and greatly\nundermines online privacy and anonymity.\n", "hidden": true, "question": "How does your project contribute to the decentralization and security of the Ethereum network?", "questionId": 9}, {"type": "paragraph", "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]\u2014for 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": 10}], "project": {"id": "0xdaf7588714a0008d7ee1fe317a87c80a6f64cb8881c016a1d87bc704eb3b115f", "title": "eth.limo", "logoImg": "bafkreico7g6kvn62eil32momfk7qjrcnrsdmhalvsz6iy4bhncov4i5d64", "metaPtr": {"pointer": "bafkreib4bsu34ee2lp4estjpqk7k4nlcpqoj3evs3sl3m2jyxxe7xxeufe", "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\nCheck out our recent articles!\nhttps://ethlimo.substack.com/p/ethlimo-everything-youve-wanted-to\nhttps://ethlimo.substack.com/p/ethlink-is-now-powered-by-ethlimo\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\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\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"}}