metadata: {"signature": "0xdc916815766f487dde0222cf6b0d75486162342c25951c85a62a08382e6677207af91e725b7cc438596c14128e9721fe8d5bdef502fba515793ec6ea4e4113ef1b", "application": {"round": "0xda3b55a9bcf58bb2d9f673836beab3ae47ca9184", "answers": [{"type": "email", "hidden": true, "question": "Email Address", "questionId": 0, "encryptedAnswer": {"ciphertext": "A3BZM3eXfIr5ZS2AXz099WS0vmKfX/L1h+85I27t6AKopM4s/QfOnCmMUm9ZAcnR", "encryptedSymmetricKey": "5a016278a815cab1b2669e1750d5c2748210117697047225353e906a70c9aa3d47c614aad0aa272cf2661801fc04fb1616bbb9f84ef9af8b1175cf6187157d1a9bdb74a0f4715af87d1675cdb7c03c7dff80c67467618781d720e0aa6391d3a4de1e6e68e0e9b36b29a696fcb4c0089a186cdaebd011a232e8ee3e772240b93c0000000000000020ba5a59e6ac8eac2748436b83f2d993a4b0a3c5bff2f9079f0cddee1c6c1352f31a7a8bcaec698505cfa8ee6931233ab7"}}, {"type": "short-answer", "hidden": true, "question": "Telegram Handle We Can Use To Contact You(you can answer N/A)", "questionId": 1, "encryptedAnswer": {"ciphertext": "YKXTPdtLVaJ4NzLfO5EBUeTltwfg0xPVBllaT1sMhfI=", "encryptedSymmetricKey": "85df2b18699920759e8430ac953ced2daf50c04bf3180c2f16d959bfbec0d49de4da766e2d4d11a3273eb4919f03cd08fa4fd0ae66d194b6944656f91e3f1684114b740fea01d53ec4a14243a58bb8a88eb62bd3e17ffecec39cedbd6654bc88b094609fb75835418e87071b3e1459b183e6ec7e2ef0f11261941640f3ec0a950000000000000020aa494faa93c2b30f20748785b2c5956c2532c09837bb384a6e9771ff3c1c0eebcec303780a7e02442ca12bab3e8031b5"}}, {"type": "link", "answer": "https://github.com/libp2p/go-libp2p", "hidden": false, "question": "Project GitHub Repo (Not Team Page): ", "questionId": 2}, {"type": "number", "answer": "5", "hidden": false, "question": "Total Team Size", "questionId": 3}, {"type": "paragraph", "answer": "marcopolo, sukunrt, achingbrain, p-shahi, yiannisbot - 0xFb90943018928cBF18e6355629A250928Ca6Be02", "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/yiannisbot", "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": "N/A", "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": "github.com/libp2p/go-libp2p, github.com/libp2p/js-libp2p, github.com/libp2p/rust-libp2p", "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": "These libp2p implementations team have been part of Protocol Labs up until the beginning of 2024 and has been supported by Protocol Labs ever since it was conceived.", "hidden": false, "question": "Total Prior Funding for the project in USD", "questionId": 10}, {"type": "checkbox", "hidden": false, "question": "Which of the following funding sources do you have? Check all that apply", "questionId": 11}, {"type": "number", "answer": "60", "hidden": false, "question": "How old (in Months) is the project?  ", "questionId": 12}, {"type": "multiple-choice", "answer": "Somewhere in the Metaverse", "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": "As of 2024-04-17, js-libp2p powers ~2.6% of the network via Lodestar nodes, go-libp2p powers ~30% percent via Prysm nodes, and rust-libp2p powers ~42% via Lighthouse nodes according to https://monitoreth.io/nodes.\n\nAs of September 15, 2022, libp2p has been powering the Ethereum mainnet and as of 2024-04-17 secures the Ethereum market cap of $355 B (not including any other networks).", "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": "libp2p offers a wide range of protocols and capabilities for Ethereum and other networks. The Beacon Chain makes use of the following libp2p protocols: the TCP transport protocol for connection establishment, mplex and yamux for multiplexing messages, Noise for data encryption, multistream select for protocol multiplexing, and GossipSub as the PubSub mechanism for data transfer/message passing. Clients like Lighthouse and Prysm are also moving to adopt the QUIC transport.\nlibp2p's Gossipsub, which is the primary protocol used for message and block propagation in the  Beacon Chain. It is responsible for timely and correct delivery of messages that will be included in the next block, making sure that misbehaving peers are not delaying propagation of important messages and no forks happen due to delayed message delivery or malicious behavior.\nInterplanetary  Shipyard continues to strengthen these libp2p implementations and their protocols for the Ethereum community.", "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": "The total libp2p team size is 5. We\u2019re providing the GH handles, Ethereum addresses and twitter handles of the team leads.", "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": "0x875513364d1d850b4df01c7bcac7751979f4d72a33686027ff62a66ef25a1e4d", "title": "Interplanetary Shipyard: go-libp2p, js-libp2p, rust-libp2p", "logoImg": "bafkreih4tvlgg6hn7pswcmq6snwbv5z5ls4bbbeecpxey2xv55fdev2kye", "metaPtr": {"pointer": "bafkreihhro75umuihsz32p2zp2kbwgny3j5gsspopbw35o3tec5seb5mmy", "protocol": "undefined"}, "website": "https://github.com/libp2p/go-libp2p", "createdAt": 1713569564573, "credentials": {}, "description": "Infrastructure Impact:\n\nThe libp2p networking stack is the core of hundreds of L1/L2 chains, including Ethereum, Filecoin, Polkadot, Optimism, etc., as well as numerous other decentralized applications.\nThe team at Interplanetary Shipyard is responsible for the feature development and maintenance of three popular libp2p implementations:  js-libp2p (github.com/libp2p/js-libp2p), go-libp2p (github.com/libp2p/go-libp2p), and rust-libp2p (github.com/libp2p/rust-libp2p).\n\nThese 3 implementations together power >=75% of the Beacon Chain i.e. the Ethereum network\u2019s consensus mechanism.\nAs of 2024-04-17, js-libp2p powers ~2.6% of the network via Lodestar nodes, go-libp2p powers ~30% percent via Prysm nodes, and rust-libp2p powers ~42% via Lighthouse nodes according to https://monitoreth.io/nodes.\n\nAs of September 15, 2022, libp2p has been powering the Ethereum mainnet and as of 2024-04-17 secures the Ethereum market cap of $355 B (not including any other networks).\nFor more information on the history of the libp2p project and Ethereum please see: https://blog.libp2p.io/libp2p-and-ethereum/.\n\nAdditionally, well over 250k IPFS p2p nodes participate in the IPFS DHT: https://probelab.io/ipfs/kpi/\n\n\nEngagement in Pioneering Development:\n\nlibp2p offers a wide range of protocols and capabilities for Ethereum and other networks. The Beacon Chain makes use of the following libp2p protocols: the TCP transport protocol for connection establishment, mplex and yamux for multiplexing messages, Noise for data encryption, multistream select for protocol multiplexing, and GossipSub as the PubSub mechanism for data transfer/message passing. Clients like Lighthouse and Prysm are also moving to adopt the QUIC transport.\n\nlibp2p also has Gossipsub, which is the primary protocol used for message and block propagation in the  Beacon Chain. It is responsible for timely and correct delivery of messages that will be included in the next block, making sure that misbehaving peers are not delaying propagation of important messages and no forks happen due to delayed message delivery or malicious behavior.\nInterplanetary  Shipyard continues to strengthen these libp2p implementations and their protocols for the Ethereum community.\n", "lastUpdated": 0, "projectGithub": "libp2p", "projectTwitter": "ipshipyard"}, "recipient": "0x53DCAf729e11022D5b8949946f6601211C662B38"}}