Adin Schmahmann

> This leads to problems with transports that, for example, validate TLS certificates, as they're kept ignorant about the domain name, and only learn the resolved address IIUC this isn't...

> I'm not sure I follow, do you mean only keep the peer id in the peer store? Or only keep the unresolved /dns4/... address? I meant keeping the addresses...

> Are we already using that somewhere in our stack? I haven't personally made much use of it, but it shows up in some consumers of go-libp2p. A few I'm...

> Are there bootstrap websocket nodes? How are you hoping to use this? If you're trying to leverage the IPFS Public DHT while only having websockets available as a transport...

This looks good to me. @aarshkshah1992 you've been looking at these things recently, any thoughts/concerns?

@RubenKelevra do you know which version caused a regression? Have you tried with v0.11.0? v0.12.0 is a very targeted release which should not have disturbed much so understanding when this...

> I can confirm this issue for 0.11 as well, so it's not a new thing. Thanks that's very helpful. Is this a v0.10.0 -> v0.11.0 thing? When was the...

Ok, so to clarify your performance/testing looks like: - v0.12.0-rc1 ❌ - v0.11.0 ❌ (includes automatic UnixFS sharding) - v0.10.0 ❓ (includes a bunch of code moving to the newer...

@RubenKelevra might be worth checking if https://github.com/ipfs/go-ipfs/pull/9042 fixes the problem (it should be in master later today). There was a performance fix in go-unixfs regarding the automatic sharding (https://github.com/ipfs/go-unixfs/pull/120)

Placeholder