Spec for HTTPS-only providers on Amino DHT
まだ誰も着手していません。
- #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 の本文から書いたものです。
説明
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/httpmultiaddr – right now it is only announced to IPNI) - We already have experimental HTTP-only retrieval in
boxo/rainbowthat- Detects
/tls/httpmultiaddrs - 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.
- Detects
- 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
- Annual reminder, that no spec for IPFS behaviors on Amino DHT exists, and if we want to make changes, need to fill this gap first: https://github.com/ipfs/specs/issues/345
- 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
- Use this as opportunity to fill gap described in https://github.com/ipfs/specs/issues/345
- We want to leverage existing DHT clients, servers, including third-party software.
- Leverage PoC that works with Storacha, and generalize it for Amino DHT and private swarms
- Make it possible for existing users to run Kubo-based node/cluster that only exposes non-recursive Trustless Gateway over HTTPS and has Bitswap Server shut down
Proposed spec direction
- use
/tls/httpin announced Multiaddr as signaling method- document that libp2p peers should follow libp2p+http spec for coexistence of multiple services on the same HTTP endpoint
- for libp2p specific ones, follow https://specs.ipfs.tech/http-gateways/libp2p-gateway/#well-known-libp2p-protocols to discover libp2p protocols supported by the HTTP endpoint → https://github.com/ipfs/specs/pull/495
- for http-only retrieval, follow plain HTTP content type negotiation (Accept header) and probing convention documented in trustless-gateway spec
- this keeps system open-ended – HTTP-based transfer protocols can be added the same way, all they need to do is to use new content-type in
Accept/Content-Typeheader - document that HTTP-only Trustless Gateway clients can ignore PeerID → https://github.com/ipfs/specs/pull/495
- this keeps system open-ended – HTTP-based transfer protocols can be added the same way, all they need to do is to use new content-type in
- document that libp2p peers should follow libp2p+http spec for coexistence of multiple services on the same HTTP endpoint
Open questions
- Any concerns with using
/tls/httpin announced Multiaddrs for this?- Example: is it ok for Kubo user to put their
Gateway.NoFetch=true&Gateway.DeserializedResponsesgateway behind Cloudflare and URL inAddresses.AppendAnnounceas/dns4/gw.example.com/tcp/443/tlsas 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
- Example: is it ok for Kubo user to put their
- 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/httpaddrs 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-peeridpath, 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 probeGET /ipfs/cidand getting 404 indicating endpoint is not a valid gateway?
- Should DHT nodes accept and gossip
As usual, ideas, feedback welcome.
- 主要言語
- HTML
- スター
- 1.2k
- フォーク
- 250
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
ipfs/specs のほかの issue
-
need/triage
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
-
need/triage
難易度 5/5 1週間以上 初心者へのやさしさ 30/100
-
dnslink:// URIsオープンneed/triage
難易度 5/5 1週間以上 初心者へのやさしさ 30/100
-
難易度 5/5 1週間以上 初心者へのやさしさ 35/100
-
need/triage
難易度 3/5 1〜2日 初心者へのやさしさ 55/100
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
volcano-sh/volcano#6323 ·
メンテナーはふだん 1 日以内に返信
-
area: facilitator bug complexity: trivial
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
accensa/x402-facilitator-stellar#709 ·
メンテナーはふだん 1 日以内に返信
-
resiliency: ParseRetryConditionMatch fails when HTTPStatusCodes or GRPCStatusCodes contain whitespace対応中かも @patelshivani2283-lab が 1 日前に担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
[Bug] maxConcurrent{Activity,Workflow,Nexus}TaskPolls are accepted but never applied対応中かも @pcbeingused333 が 1 日前に担当しました。 オープンsdk-typescript
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
temporalio/sdk-typescript#2693 ·
メンテナーはふだん 1 日以内に返信