Spec for HTTPS-only providers on Amino DHT

オープン
#496 コメント 4 件 リアクション 7 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

  • #501 @guillaumemichel による — マージされずにクローズ

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
30/100
issue の種類
ドキュメント
明瞭さ
説明が足りない
活発さ
静か

調査の方向性

まず issue #496 の「Need」、「Proposed spec direction」、「Open questions」セクションを確認し、次にリンクされている Trustless Gateway と libp2p gateway の仕様および関連する issue を読みます。/tls/http に関して提案されているシグナリング、検証、相互運用性の要件を、既存の Amino DHT の動作と比較します。オープンな疑問を解決し、必要な動作を文書化した合意済みの仕様を作成できれば完了です。

索引モデルが issue の本文から書いたものです。

説明

need/triage

Filling public issue because this died in private channels and threads many times
Part of work towards https://github.com/ipshipyard/roadmaps/issues/9 and https://github.com/ipshipyard/roadmaps/issues/15
This is also helping with webseeds from https://github.com/ipshipyard/roadmaps/issues/19

[!TIP]
A lot of information below is from 2025 Q1 and outdated.
Jump to my 2026 Q3 status summary in https://github.com/ipfs/specs/issues/496#issuecomment-5195385659

Need

We need to agree and write down a specification how HTTP-only Trustless Gateway providers can be announced on existing Amino DHT.

Such provider can have a synthetic PeerID for interop with routing systems and software, but in reality it won't have any libp2p networking stack, and only expose HTTP endpoint that follows the Trustless Gateway spec.

Wider context

  • We already have big providers that have HTTP-only "PeerID" provider (e.g. Storacha announces special peer with /tls/http multiaddr – right now it is only announced to IPNI)
  • We already have experimental HTTP-only retrieval in boxo/rainbow that
    • Detects /tls/http multiaddrs
    • Performs content-type negotiation / probe to confirm the HTTP endpoint supports trustless gateway protocol
    • Performs HTTP-only retrieval from such provider
    • The PeerID is not used for anything.
      • There is no auth when client learns about this provider from delegated routing system that proxies to IPNI and DHT, nor IPNI runs any validation checks when it accepts such announcement.
  • We want to allow people to self-host over HTTP and turn off Bitswap
    • Stability and cost reduction thanks to HTTP Caching and free HTTP CDNs makes self-hosting possible with cheap hardware and with narrow bandwidth
  • We can't deploy protocol changes to DHT without waiting 6-24+ months for significant % of DHT server nodes to update
  • Most of people who self-host run Kubo or IPFS Cluster backed by a fleet of Kubo nodes that announce to Amino DHT (and some run sidecar that also announces to IPNI)

North star

Proposed spec direction

Open questions

  1. Any concerns with using /tls/http in announced Multiaddrs for this?
    • Example: is it ok for Kubo user to put their Gateway.NoFetch=true&Gateway.DeserializedResponses gateway behind Cloudflare and URL in Addresses.AppendAnnounce as /dns4/gw.example.com/tcp/443/tls as extra hint for clients that prefer HTTP-only retrieval?
    • afaik we have all specs necessary for reliable interop – see spec direction above, but comment below if any spec gaps exist
  2. If content providers start announcing their trustless, non-recursive gateways as /dnsX/example.com/../tls/http, do we need any auth of DNS names?
    • Should DHT nodes accept and gossip /dnsX/example.com/../tls/http addrs blindly or should extra validation be added at routing system level (DHT, IPNI)?
    • Following prior art of ACME challenges, we need to think about HTTPS on raw IPs, or other setups without access to DNS. We could require a signed peerid published on DNS TXT or as HTTP GET file on .well-known/libp2p/signed-peerid path, but this complicates deployments, requires people to deal with PeerIDs, and at the end of the day, how is this auth request any better from HTTP client blindly sending a trustless probe GET /ipfs/cid and getting 404 indicating endpoint is not a valid gateway?

As usual, ideas, feedback welcome.

主要言語
HTML
スター
1.2k
フォーク
250
PR マージ指標
30日以内にマージされた PR はありません

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

ipfs/specs のほかの issue

ipfs/specs の issue をすべて見る

似ている issue

Distributed Systems の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。