Skip to content

Add RFP-2025-04: Lean and Performant Libraries #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Add RFP-2025-04: Lean and Performant Libraries #7

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c638ffa
Retire spring, welcome summer
mishmosh Jul 18, 2025
70ce041
Create 2025-round-1-spring.html
mishmosh Jul 18, 2025
494fdb0
Add RFP #4
mishmosh Jul 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
170 changes: 170 additions & 0 deletions utility-grants/2025-round-1-spring.html
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,170 @@
<!doctype html>
<html lang="en" dir="ltr">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width">
<title>IPFS Implementation Fund</title>
<link rel="stylesheet" href="../fund.css">
<link rel="icon" href="data:image/svg+xml,<svg xmlns=%22http://www.w3.org/2000/svg%22 viewBox=%220 0 100 100%22><rect x=%220%22 y=%220%22 width=%22100%22 height=%22100%22 fill=%22%23fb2c09%22></rect></svg>">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" property="og:title" content="IPFS Implementation Fund">
<meta name="twitter:description" property="og:description" content="The IPFS Implementations Grants program was established in 2022 to advance the development, growth, and impact of the InterPlanetary File System (IPFS) project.">
<meta name="twitter:image" property="og:image" content="https://ipfsgrants.io/banner.png">
<meta name="twitter:image:alt" content="IPFS Implementation Fund in white on a bright red background">
<meta name="twitter:url" property="og:url" content="https://ipfsgrants.io/">
<meta property="og:site_name" content="IPFS Implementation Fund">
<meta property="og:locale" content="en">
<meta name="theme-color" content="#fb2c09">
</head>
<body>
<main>
<h1>IPFS <br>Implementations <br>Grants</h1>
<p>
The IPFS Implementations Grants program was established in 2022 to advance the development, growth, and impact
of the InterPlanetary File System (IPFS) project through a focus on developer choice and availability. We provide
financial support to projects and teams working on integrations, extensions, and new implementations that make
IPFS accessible to more developer communities across a variety of languages, platforms, and systems.
</p>


<h2>Spring 2025 Request for Proposals: Content-Addressed Data Tools</h2>
<p><i>Note: The Spring 2025 round is now closed.</i></p>


<p>The IPFS Implementations Fund supports a more open, resilient, and efficient web by funding implementations of the <a href="https://specs.ipfs.tech/">IPFS protocol</a>. It aims to broaden the reach and impact of the IPFS project by making content addressing and peer-to-peer networking more accessible across different platforms, programming languages, environments, and use cases.</p>
<p>Our Utility Grants program supports developers creating essential utilities, libraries, and tooling. Grants of $5,000-25,000 per project aim to fill critical tooling gaps and strengthen the foundations of an open and interoperable web.</p>
<p>For the Spring 2025 cycle, we seek proposals from qualified individuals or teams for the following:</p>


<h3>RFP #2025-01: CAR Archive Explorers and Utilities</h3>
<p>The CAR format (Content Addressable aRchives) makes data reliably portable by packaging up content with its cryptographic identifiers. This ensures the same data can be verified and used across different systems and platforms, making it a good building block for “credible exit” and data portability. Typically found in a file with a <code>.car</code> filename extension, you can think of them like TAR files that are designed for storing collections of content addressed data.</p>
<p>Originally created as a way to create stable documents from large or dynamic IPLD graphs (including those graphs that populate “virtual directories” of files added to IPFS), CAR files can now be found in IPFS-based systems, Storacha, ATProto, and other open source projects. With growing interest in data independence – moving large datasets between storage providers, backing up personal content from hosted services, and maintaining data integrity across the web – there's a growing need for accessible tools that help people create, inspect, and manage their own CAR files.</p>
<p>Currently, there is limited stand-alone tooling for the CAR format. Prior art includes <a href="https://docs.ipfs.tech/reference/kubo/cli/#ipfs-dag-import">kubo</a>'s <code>dag import</code> and <code></code>dag export</code> CLIs, <a href="https://github.com/hsanjuan/caribdis">caribdis</a>, and Bluesky’s <a href="https://github.com/bluesky-social/indigo/blob/main/cmd/goat/repo.go">goat</a>, but they are mostly embedded within larger app-specific libraries and not ergonomic to use outside of that context. Standalone tools include <a href="https://www.npmjs.com/package/ipfs-car">ipfs-car</a> and <a href="https://github.com/ipld/go-car">go-car</a>.</p>


