Spec for HTTPS-only providers on Amino DHT
Nadie ha tomado este issue todavía.
- #501 de @guillaumemichel — cerrado sin fusionar
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 30/100
- Tipo de issue
- Documentación
- Claridad
- Necesita aclaración
- Estado de actividad
- Tranquilo
Línea de trabajo
Comienza con las secciones «Need», «Proposed spec direction» y «Open questions» del issue #496; después, lee las especificaciones enlazadas de Trustless Gateway y libp2p gateway, así como los issues relacionados. Compara los requisitos propuestos de señalización, validación e interoperabilidad de /tls/http con el comportamiento existente de Amino DHT. Se considerará terminado cuando se produzca una especificación acordada que resuelva las preguntas abiertas y documente el comportamiento requerido.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- HTML
- Estrellas
- 1.2k
- Forks
- 250
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de ipfs/specs
-
Simplify Spec StatusesAbiertoneed/triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Revise steward and editor rolesAbiertoneed/triage
Dificultad 5/5 Más de una semana Aptitud para principiantes 30/100
-
dnslink:// URIsAbiertoneed/triage
Dificultad 5/5 Más de una semana Aptitud para principiantes 30/100
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
-
need/triage
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
Todos los issues de ipfs/specs
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
volcano-sh/volcano#6323 ·
Los mantenedores suelen responder en 1 día
-
area: facilitator bug complexity: trivial
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
accensa/x402-facilitator-stellar#709 ·
Los mantenedores suelen responder en 1 día
-
resiliency: ParseRetryConditionMatch fails when HTTPStatusCodes or GRPCStatusCodes contain whitespacePosiblemente ocupada @patelshivani2283-lab la tomó hace 1 día. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
[Bug] maxConcurrent{Activity,Workflow,Nexus}TaskPolls are accepted but never appliedPosiblemente ocupada @pcbeingused333 la tomó hace 1 día. Abiertosdk-typescript
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
temporalio/sdk-typescript#2693 ·
Los mantenedores suelen responder en 1 día