Description

This is a follow-up to #3270.

The types and operations/behavior that are expected from an underlying p2p library should be specified.
This way we can have clear overview an understanding what requirements we have on the underlying p2p network.

• use of multiaddress for peer addresing
• have sink for outgoing packets
• have a stream for incoming packets
• ... etc.

Ideally this is defined using a trait that on its interface operates with Multiaddress,...

Definition of DONE

• p2p HOPR requeirements are abstracted out into a trait
• the trait is implemented using libp2p-rs