<p>We are interested in tools that make CAR archives more useful and/or more usable. Command line tools, utility libraries, and browser-based explorers are equally welcome. Enhancements or extensions to existing tools or platforms are especially encouraged.</p>


<h3>RFP #2025-02: DASL Testing</h3>
<p>DASL (Data-Addressed Structures &amp; Links, pronounced "dazzle") is a small set of simple, standard primitives for working with content-addressable resources on today’s or tomorrow’s web. It is a strict subset of IPFS CIDs and IPLD, optimized for simplicity, HTTP, and longevity.</p>
<p>The DASL spec was published in December 2024, and is currently supported by <a href="https://dasl.ing/#how">9 implementations or tools</a>. Now, let’s test it. We are interested in proposals with two phases:</p>
<ul>
<li>First, authoring a set of tests and designing a few happy-path and failure test cases for DASL (specifically its <a href="https://dasl.ing/#spec">CID, dCBOR42, and CAR specs</a>).</li>
<li>Second, testing against real-world implementations in approximate conformance and working through spec changes and/or test changes towards a “minor version” that exhausts major corner-cases and ambiguities.</li>
</ul>
<p>Additional notes:</p>
<ul>
<li>Applicants should make sure that this works as a loop with the spec to clarify and improve it as needed, rather than slavishly follow it. The DASL authors will be available for discussion and collaboration.</li>
<li>Proposals should include a list of implementations (at least one ATProto-based) to test against, to ensure alignment of spec, test suite, and implementations.</li>
<li>See <a href="https://github.com/darobin/dasl.ing/issues/25">https://github.com/darobin/dasl.ing/issues/25</a> for prior discussion.</li>
</ul>


<h3>RFP #2025-03: Improving Data Utilities</h3>
<p>Recently, several new utilities, libraries, and tools have emerged for working with content-addressed data (CIDs, IPLD, DASL). We welcome these new contributions to the content-addressed ecosystem! We are interested in proposals to improve both longtime and emerging utilities.</p>
<p>The scope of work can range broadly, from technical improvements to docs, code examples, outreach, or education. This RFP is focused on active projects that show evidence of current usage and adoption (for example, Github stars, a variety of issue creators, a healthy dependency graph).</p>


<h2>How To Apply</h2>
<h3>Submission Process</h3>
<ol>
<li>Prepare your proposal document according to the requirements outlined below.</li>
<li><a href="https://docs.google.com/forms/d/e/1FAIpQLSfQXmZ-Iho7EHYwAv-j0RkEwG4xUcQRy0mtWQEyPhl4ld2jTw/viewform?usp=dialog">Submit your proposal</a> no later than <strong>Sunday, March 30, 2025</strong>.</li>
<li>Ensure all team members are available for a potential Q&amp;A call during the specified dates.</li>
</ol>


<h3>Proposal Document</h3>
<p>Please prepare a clear and concise proposal (no longer than 2 pages) with the following sections:</p>
<ol>
<li>Project Overview</li>
<li>Technical Design</li>
<li>User Feedback and Adoption Plan</li>
<li>Schedule and Budget</li>
<li>Qualifications of Team, including prior open-source work</li>
</ol>


<h3>Additional Information</h3>
<ul>
<li>License: Projects must be licensed under the MIT and/or Apache-2.0 licenses.</li>
<li>Duration: This program targets projects of 1-3 months. Exceptions will be considered on a case-by-case basis.</li>
<li>Contributions to existing projects:</li> If you are proposing to improve an existing project of which you are not a maintainer, please check with the maintainer(s) first. Your proposal should link to an issue or other artifact showing that you have discussed the proposed change with the maintainer, incorporated any feedback, and that they support and will be available to review your PRs.
<li>Project Communications:
<ul>
<li>Grantees are expected to publish an overview and introduction to their project upon completion. This can be on a personal blog or website, the IPFS Forum, or other public place.</li>
<li>Grantees will give a brief presentation at a virtual showcase in June. Depending on your proposed timeline, projects are not required to be completed at this time, but should have enough progress for a meaningful presentation.</li>
</ul></li>
<li>Maintenance Grant: An additional grant of 10% of the original award will be available to support a 12-month period of basic maintenance. This can include any activity to keep your project healthy, including but not limited to bug fixes, minor improvements, community support, responses to Github issues or PRs, docs, examples, and other educational content.</li>
</ul>


