We considered to derive peerID for IPNI using SP's owner wallet address (aka the operational address) - which comes with a downside - whenever the SP wants to rotate their operational keys (which will lead to a new peerID), all their ads need to be updated with new peerID and that is an expensive operation (basically establish a new ad chain), especially for large providers. PeerID really doesn't have any binding relationship with a dataset or a piece perse - client will still retrieve from the the sp's service url

So to keep the peerID relatively stable for reducing IPNI ops, we could use a pdpOffering.IPNIPeerId .