Spec for HTTPS-only providers on Amino DHT
还没有人认领这个 Issue。
- #501 来自 @guillaumemichel —— 已关闭,未合并
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 30/100
- Issue 类型
- 文档
- 描述清晰度
- 需要澄清
- 活跃度
- 冷清
调研方向
先阅读 issue #496 中的 “Need”、“Proposed spec direction” 和 “Open questions” 部分,然后阅读链接的 Trustless Gateway 和 libp2p gateway 规范及相关 issue。将针对 /tls/http 提出的 signaling、validation 和 interoperability 要求与现有的 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 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
ipfs/specs 的其他 Issue
-
need/triage
难度 2/5 1-3 小时 新手友好度 68/100
-
need/triage
难度 5/5 一周以上 新手友好度 30/100
-
dnslink:// URIs未关闭need/triage
难度 5/5 一周以上 新手友好度 30/100
-
难度 5/5 一周以上 新手友好度 35/100
-
need/triage
难度 3/5 1-2 天 新手友好度 55/100
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
bug hal:proposed neofs-storage
难度 2/5 1-3 小时 新手友好度 78/100
nspcc-dev/neofs-node#4325 · 3 条评论 ·
维护者通常 1 天内回复
-
pytorch plugin gives every master pod RANK=0, so master replicas > 1 leaves a rank missing可能已有人在做 @rakesh0x 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
volcano-sh/volcano#6323 · 1 条评论 · 已指派 1 人 ·
维护者通常 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 于 2 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复