Purpose of Meeting and important docs 5m:
Important reference documents:
Updates from contributing teams 25m:
IPFS 5m
- IPIP-410: streaming support on /routing/v1 HTTP API (in review, looking for feedback)
- A bit of a formality just clarifying how we do streaming.
- AI: We’ve merged this into Kubo, both client and server but in testing we’re not seeing cid.contact streaming support for /routingv1 API.
- Kubo: ability to act as content routing /routing/v1 HTTP proxy (PR draft)
- Give this a review! https://github.com/ipni/indexstar/issues/92
- Exposing existing routing system in Kubo as the Routingv1 endpoint and documenting the libraries provided to the community. Empowering community to not depend on 3rd party infrastructure. Dependent on HTTP endpoints sparing some DHT crawling overhead. How do we represent providers with a known protocol? CID to PeerID relationships established but we may not get any data on multiAddrs.
- Important point we don’t want to assume bitswap. We want peer routing for light clients, but that discussion is still ongoing “how to represent provider records without known addresses or provider protocols?”
- Open question for /routing/v1/providers: how to represent providers with “unknown” protocol (eg. in DHT proxy scenario)
IPNI 5m
- DH store covering 100% of Prod Queries
- Graphsync concurrency limitations caused us some adchain pulling heartache this week but we’ve managed to overcome it and are back on track.
- We are doing a high level overview of where we’re at and what we think we can wrap up by the end of the Quarter. Coming your way:
- Measurement of other indexer instances(sync state - ad chain ingestion)
- CLI cleanup
- An MVP IPNI deployment for partner instances with Doublehashing we’re working with a partner to bring up.
- Some metrics improvements
- Revised IPFS docs!
- Edge node service(caching) - hopefully with deployment to Saturn L1s.
Probelab 5m