> How is it compromising if you rebroadcast repetedly any tx in the mempool? What exactly does it compromise?

IP address to all peers.

> It gives out the information that you have a mempool that holds transactions longer than the median holding time of the network, that's it. That tx is possibly not yours.

Yeah, unless you wait for 2 weeks (or whatever the default eviction mempool policy is) after which the transaction rebroadcasting links it to your IP. **I repeat again. Bitcoin core treats those transaction as your own when your pubkey is the receipient. And will not stop trying to rebroadcast them.**

Sorry, I have a policy that I don't engage in reply chains for more than 3 replies. Hope that replies so far were helpful.

How is it compromising if you rebroadcast repetedly any tx in the mempool? What exactly does it compromise? It gives out the information that you have a mempool that holds transactions longer than the median holding time of the network, that's it. That tx is possibly not yours.

tolot

Never said it is different.  Rebroadcasting means repeated broadcasting. 

And the "**repeating tx broadcasting forever (because of low feerate)**" part is privacy compromising. Hope that helps clear things up. For more info just google "bitcoin rebroadcasting".

CruncherDefi

bitcoin

Beware of possibly new type of chain analytics for correlating pkeys to IPs

How is rebroadcasting different from broadcasting in the p2p network?
Can you point to some resources?