<h3>Important Dates</h3>
<ul>
<li>Informational Sessions (Virtual): <a href="https://lu.ma/14t7w2oy">March 12</a> &amp; <a href="https://lu.ma/gwpygczs">March 26</a>, 2025</li>
<li>Submission Deadline: March 30, 2025</li>
<li>Finalist Notification: April 7, 2025</li>
<li>Review Period: April 7 - April 21, 2025</li>
<li>Q&amp;A Calls with Finalists: April 17 - April 20, 2025</li>
<li>Grantees Acceptance Notification: April 23, 2025</li>
<li>Grantee Presentations (Virtual): June 25, 2025</li>
</ul>


<p>Thank you for your interest and good luck with your submission! For any questions, please contact <a href="mailto:utility-grants@ipfs.io">utility-grants@ipfs.io</a>.</p>


<h2>How to Contribute</h2>
<p>
This program is supported by Protocol Labs (2022-2025) and the Filecoin Foundation (2022). If your fund or foundation aims
to boost open-source IPFS adoption, consider
<a href="mailto:implementations-grants@ipfs.io?subject=Contributing%20to%20IPFS%20Implementations%20funding">joining as a funder</a>.
</p>


<h2>About</h2>
<p>
The IPFS Implementations Grants program is a cell of the <a href="https://openimpact.foundation/">Open Impact Foundation</a>,
a Liechtenstein charitable foundation. Our advisors are Michelle Lee, Juan Benet, and Dietrich Ayala (emeritus).
Thank you to Addie Wagenknecht, Matt Frehlich, and Patrick Kim.
</p>
<h2>Past awardees, in alphabetic order:</h2>
<ul>
<li>
<a href="https://www.3studio.online/">3S Studio</a>, for
<a href="https://blog.ipfs.tech/2022-11-15-3s-studio/">IPFS plugins for the Unreal and Unity gaming engines</a>.
</li>
<li>
<a href="https://brave.com/">Brave Browser</a>, for
<a href="https://brave.com/blog/nft-pinning/">automatic NFT backups</a> to a local IPFS node.
</li>
<li>
<a href="https://www.igalia.com/">Igalia</a>, for
<a href="https://blog.ipfs.tech/14-11-2022-igalia-chromium/">refactoring Chrome to support non-HTTP protocols</a>.
and
<a href="https://blog.ipfs.tech/2021-01-15-ipfs-and-igalia-collaborate-on-dweb-in-browsers/">other</a>
<a href="https://blogs.igalia.com/jfernandez/2023/06/20/secure-curves-in-the-web-cryptography-api/">improvements</a>
across 3 major browser engines for future IPFS compatibility
</li>
<li>
<a href="https://fission.codes/">Fission</a>, for the
<a href="https://fission.codes/blog/ipvm-computation-ipfs/">IPVM content-addressed computing</a>
protocol and implementation
</li>
<li>
<a href="https://littlebearlabs.io/">Little Bear Labs</a>, for
<a href="https://blog.ipfs.tech/2023-05-multigateway-chromium-client/">native support for verified IPFS requests in Chromium</a>.
</li>
<li>
<a href="https://n0.computer/">Number Zero</a>, for <a href="https://iroh.computer/">Iroh</a>, a new
IPFS-based toolkit for building distributed systems
</li>
<li>
<a href="https://github.com/Peergos">Peergos</a>, for
<a href="https://github.com/Peergos/nabu">Nabu</a>, a ground-up implementation of IPFS in Java and improvements to
<a href="https://github.com/libp2p/jvm-libp2p">jvm-libp2p</a>
</li>
</ul>
</main>
</body>
</html>
Loading