Improved developer tooling

Demo of a basic HTTP-based IPFS implementation that can find and fetch blocks from existing IPFS peers in a language with poorer IPFS and libp2p support (e.g. Python)

Depends in practice on Trustless HTTP retrieval (and serving) being available in kubo by default
May also require kubo to also allow serving data over HTTP (or HTTP over libp2p)
May also involve work on delegated routing / IPNI

We've decided to leave the criteria open, but have a simple litmus test, we will decide on a CID that these implementations need to be able to fetch. If you can fetch it, you're golden. The idea is to have a hackathon day, and give folks a single day to build something that achieves this, and then select a winner from the pool of successful solutions.

ETA

Q3

Expected impact

Building a new compatible IPFS implementation should be easy if you don’t need fancy features / optimizations (e.g. if you do dumb downloading, don’t need to handle peers behind NATs, etc.)

Will enable developers to understand how they bring the pieces of IPFS they need into their application even if the user doesn’t have a local kubo node running