Content liability: who is responsible for illegal content on a P2P network? Operators of BitTorrent trackers, IPFS pinning services, relay nodes, and Tor exit relays face different legal exposure depending on jurisdiction.

Encryption regulation: strong cryptography used in transport encryption and anonymity networks may be regulated in some countries.

Safe harbor: DMCA §512, EU E-Commerce Directive, and DSA provide conditional immunity for intermediaries who respond to valid takedown requests.

Data protection: GDPR and similar laws apply when P2P systems process personal data. Append-only logs in SSB and Hypercore create tension with the right to erasure. Content-addressed data is immutable by design—erasure means removing all copies, which is hard when storage is distributed.

Index/relay-level takedowns: centralized components (trackers, gateways, relays, pinning services) can remove entries or deny service in response to valid requests.

Community moderation: in social P2P systems like SSB and Matrix, moderation is social: blocking, muting, community norms, and power levels.

Reputation-driven filtering: PubSub scoring and peer reputation filter bad actors at the protocol level.

Transparency: publish moderation policies and actions; avoid opaque censorship.

Default private: data sharing should be opt-in, not opt-out. Don't inadvertently leak local files to the network. Hypercore requires explicit sharing of discovery keys.

Explicit consent: inform users when their data will be replicated or relayed.

Rate limits and resource caps: prevent a single peer from consuming unbounded storage, bandwidth, or CPU. Critical for defending against DoS attacks.

Minimum viable metadata: collect and expose only what's necessary for protocol function. See Privacy.

Privacy and anonymity tools like Tor and I2P serve both human rights defenders and malicious actors. There is no technical solution to this tension. Good P2P design:

Enables privacy by default for all users.

Provides moderation and reporting tools at application and community layers.

Documents the threat model honestly.

Cooperates with legal processes where required, while protecting user privacy where possible.

Compliance intersects with Identity (accountability vs pseudonymity), Privacy (right to anonymity vs abuse prevention), Storage (data retention and erasure), State Sync (append-only logs vs right to be forgotten), and Testing (audit trails and compliance verification). Design Patterns should incorporate compliance thinking from the start—retrofitting moderation into a decentralized system is much harder than designing for it.