Mirrored from filpgf.io — ProPGF Batch 3 (Karma program 1479, application 6a319aca13ef2aeed7ce0d97, status: pending). Contact details redacted; canonical application lives on filpgf.io. 1.1 Project Name DotSwarn 1.2 Project Github https://github.com/libp2p/universal-connectivity 1.4 Team Lead/Point of Contact Kritika Agrawal 1.5 Category [ "RFP 1 - Customer-facing products built on Filecoin" ] 1.6 Open Source Status Fully Open Source 2.1 Project Summary DotSwarm is a production-grade C# / .NET peer for the libp2p universal-connectivity ecosystem, paired with the first real-world application demo — a decentralized supply chain tracking system — built on top of it. The libp2p universal-connectivity repository currently showcases cross-language P2P connectivity in Go, Rust, TypeScript, and Nim. C# and .NET — used by millions of enterprise developers in banking, healthcare, logistics, and manufacturing — have no peer. DotSwarm fills this gap by delivering a fully interoperable dotnet-peer using NethermindEth/dotnet-libp2p, connecting to all existing UC peers via TCP, QUIC, and WebTransport. On top of this foundation, DotSwarm builds a decentralized supply chain tracking demo: four .NET nodes (manufacturer, warehouse, shipper, retailer) gossip real-time cargo events to each other via GossipSub — no central server, no single point of failure. Every cargo event is stored as an immutable, content-addressed record on Filecoin, creating a tamper-proof audit trail with a CID per event. A live dashboard displays cargo status and Filecoin CIDs in real time.This grant does two things simultaneously: it closes the .NET gap in the libp2p ecosystem, and it demonstrates — for the first time in any UC language — that libp2p is production-ready for enterprise real-world applications beyond chat demos. 2.2 Who does this work support? [ "Application Builders", "Application Users", "Network Infrastructure" ] 2.3 Total Funding Requested (USD) 30000 2.4 Milestones & Budget [ { "title": "Milestone 1 — C# dotnet-peer in UC with TCP + QUIC + GossipSub", "description": "The NethermindEth/dotnet-libp2p library exists but has no presence in the libp2p/universal-connectivity repo. This milestone adds a /dotnet-peer folder to UC — a fully working C# peer that connects to Go, Rust, JS, and Nim peers via TCP and QUIC transports, joins the GossipSub chat topic, and sends/receives messages across language boundaries.", "dueDate": "2026-08-25", "fundingRequested": "$5,000", "completionCriteria": "Completion Criteria:\n1. /dotnet-peer directory created in libp2p/universal-connectivity with a working C# project using NethermindEth/dotnet-libp2p.\n2. dotnet-peer connects to bootstrap.libp2p.io and joins the universal-connectivity GossipSub topic.\n3. Verified cross-language message exchange: C# peer sends a message visible to Go peer and vice versa.\n4. TCP and QUIC transports working and documented in the UC transport compatibility table.\n5. PR opened and merged (or ready for review) in the official libp2p/universal-connectivity repository.\n6. README for /dotnet-peer with setup and run instructions." }, { "title": "Milestone 2 — WebTransport implementation in dotnet-libp2p", "description": "WebTransport is currently missing from NethermindEth/dotnet-libp2p (marked help wanted). Without it, the C# peer cannot connect to browser-based JS peers — a critical gap for enterprise .NET backends that need to communicate directly with web clients. This milestone implements WebTransport in dotnet-libp2p and enables it in the dotnet-peer, making C# the third UC language (after Go and JS) to support browser connectivity.", "dueDate": "2026-12-12", "fundingRequested": "$9,000", "completionCriteria": "Completion Criteria:\n1. WebTransport transport layer implemented as a new protocol package in NethermindEth/dotnet-libp2p.\n2. dotnet-peer connects to the browser-based JS peer in UC via WebTransport — verified end-to-end.\n3. Transport table updated: TCP QUIC WebTransport \n4. PR submitted to NethermindEth/dotnet-libp2p upstream.\n5. Integration test: C# node and browser JS node exchange GossipSub messages via WebTransport.\n6. Documentation added to dotnet-libp2p docs for WebTransport usage." }, { "title": "Supply Chain 4-node demo with GossipSub", "description": "This milestone builds the first real-world application demo in the entire libp2p universal-connectivity ecosystem — across any language. Four .NET console apps represent supply chain participants:\nmanufacturer-node (creates cargo events), warehouse-node (receives and logs arrivals), shipper-node (broadcasts in-transit updates), and retailer-node (confirms delivery). All four gossip cargo events to each other P2P via GossipSub in real time — no central server,\nno broker, no database.", "dueDate": "2027-01-31", "fundingReques …[truncated] 3.1 Impact pathway Output: DotSwarm adds a production-grade C# peer to libp2p/universal-connectivity — the first .NET implementation in the ecosystem — and ships the first real-world application demo (supply chain tracking) built on UC in any language. Every cargo event in the demo generates a verifiable paid storage deal on Filecoin Calibration testnet. Outcome: The .NET developer community — the largest enterprise backend ecosystem — gains a working, documented path to build Filecoin-connected P2P applications. Supply chain companies running .NET (SAP, Oracle Dynamics, Microsoft Dynamics shops) can see a direct reference implementation for their use case. WebTransport implementation unblocks browser connectivity for all future .NET libp2p applications. Impact: Every cargo event creates a paid Filecoin deal (Objective 1, direct). The .NET onramp brings a massive new developer segment into the Filecoin ecosystem (Objective 3, direct). WebTransport upstreamed to dotnet-libp2p improves core infrastructure for all .NET Filecoin clients (Objective 2, indirect). 3.2 Verification metrics | Metric | Target | |---|---| | dotnet-peer PR merged in UC repo | ✅ by M1 | | Transports working (TCP, QUIC, WebTransport) | 3/3 by M2 | | WebTransport PR merged in dotnet-libp2p | ✅ by M2 | | 4-node supply chain demo running locally | ✅ by M3 | | Filecoin deals created per demo run | ≥20 verified CIDs by M4 | | Dashboard live at public URL | ✅ by M5 | | Tutorial blog post published | ✅ by M5 | 3.3 References Manusheel Gupta — Maintainer, GitHub: github.com/seetadev Discord: manusheel#3075 Luca Pisani — Maintainer GitHub: github.com/acul71 Discord: lucap#5517 Anubha Maneshwar — Coordinator, PLDG (Protocol Labs Dev Guild) LinkedIn: linkedin.com/in/anubhamane Discord: anubha_maneshwar#6873 4.1 Monthly Operating Burn [ "< $10K (basic solo operation or part-time team)" ] 4.2 What % of total team monthly burn depends on this grant? As a solo open-source developer, the majority of the project's development time and infrastructure costs are expected to be funded through this grant. Approximately 90% of the project's monthly operating budget would depend on grant funding during the development period. 4.3 If this grant is not awarded, what happens? If this grant is not awarded, the project will likely proceed at a significantly slower pace and in a reduced scope. As a solo developer, I would need to prioritize paid work and other commitments, which would delay implementation of the C#/.NET peer, WebTransport support, and the Filecoin-integrated supply chain demonstration. The grant would enable dedicated development time, faster delivery of milestones, upstream contributions to dotnet-libp2p and universal-connectivity, and comprehensive documentation for the broader ecosystem. Without funding, I would still aim to contribute to the ecosystem, but development would be incremental and several planned features may be postponed or scaled back. In particular, the WebTransport implementation and the Filecoin storage integration are the components most likely to be delayed without grant support due to their complexity and development effort requirements. 4.4 Core Team Kritika — Project Lead & Sole Developer Responsible for architecture, implementation, testing, documentation, Filecoin integration, dashboard development, and upstream contributions to dotnet-libp2p and libp2p/universal-connectivity. Relevant experience includes C#/.NET development, distributed systems, peer-to-peer networking, open-source software development, and blockchain/Filecoin ecosystem research. The project is currently being executed as a solo open-source effort. Any external feedback or code reviews will be obtained through the open-source community and maintainers of the relevant repositories. 4.5 Has your team received a ProPGF grant or funding from PLFIF before? [ "Yes" ] 5.1 Key risks & dependencies 1. WebTransport complexity — it is missing from dotnet-libp2p for a reason. Mitigation: start with a minimal implementation, coordinate with Nethermind maintainers via their open issues. 2. dotnet-libp2p is still in beta — APIs may change. Mitigation: pin to a stable preview version, track upstream changes weekly. 3. Solo developer risk. Mitigation: all code MIT-licensed and open source from day one; milestone-based payouts mean partial delivery is compensated. 4. Filecoin deal-making API maturity on Calibration testnet.Mitigation: abstract storage behind a swappable interface; target Calibration for all milestones. Objective 1 Direct Objective 2 Indirect Objective 3 Direct