Spec for HTTPS-only providers on Amino DHT

未关闭
#496 4 条评论 7 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 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 内容生成。

描述

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. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ipfs/specs 的其他 Issue

查看 ipfs/specs 的全部 Issue

相似的 Issue

更多 Distributed Systems Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。