Checklist

• This is not a new feature or an enhancement to the Filecoin protocol. If it is, please open an FIP issue.
• This is not brainstorming ideas. If you have an idea you'd like to discuss, please open a new discussion on the Boost forum and select the category as Ideas.
• I have a specific, actionable, and well motivated feature request to propose.

Boost component

• boost daemon - storage providers
• boost client
• boost UI
• boost data-transfer
• boost index-provider
• Other

What is the motivation behind this feature request? Is your feature request related to a problem? Please describe.

Boost Transports protocol offers a way to query the list of transports offered by a node. However the multiaddrs returned by the transports do not always contain the peer ID over which the data can be retrieved.

Peer ID is only included when the addrs are populated from a libp2p host that is separate from node's host. This is because Host.Addrs() does not include peer ID in the returned addrs.

Describe the solution you'd like

Always include peer ID in the multiaddrs returned. This removes the need for implicit assumption that when peer ID is not specified it should be the same as node peer ID.

Describe alternatives you've considered

Not doing this would require extra interaction to get the peer ID of the node.

Additional context

No response