js-peer: add ability to connect via peerID

[Nkovaturient]

Issue: #177

• PR created as part and discussion, here -> Issue

Aims:

• Example where two peers find each other with the peer-id only (in the best case with a dht for detecting the multiadders)
• Function to fetch peerinfo, connect thru known peers in peerStore
• DHT lookup attempts
• Compnent to render the list of peerIds connected with the entered peerID

Description:
1)findByPeerId function aims to find through PeerStore or DHT Lookup
2)DHT response and peerResponse as fallback

Fix needed:

• peerInfo response is retrieving a list of mutiaddrs alongwith bootstrap addrs, however on clicking connect thru either of them, an error of NoValidAddressesError: The dial request has no valid addresses or "DHT lookup failed"

• OUTPUT from PEERINFO obj(mainly thru Known Peer, not DHT)

addresses
: 
(10) [{…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}]
id
: 
Ed25519PeerId {type: 'Ed25519', multihash: Digest, publicKey: Ed25519PublicKey, string: undefined, Symbol(@libp2p/peer-id): true}
metadata
: 
Map(3) {'AgentVersion' => Uint8Array(64), 'last-dial-success' => Uint8Array(13), 'ProtocolVersion' => Uint8Array(0)}
peerRecordEnvelope
: 
Uint8Array(737) [10, 36, 8, 1, 18, 32, 87, 101, 178, 119, 212, 235, 230, 116, 127, 160, 63, 160, 129, 209, 158, 114, 12, 73, 56, 97, 94, 174, 237, 156, 100, 176, 89, 177, 213, 203, 191, 239, 18, 2, 3, 1, 26, 242, 4, 10, 38, 0, 36, 8, 1, 18, 32, 87, 101, 178, 119, 212, 235, 230, 116, 127, 160, 63, 160, 129, 209, 158, 114, 12, 73, 56, 97, 94, 174, 237, 156, 100, 176, 89, 177, 213, 203, 191, 239, 16, 199, 222, 166, 171, 183, 153, 254, 142, 24, 26, 50, 10, 48, 4, …]
protocols
: 
(10) ['/floodsub/1.0.0', '/ipfs/id/1.0.0', '/ipfs/id/push/1.0.0', '/ipfs/kad/1.0.0', '/ipfs/ping/1.0.0', '/libp2p/circuit/relay/0.2.0/hop', '/libp2p/circuit/relay/0.2.0/stop', '/meshsub/1.0.0', '/meshsub/1.1.0', '/meshsub/1.2.0']
tags
: 
Map(7) {'kad-close' => {…}, 'kad-peer' => {…}, 'keep-alive-circuit-relay' => {…}, 'keep-alive-kad-dht' => {…}, 'universal-connectivity' => {…}, …}

• why DHT lookup is failing?
• How to fetch peerInfo by entering peerId of known connections with valid addrs

[2color]

Instead of using the DHT service, you should use libp2p.peerRouting.findPeer(peerId) which abstracts from the specific peerRouting implementations. This way, it can benefit from both delegated routing and the DHT.

I would also reduce the scope of this PR and not introduce the kadDHT.

[2color]

See https://github.com/ipfs-shipyard/www-helia-identify/blob/main/src/index.ts#L59-L86 for how to simplify.

You probably don't even need the onPorgress hook from findPeer.

[Nkovaturient]

alryt will implement and fix as desired

[2color]

Thanks for the PR, Neha.

Before a proper review:

• Can you please run prettier on the files you edited in this PR to format changes (I've opened js-peer: add prettier for consistent styling #211 to address this). A lot of changes in this PR are code style changes adding unnecessary noise that makes reviewing harder.
• Can you please remove any commented out code that isn't relevant for this.

[Nkovaturient]

Thanks for the PR, Neha.

Before a proper review:

• Can you please run prettier on the files you edited in this PR to format changes (I've opened js-peer: add prettier for consistent styling #211 to address this). A lot of changes in this PR are code style changes adding unnecessary noise that makes reviewing harder.
• Can you please remove any commented out code that isn't relevant for this.

Roger that! @2color

[Nkovaturient]

Hey, @2color
wanna update you with recent commits:-

• ran prettier on files and code changes
• modified kadDHT to peerRouting methods-indeed an effective way of finding peers
• updated the peerFind handler in index.tsx
  

[Nkovaturient]

Hey, kindly review and provide guidance--
summary of the key changes made for peer connectivity:

Basically findBypeerID is fetching a list of multiaddrs --> in peer-maddr.tsx -we are filtering it with valid transport stack --> then trying to connect with either of them handleConnect

• Connection Handling:

• Fixed connection object creation to use actual libp2p connection
• Updated connection type interface to match simplified structure
• Added proper connection state management

• Transport Protocol Validation:

• Added checks for WebTransport + certhash
• Added checks for WebRTC + QUIC + certhash
• Added external address validation

• Connection Flow:

• Parse multiaddr to extract peerID
• Validate transport stack
• Attempt connection via connectToMultiaddr
• Store successful connection in state
• Clear resolved multiaddrs after connection
• Handle connection errors with user feedback

• UI Improvements:

• Added connection priority system
• Show transport protocol badges
• Display connection status indicators
• Added loading states during connection

[Nkovaturient]

@2color any updates/guidance?