metadata: {"signature": "0x4ec0cc0d5e84f0bd525c5983040bafa104fb8498a400b43462c020805027348a5d6cb9f393a14c39d273d5b7f6a85044166b6f87c8451c266c7b345b9a1564271b", "application": {"round": "0xda3b55a9bcf58bb2d9f673836beab3ae47ca9184", "answers": [{"type": "email", "hidden": true, "question": "Email Address", "questionId": 0, "encryptedAnswer": {"ciphertext": "QdlR69umbzqwLfhIZkth728fq/NcdMGpo0LijhnJNXQyboBPh3Vak/ykPEVf3Etz", "encryptedSymmetricKey": "d64b3598ca69837e80c3cf945cdd122b47c80b66e346d8f9125da4fbe2a0e86e80993dc8bd10ad7ea9df07df54557c16dde11096146042f2467e2fec29fff21172986cf3e7bb12e8ca57684f9ffc328041a53896b96453e9945ac32bd2715baa4538f771a4d1bd7ecb4f19e2b6533f0961c385a74f92cb22c552c62f4a2919b50000000000000020c2fdc7e10878d73a182c0985b8dc933b4211eefd666bd943a9e95900f7ed957066c01c0bb917dd318783861cb4e90990"}}, {"type": "short-answer", "hidden": true, "question": "Telegram Handle We Can Use To Contact You(you can answer N/A)", "questionId": 1, "encryptedAnswer": {"ciphertext": "kIeg3eUIO2gsmKXCQ2k2SHurXpFYs3dS4gh92jT8zZo=", "encryptedSymmetricKey": "1210ff2e5ecb3ecbe23e805d101c9e7d9c800c8f3ddd89df5e1f9035e0d438a5c9ac2ab70a57c81f025fca84c5f6b606ec73387b248d7a80d66ecd81365cb9f5ea9f3188794ced8a15d92aad9f8ab3ae17299637fe4f69baa48e8453eca44aabdb15c73e1fe9f5684aca979e4650365cec222d958d5b0c7d3f2093e5b132358f0000000000000020c85b25bc8efecdaa413277a99cf62da8fd4cc477f5d232d3b005998156ca386c20f263db094e6e2f1943974d874c65b5"}}, {"type": "link", "answer": "https://github.com/mbcse/CrossSync", "hidden": false, "question": "Project GitHub Repo (Not Team Page): ", "questionId": 2}, {"type": "number", "answer": "1", "hidden": false, "question": "Total Team Size", "questionId": 3}, {"type": "paragraph", "answer": "mbcse - 0xAa81f641d4b3546F05260F49DEc69Eb0314c47De", "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": "N/A", "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", "hidden": false, "question": "Link to your Public Group Chat (e.g. Discord or Telegram)", "questionId": 6}, {"type": "paragraph", "answer": "NA", "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", "answer": "", "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": "We are still in the Building phase", "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": "0", "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": "6", "hidden": false, "question": "How old (in Months) is the project?  ", "questionId": 12}, {"type": "multiple-choice", "answer": "Asia", "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": "I am building a truly interoperable protocol that allows any chain to talk and call contracts on any chain. Interoperability is still an issue in the web3 space. Although many solutions have emerged in the market trying to solve this problem there is still a long way to go. Reaching small and new chains as quickly as possible is still a problem to solve. I feel my protocol solves this big problem and I think it will be a great success.", "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": "In the growing world of blockchain, handling different chains poses a challenge, making it tough for users, especially developers. Cross Chain Messenger Protocols aim to solve this, but face issues with limited chain support, varied fees, syntax differences, and more. To address these challenges, CrossSync Protocol provides a common gateway for multiple interoperability protocols. Users interact with the CrossSync Protocol Gateway, simplifying the process. It converts payloads for different messenger protocols, making it user-friendly and eliminating integration complexities.\n\nBenefits:\n\nA common relayer fee simplifies developer integration. Combining various protocols into one enables cross-chain messaging on almost all chains. Auto Routing ensures the lowest fees for cross-chain calls. Modular design allows easy integration of any protocol. Benefits users and developers in terms of UI, fees, ease of use, integration, etc. Operates on-chain through secure smart contracts.Why We are Novel/Better than alternatives: There is no direct protocol that does this. No one has focused on cross-contract calls. There are dex and bridge aggregators which do this but they don't focus on message/liquidity passing as such and also they are limited to chains due to their architecture. They are also more focused on off-chain decision-making for bridging things whereas we are focusing fully on on-chain decision-making and message passing. Our Focus is to build a protocol that is as simple as connecting to any chain that launches tomorrow and also provides an aggregated gateway to all the messengers in the ecosystem, such that as a developer you are not constrained to use a single messenger on a network. We also provide a unified interface to all messengers so if you are using a single messenger and want to switch to another messenger at any time, you can do it easily by just switching the routeId. All the input parameters will remain the same! For Example: Let's say your dapp is using Axelar and you are available on 10 chains that Axelar supports but suddenly a new super chain comes into the market that has its messenger from optimism to super chain only but is not available to be connected to other chains as axelar is not supporting that. Now how will you do cross-contract calls to this new super chain? You have to find different messengers that do that which is time-consuming and code change is required or maybe it's even not available. But with crosssync, as soon as superchain messenger is deployed we will connect it in crosssync. Now You can send cross-contract calls from polygon to superchain in this way: polygon to Optimism using Axelar and Optimism to Superchain using native messenger. To do all this You don't need to integrate those individual messengers in your code or figure out things on your own as crosssync will handle all this through manual or automatic routing in the contract. I feel we will be the protocol using which others can build their own cross-chain dexes, apps, bridges, etc in the least time which will bring interoperability to a new level in the web3 ecosystem. Also, our focus is a smart contract protocol and not the SDK kind of protocol. We want to give a fully on-chain solution!", "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", "answer": "We have been the winner at the EthOxford Hackathon and have received good interest from blockchains. We are already live on testnet and building at a fast pace. You can checkout our website and documentation for further details. \n", "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": "Yes", "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": "0x5dea290c069603280365429f571d5f23f0679dce4f29a6d88fce02e9c4463ff4", "title": "CrossSync Protocol", "logoImg": "bafkreigcowufhglmbvmwxqoqmxqajif3ilr45iqr2epej2cofstloj6bqu", "metaPtr": {"pointer": "bafkreigfpyzue66yngnvoi5m2lwurchzcchcfbyk7q3zkcw5ocu5hkafsm", "protocol": "undefined"}, "website": "https://crosssync.network", "bannerImg": "bafkreih5nif6eh3jfgm7mxzte6hw3kv5e5ledrecj7xzd3lsha4hmvyzte", "createdAt": 1714116834559, "userGithub": "mbcse", "credentials": {}, "description": "A cross-chain messengers aggregator protocol that provides a common interface to connect to multiple messaging protocols to send cross-chain contract calls and liquidity across many chains\n\nVideo Demo: https://www.loom.com/share/dfed8249187e4150b8041c296999b19f?sid=531f7130-722b-4038-83f7-ea4b71cf7941\n\n\n# The problem we are trying to solve :\n\nIn the ever-growing world of blockchain, with new blockchains popping up all the time, we must make sure we can easily work across different chains and handle the increasing demands for new blockchains and liquidity. If data and money are spread out on many chains without an easy way to connect them, it makes things tough for users, especially for developers and dApps working in the blockchain space.\n\nWe've got these things called Cross Chain Messenger Protocols to help with this. They let us call smart contracts on different chains and move funds around in a decentralized way. They've done a good job solving the interoperability problem, but there's still a hitch \u2013 scalability and availability of these protocols on the chains that dApp developers want to use. Confused? Let me break it down.\n\nThere are a bunch of interoperability protocols out there like Hyperlane, Connext, Axelar, ChainLink CCIP, and more. But here's the issue:\n\n1. **Limited Chain Support:**\n    - Not all protocols support every chain, leading to a fragmented landscape where specific interoperability solutions cater to only a subset of chains.\n2. **Varied Fee Structures:**\n    - Divergent fee models across protocols introduce complexities for users. Some protocols impose high fees on certain networks, while others maintain lower fees, creating inconsistency and unpredictability.\n3. **Syntax and Implementation Disparity:**\n    - Each protocol employs a distinct syntax for contract implementation, adding a layer of complexity for developers. This diversity complicates the integration process and demands specialized expertise.\n4. **Payment Currency Disparities:**\n    - Protocols differ in the payment currencies they support, further complicating cross-chain transactions. This diversity necessitates adjustments in payment methods, leading to increased friction and potential errors.\n5. **Limited Accessibility:**\n    - The protocols are not readily available for seamless incorporation into various chains, making the integration process cumbersome and time-consuming for developers.\n\nThere are other problems too, but these make things hard for developers and users. Imagine a dApp that wants interoperability on chain1, chain2, and chain3. The problem is Hyperlane only works on chain1, Connext on chain2, and Axelar on chain3. So, if a developer wants interoperability features in their smart contracts, they have to deal with all three services, which are different in how they work, the fees they charge, and how you pay. That makes it pretty much unusable for them. That's where we come in \u2013 we're working on a solution to fix this mess.\n\n# The Solution (CrossSync Protocol)\n\nTo address these challenges and provide a common Interface and Gateway for interacting with multiple messaging interoperability protocols CrossSync has been made, With this users only need to implement and interact with CrossSync Protocol Gateway. They have to call the sendMessage function of the CrossSync Gateway and specify the route ID for sending messages, for example, 1 for Using Axelar, 2 for CCIP, 3 for Connext, 4 for Hyperlane, and 5 for Wormhole, and so on\u2026. CrossSync Protocol handles the rest and converts all the payload into the payload required for the messenger protocol, you don't have to bother about different kinds of domain IDs, chain names, etc. Additionally, users no longer have to implement individual interfaces to receive messages on the destination chain. A single receiveMessage function is all they need to integrate for receiving the payload.\n\n### Benefits\n\n- A common relayer fee makes it easy for developers to integrate any of these protocols with ease and less hassle.\n- Many of these protocols are available on different kinds of chains, ones you combine all of them into the same protocol, you can have cross-chain messaging available on almost all chains now\n- With Auto Routing users get the lowest fees for cross-chain calls if many protocols are available on the same chain.\n- The design of this protocol has been kept modular, any protocol can be integrated easily by just deploying an implementation contract for it.\n- This protocol benefits users as well as developers from the perspective of UI, Fees, ease of use, ease of integration, etc.\n- Completely on-chain and handled by smart contracts in a secure way\n- With the introduction of the CSYNC token, users can pay fees in this single common token, get low fees discount and developers just need to implement this single token for handling fee payments\n\n\nWe have been Winners at Multiple hackathons like ethoxford, ethglobal, etc. We have received great feedback from the community and chains!", "lastUpdated": 0, "projectGithub": "mbcse/CrossSync", "projectTwitter": "crosssync"}, "recipient": "0x381eA45d53d9d306855153cbc58d04cBe5723A5e"}}