📙 Overview

• We don't think platforms can succeed in a vacuum. We need to start with a really sticky product that solves real user problems
• We think it's critical for onboarding to be low-friction. It should be free and keyserver setup should be optional unless you want to host a community
• Once we have a solid install base of keyservers, we flip it into a platform

Web3 Discord

🔑 Sovereign, private chat communities

• Comm is the first E2E chat app that can support the Slack / Discord feature set
• Keyservers enable this
• Not just E2E: Comm is censorship-resistant
• Keeping identity on-chain (eg. login with ETH) prevents us from being able to hijack identity

₿ Targeting Web3 communities

• ALL of these communities are on Discord today
• There is a values disconnect – Discord is centralized, unencrypted
• Web3 communities tend to be more open to adopting new tech
• Will be great to have a lot of coders signed up when we launch our app platform

🎛️ The noise problem

• Discord is a broken experience product-wise due to the noise problem
• We're focused on asynchronous use cases
• Comm's home screen is a unified inbox that shows all of your threads