Invisible Crypto
summary
Element proposes making Matrix E2EE usable by default: it requires mandatory device verification and identity pinning (TOFU), embeds device keys into encrypted events, and adds an authenticated backup signature so restored keys are provably uploaded by a user device. Clients will drop unsigned devices and remove per‑message shields; QR‑code device linking bootstraps verified devices. Several MSCs (including MSC4161) and a Rust SDK implementation exist to do the heavy lifting, and Element records an internal rerun demonstrating the workflow.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:48What is invisible crypto
- 3:58Challenges in Matrix crypto
- 15:09Proposed solutions overview
- 18:47Mandatory device verification
- 24:09Authenticated backup solution
- 27:01Technical challenges addressed
- 31:58QR code login demo
- 34:25Summary and call to action
- 36:15Q&A session
related talks
42mDesigning Matrix: A Global Decentralised End-to-End Encrypted..
30mImplementing a third layer of security (do we need it?)
34mPractically-exploitable Cryptographic Vulnerabilities in Matrix
24mEnhancing Privacy in Cross-Chain Messaging: Untraceable Credentials with TEEs
22mGuarding the Gate: Strategies for High Security with Passkeys
18mThe Future of Crypto Wallets: Trends and Innovations
25mSecure by Design
24mEnd-to-End encryption for iOS Developer