1. The Sybil & Phishing Attack Vector
Client-side filtering like “Smart Inbox” is just a band-aid. Web3 messaging without economic friction is structurally flawed. With zero cost to initiate communication, the protocol remains completely vulnerable to automated phishing campaigns. Furthermore, any future network scaling or incentivization will be immediately exploited by Sybil botnets generating fake messaging volume to farm rewards.
Proposal: Implement base-layer economic friction (e.g., micro-staking, computational Hashcash-style PoW, or dynamic rate-limiting) to send messages to unconsented inboxes.
2. Metadata Leakage (Social Graph Harvesting)
While message content is E2E encrypted via MLS, network nodes actively monitor and log metadata (sender, recipient, timestamps, and payload sizes). This enables passive harvesting and mapping of web3 identity relationships, completely breaking on-chain privacy and exposing user interaction graphs to malicious node operators.
Proposal: Enforce protocol-level traffic padding (uniform packet sizes) and randomized delivery micro-delays to blind node operators and prevent social graph deanonymization.
Bottom Line:
Protocol-level security against economic exploitation and privacy leaks must take precedence over cosmetic UX features like message editing or inbox tabs. Let’s fix the foundation before building the curtains.