-
Notifications
You must be signed in to change notification settings - Fork 20
Delegate resolution of DNSlink and IPNS records #5
Comments
@lidel I wonder if using the |
@hacdias we won't have I filled https://github.com/protocol/bifrost-infra/issues/2327 to expose |
Discussion/analysis of v0 api usage on ipfs.io was done here: https://www.notion.so/pl-strflt/API-v0-Distribution-9342e803ecee49619989427d62dd0f42 |
Done in #19 |
Initial idea (for Feb 17 binary)
/ipns/id
content paths to/ipfs/cid
oneshttps://node[0-2].delegate.ipfs.io/api/v0/resolve
(it handles both DNSlink and IPNS)id
to avoid sending lookup, we can do it in two stages:/api/v0/resolve
and handle IPNS and DNSLink separately/api/v0/routing/get
and cache based on TTL of the IPNS recordhttps://node[0-2].delegate.ipfs.io/api/v0/routing/get
(cc @hacdias to confirm, I believe we already do this is tests).
Long term, we want to use delegated HTTP routing for IPNS (follow-up for IPIP-337, when that API supports IPNS lookups), and DoH for DNSLink (https://github.com/libp2p/go-doh-resolver/ ?)
The text was updated successfully, but these errors were encountered: