Slide 1 — Title & Overview
Trezor Bridge®: a lightweight, cross-platform local proxy that enables secure communication between Trezor hardware wallets and web or desktop applications. This presentation covers why Bridge exists, how it works, installation steps, common problems and their fixes, security best practices, and developer notes.
Speaker notes: Introduce the problem — browsers historically couldn't access USB devices directly, Bridge solves this while keeping private keys isolated on the device.
Slide 2 — Why Bridge?
Bridge ensures reliable USB communication across Windows, macOS, and Linux. It simplifies user experience for web-based wallets and Trezor Suite by providing a consistent local API and handling permission quirks across platforms.
Speaker notes: Emphasize cross-platform reliability and why a local service is preferable to browser-only approaches in many environments.
Slide 3 — How Bridge Works (Simple)
Bridge runs as a background application on the user's machine and exposes an API on localhost. Web apps and desktop Suite call this API to send commands; the Trezor device performs signing and displays transaction details for confirmation.
Speaker notes: Use a diagram on-screen showing browser ↔ Bridge ↔ USB ↔ Device. Make clear that private keys never leave the hardware.
Slide 4 — Installation Steps
1) Download Bridge from the official page: trezor.io/bridge.
2) Choose platform-specific installer (Windows, macOS, Linux).
3) Verify checksums where provided.
4) Install and restart browser or Suite.
Speaker notes: Remind audience to avoid third-party mirrors and to verify checksums via the Downloads page:
trezor.io/downloads.
Slide 5 — Common Troubles & Fixes
Typical issues: Bridge not running, browser permission blocks, outdated Bridge version, firmware mismatch. Quick fixes: restart Bridge, clear browser cache, reinstall Bridge from official source, confirm firmware via firmware page.
Speaker notes: Walk through a live demo restarting the Bridge service or checking http://localhost:21325 if appropriate.
Slide 6 — Security Best Practices
Install Bridge only from official pages, keep it up to date, ensure it listens only on localhost, and never enter your seed on any website. For further reading, reference the Anti-Phishing page: trezor.io/phishing.
Speaker notes: Reinforce: signing happens on device; Bridge only relays messages. Recommend regular firmware checks and updates.
Slide 7 — Developer Notes
Developers should follow origin checks, prompt users for explicit actions, and rely on the official Bridge API documented in the Trezor developer resources. See GitHub and Business & API pages for integration details.
Speaker notes: Share links to libraries and SDKs that simplify integration. Mention testing strategies and the importance of user prompts.
Slide 8 — Use Cases & Demos
Bridge empowers web wallets, dApp interactions, and desktop Suite operations. Demo examples: sign a simple BTC transaction, connect to a web-based wallet, or show a swap flow via Suite's integrated partners.
Speaker notes: Offer live demos if possible and point to Suite:
suite.trezor.io.
Slide 9 — Troubleshooting Deep Dive
Advanced diagnostics: check running processes, verify Bridge port, inspect OS USB permission policies, re-install drivers on Windows, and use alternative browsers for testing. For assistance see Support Center.
Speaker notes: Provide command-line tips for Linux and macOS power users, and explain driver reinstallation on Windows.
Slide 10 — FAQ & Closing
Answer common questions: Is Bridge necessary? (usually yes for web workflows). Is it safe? (yes, if installed from official sources). Where to get help? (Support, Blog).
Speaker notes: Wrap up with recommended reading and links; invite questions.