Content Discovery:

• Publish your content to IPNI as supporting HTTP Gateway Trustless Data Transfer codec https://github.com/multiformats/multicodec/pull/321/files

• You don’t need republish — you can use extended providers to update all your existing records — cc: @Masih Derkani @Anonymous for support doing this

• Metadata for HTTP Gateway Trustless Data Transfer protocol in the indexer — I recommend we start with blank and update later — needs implementation in network indexer cc: @Masih Derkani

  https://github.com/ipni/go-libipni/issues/21

Data Transfer:

• To serve lassie, you must update your gateway to support the trustless CAR improvement spec: https://github.com/ipfs/specs/pull/402
  • Cheat sheet for what you need to change:
    • You must transmit intermediate blocks on a path when serving CAR file requests
    • You must support the car-scope parameter which defines three different levels of traversal at the end of the path:
      • block - just return a single block at the end of the path
      • file - return the unixfs entity, if it’s unixfs — otherwise single block. concretely, that means all the blocks in a UnixFS file, and all the blocks that enable a listing of a UnixFS directory (this is just a single block for normal directories but multiple blocks for the case of a HAMT directory)
      • all - send the whole recursive dag at the end, down to the leaves
    • Important: for now, we don’t need you to support the bytes parameter — you should eventually be spec compliant, but likely the spec will change while in the IPIP process, so no worries if it’s not implemented first
• Until 5/8 @Anonymous is the point person for support in implementing HTTP transfer on the server, as @Kyle Huntsman is busy implementing the Lassie client. After that @Hannah Howard will also be available 🙂