Marcin Rataj

I think it would be enough for Desktop to register itself as a handle that: 1. converts all types of non-HTTP addresses to a HTTP URL at our official public...

Triage: - Most providers with HTTPS multiaddresses are unusable - try to clean up `cid.contact/routing/v1` responses, switch both http and bitswap providers to modern `peer` schema so we can remove...

Something we could try, without changing too much, without touching higher level abstractions like exchanges, is doing opportunistic HTTP fetch in `boxo/bitswap` itself. Wrote initial thoughts in https://github.com/ipfs/boxo/issues/608 – pinged...

@anthonyra iiuc to make Rainbow compatible with [swarm.key-based private bitswap network](https://github.com/ipfs/kubo/blob/master/docs/experimental-features.md#private-networks) you need more than just Bootstrappers. :point_right: If you need PNET support, please fill a new issue describing your...

@mashi @willscott just for the sake of planning, do we have any ETA for cid.contact supporting IPNS lookups ([IPIP-351](https://specs.ipfs.tech/ipips/ipip-0351/))? If it is not happening in next 1-2 months, we could...

Filled https://github.com/protocol/bifrost-infra/pull/2701 to enable `/ipns/id?format=ipns-record` (`Accept: application/vnd.ipfs.ipns-record`) lookups at `node[0-2].delegate.ipfs.io`. Once we have it in prod, we can remove Kubo RPC related code incl. [`KUBO_RPC_URL`](https://github.com/ipfs/bifrost-gateway/blob/main/docs/environment-variables.md#kubo_rpc_url) and implement `IPNS_GATEWAY_URL`

https://github.com/protocol/bifrost-infra/pull/2701 got merged, and we now can switch `routing.go` to fetch signed IPNS records via: ```console $ curl -s -H 'Accept: application/vnd.ipfs.ipns-record' "https://node2.delegate.ipfs.io/ipns/k51qzi5uqu5dgutdk6i1ynyzgkqngpha5xpgia3a5qqp4jsh0u4csozksxel2r" -o test.ipns-record ``` And then verify signature...

@hacdias you are right, we need to keep `KUBO_RPC_URL` for these legacy `/api/v0` paths handled by `newKuboRPCHandler` – but these are only redirects, and we should only register `/api/v0` listener...

(had no time to investigate) I think we need to switch to new boxo, and maybe kubo too, since https://github.com/ipfs/boxo/pull/369 finally got merged?

This needs to be fixed in boxo, most likely by adding the `v1` marker [here](https://github.com/ipfs/boxo/blob/8ec71db551e0a5369ccbe639334fee43f303a033/ipld/unixfs/pb/unixfs.pb.go#L193-L195) (we already did similar thing [here](https://github.com/ipfs/boxo/blob/8ec71db551e0a5369ccbe639334fee43f303a033/bitswap/message/pb/message.pb.go#L371-L377) ) as noted in [this private Slack thread](https://filecoinproject.slack.com/archives/C03AQ3QAUG1/p1685023439621479?thread_ts=1685022344.779649&cid=C03AQ3QAUG1). Fix...