Overview
Trezõr® Brïdge® is an official companion utility designed to act as a secure communication layer between your Trezor hardware device and applications that need to interact with it. The Bridge provides a minimal, auditable surface for connecting the host (browser or desktop app) to the device, handling transport, session management, and device discovery while ensuring signing operations always occur inside the hardware wallet.
The objective is simple: enable modern workflows (web wallets, desktop management apps, developer tooling) without exposing private keys, while keeping the codebase lean, open to review, and easy to update.
Key features
Device discovery & transport
USB and WebUSB support plus optional native helpers for improved cross-platform detection.
Secure signing channel
All signing requests are routed to the Trezor device; Bridge never sees or stores private keys or mnemonic material.
Session & permission model
Explicit user approval and origin-based permissions for web integrations to limit exposure to untrusted pages.
Open & auditable
Source code is public and intended for third-party audits and integrations.
Small footprint
Lightweight background process with minimal network interaction — focused on transport and security primitives.
Developer API
Simple JSON-RPC style API to integrate into web apps, CLI tooling, or native apps.
Download & Installation
Install Trezõr® Brïdge® from official channels. Choose the package that matches your OS:
- Windows (MSI/EXE)
- macOS (PKG / Homebrew)
- Linux (AppImage, .deb, .rpm)
- Browser (WebUSB) — requires explicit user permission per site
Security tip: always verify checksums and signatures published on the official site before installing. Avoid third-party binaries and unverified package sources.
Quick start
- Download the latest Bridge package from the official site.
- Run the installer and start the Bridge service (it runs in the background).
- Connect your Trezor device and open the web or desktop app that supports the Bridge.
- Grant the requested permissions and confirm device prompts to begin interactions.
Typical signing workflow
Bridge acts as an intermediary that forwards signing requests from the host to your Trezor and returns signed transactions only after you explicitly approve them on-device. A simplified flow looks like this:
// Simplified request flow
1. Host builds unsigned transaction / message.
2. Host calls Bridge API to send the payload to connected device.
3. Bridge forwards payload to Trezor device using USB/WebUSB.
4. Trezor displays transaction details on-screen for user verification.
5. User approves on-device; device signs securely.
6. Signed payload returned via Bridge to host; host broadcasts to network.
This flow ensures the host never touches private keys and that users always confirm on the hardware screen — the authoritative source for transaction details.
Security model
Trezõr® Brïdge® is built on a few core security guarantees:
- Private key isolation: Private keys and signing operations remain inside the hardware device at all times.
- User-centric approval: The hardware device is the single source of truth for approving transactions and revealing public keys.
- Least privilege: Bridge exposes a minimal API surface. Web origins must request explicit permission to talk to devices.
- Auditable code: Open source with reproducible builds to allow independent security review.
Bridge intentionally does not perform any long-term storage of secrets. Session metadata is ephemeral and scoped to the origin and session.
Developer integration
Developers can integrate Trezõr® Brïdge® via a straightforward JSON-RPC API. Common operations include:
- Device enumeration and status
- Requesting public keys / xpubs
- Sending sign requests for transactions and messages
- Managing origin/permission grants for web apps
// Example: pseudo-code to request a signature
const req = { method: 'trezor_sign', params: { tx: unsignedTx } };
const resp = await bridge.send(req);
// resp.signedTx -> broadcast
Refer to the official docs and API reference for exact schema, error codes, and integration examples.
Troubleshooting & FAQ
- Bridge cannot find my device
- Check cables, confirm the device is unlocked, ensure the latest firmware is installed, and that Bridge is running with the necessary permissions. On browsers, ensure you granted WebUSB permissions for the origin.
- Should I leave Bridge running all the time?
- Bridge runs as a background helper only when needed. For maximum attack surface reduction, start it only when using trusted applications.
- Does Bridge ever see my recovery seed?
- No. Bridge never requests or receives your recovery seed. Any prompt asking for your seed is a scam — never share it.