Addresses

[ghost]

/dns4/ws-star-signal-1.servep2p.com/wss/p2p-websocket-star/

Shouldn't this be:

/dns4/ws-star-signal-1.servep2p.com/tcp/443/wss/p2p-websocket-star

With the added /tcp/443 and the trailing slash removed

[mkg20001]

Internally this is converted to https://ws-star-signal-1.servep2p.com so it doesn't matter. (It needs to be an URL because socket.io)

[ghost]

Okay, understood -- multiaddrs are always explicit, so we need that /tcp/443 bit there. TCP multiaddrs are always of the form /ip4/<addr>/tcp/<port> (and same for /ip6 of course).

[daviddias]

Just tested, indeed it fails with an addr with tcp + port

Error: invalid multiaddr: /dns4/ws-star.discovery.libp2p.io/tcp/443/wss/p2p-websocket-star/ipfs/Qma3uqwymdqwXtC4uvmqqwwMhTDHD7xp9FzM75tQB5qRM3

[daviddias]

js-mafmt works well with that multiaddr -- multiformats/js-mafmt#20 --, the issue is on the module multiaddr parsing function