{"signature": "0x67a46184c6c624f98f479f2bb1b48cc32253e72195c72067940a7bc41d0bedda772a954dffae6a03be66b38366a13a39710324aa712d43fa35223151b9b499b41b", "application": {"round": "0xd2d99614321becd7cd0636715bbb4c94968e6271", "answers": [{"type": "email", "hidden": true, "question": "Email Address", "questionId": 0, "encryptedAnswer": {"ciphertext": "rA/0HuIcjeFW2jek3ibzzdrngvreqmgX1NeKz5mdLkW8TU0/mBMQxPC3edaUx8oW", "encryptedSymmetricKey": "c4a8ff7d3310b566bac8b1044b4ed5e89e053fb5bc86be363b58af10852bfd674ba8dfa0061464c95754e104a5b60515ec49fab78f7be91218149d2d61ccee91b1ce3cebfd9351542051ae07bf2b36594b66fd3e22c41fa42e352ec3143c1d96efc70adcb775c4d307c31187d738a2a051c9bd122db51e04495f16193bf932360000000000000020c305b5421a1aae1e10e896aff061c8ca5128c77831d5892d9e310088993c806687b503bbb6ed7c21df55486b9fc9418b"}}, {"type": "short-answer", "answer": "yaaybee", "hidden": true, "question": "Telegram Handle", "questionId": 1}, {"type": "short-answer", "answer": "https://github.com/router-protocol/tangled", "hidden": true, "question": "Project GitHub Repo", "questionId": 2}, {"type": "short-answer", "hidden": true, "question": "Link to your Public Group Chat", "questionId": 3}, {"type": "short-answer", "answer": "No", "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": "Tangled is a frontend library intended to help developers integrate 7+ chain types on the user interface in a jiffy. It supports EVM, Cosmos, Sui, Solana, Ton, Bitcoin and Near.\n\nTangled is type safe and an extremely consistent interface to work with the underlying chains.\n\nTangled utilises the best SDKs from each ecosystem for the underlying primitives of chain interactions. Viem, Wagmi for Ethereum, Mysten's Dapp-kit for Sui and so on.", "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": "Cross-chain applications hit integration bottlenecks while integrating different chain types. The learning curve to integrate different wallet SDKs is very steep and littered with blockers. \n\nThere are many different packages that are developed by each ecosystem and they have different interfaces.\n\nEach cross-chain dapp would need to implement these interfaces again and again.\n\nIt's very crucial to support as many chains as possible in today's world. And Tangled helps reduce this overhead.\n\nFor a multi-chain dapp, the integration time for all 8+ chain types would be around 2 months. With Tangled, it comes down to just 2 days.", "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": "Tangled is in active use at Router Protocol. It will soon serve all active users of the Nitro bridge.\n\nTangled is also being integrated in the ecosystem applications built on top of Router Protocol to integrate different chain types on the interfaces.\n\nThe SDK has started to rake in massive time savings while integrating and maintaining wallet connections on the ecosystem applications. \nLive example (older version) - https://poc.routerintents.com/", "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": "Grant funds will be utilised to seek more developer bandwidth for the active development of the SDK.\n\nOne of the most interesting scopes is account abstraction. There is a very real need to create multi-chain social sign ups and abstract away the wallets and provide a single wallet gateway to all chain types.\n\nUI kit for facilitating chain abstracted interactions is on the task list as a separate package. This can be used by any cross-chain dapp to provide a seamless experience. \nScopes include designing and development of the UI kit.\n\nThere is also infra cost associated with using certain portfolio services and account abstraction providers. Grants will largely help cover these costs. This will provide an initial launch pad to experiment with different services and build with what works best.", "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", "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": 9}], "project": {"id": "0xf29bd37df548df4ad299eecbd30ccfb0d6f1affe8175b335bab40eb5dec28226", "title": "Tangled3 \ud83e\udea2", "logoImg": "bafkreiepww76jhysdtprrzq7ly72hrj2lygoarxeckk6x6aqmq26zo6sjq", "metaPtr": {"pointer": "bafkreiaefbvbyoqg2vrmgce5c47uya4sdvdsm735sntlnexgw4ntod5kna", "protocol": "undefined"}, "website": "https://www.npmjs.com/package/@tangled3/react", "bannerImg": "bafkreicgc34ocdsmgxmd47umvypqxgdikmkqadxnjlp7wpw5g2u7oxyle4", "createdAt": 1729094929399, "userGithub": "router-protocol", "credentials": {"github": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9.._zf5k8f7B0wmh4ECY3GPa66-kIXf152RQRunTFSV0WYWXrnuKpiZlhrhJ1ZNRn5Nxku5isXQQQwlgtGxEcAJDQ", "type": "Ed25519Signature2018", "created": "2024-10-16T16:08:26.826Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2024-10-16T16:08:26.826Z", "expirationDate": "2025-01-14T16:08:26.826Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xA97D308c27cECa01E4a422693B73d238340CfcF4", "hash": "v0.0.0:8cEOH9pfG66iHL/edS7Zq3SrG/IPMEicjJxKNwFNNzY=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextGithubOrg#router-protocol#111138421"}}, "twitter": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9.._xzRXG293BtBaX6n9Oj12XsE73aNHrGWUcTD1Xke1hX4-sVyYL_0Yd8_1jE6HpBpPwBOHbfaVYhRVdT7wQKtBg", "type": "Ed25519Signature2018", "created": "2024-10-29T12:52:33.896Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2024-10-29T12:52:33.896Z", "expirationDate": "2025-01-27T12:52:33.896Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xA97D308c27cECa01E4a422693B73d238340CfcF4", "hash": "v0.0.0:O7tNYJkrTHPTrWfFd3N4J9R06CsOnJkRRWdUiBL5Q4c=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextTwitter#routerprotocol"}}}, "description": "# Today\nWeb3 has evolved into a multi-chain ecosystem with a plethora of non-EVM and countless EVM chains.\n\n# Problem\nCross-chain applications hit integration bottlenecks while integrating different chain types. The learning curve to integrate different wallet SDKs is very steep and littered with blockers. \n\nThere are many different packages that are developed by each ecosystem and they have different interfaces.\n\nEach cross-chain dapp would need to implement these interfaces again and again.\n\nIt's very crucial to support as many chains as possible in today's world. And Tangled helps reduce this overhead.\n\n# Solution\nTangled is a frontend library intended to help developers integrate 8+ chain types on the user interface in a jiffy. It supports EVM, Cosmos, Sui, Tron, Solana, Ton, Bitcoin and Near.\n\nTangled is type safe and an extremely consistent interface to work with the underlying chains.\nIt utilises the best SDKs from each ecosystem for the underlying primitives of chain interactions. Viem, Wagmi for Ethereum, Mysten's Dapp-kit for Sui and so on.\n\n# Current Status\nRouter Protocol is building and actively using Tangled to provide the multi-chain utopia for the bridges and cross-chain dapps built in it's ecosystem.\n\nThe SDK has started to rake in massive time savings while integrating and maintaining wallet connections on the ecosystem applications. \nLive example (older version) - https://poc.routerintents.com/\n\n# Future\nChain abstraction dapps will be able to create their own SDKs on top of the interfaces that Tangled provides.\n\nWe also support Walletconnect modals by default. Account abstraction is one of the next steps to enable chain-less experiences with Tangled!\n\nUI kit for facilitating chain abstracted interactions is on the task list as a separate package. This can be used by any cross-chain dapp to provide a seamless experience. \nScopes include designing and development of the UI kit.\n\nThere is also a very real need to create multi-chain social sign ups and abstract away the wallets and provide a single wallet gateway to all chain types.\n\nWe are looking for a grant to support the development of Tangled and to make it a more robust and developer-friendly tool for the community.\n", "lastUpdated": 0, "projectGithub": "router-protocol", "projectTwitter": "routerprotocol"}, "recipient": "0xA97D308c27cECa01E4a422693B73d238340CfcF4"}}