Install & first run
The Trézór App installs like any modern companion app. Download the package for your OS from the official site, verify the checksum or signature if available, and run the installer. The App runs a local, encrypted service that brokers connection requests from browsers or desktop apps. During first run you'll be asked to grant minimal OS permissions for the local service — these are required so the Bridge can listen for incoming connection calls from your browser extensions or native clients.
Step-by-step quick install
- Download from the official Trézór site and check TLS and signatures.
- Run the installer and allow the local service when prompted.
- Connect your Trezor device with the official cable; unlock it when requested.
- Open a compatible dApp or wallet and follow its connect flow; the App will show an approval prompt.
Core features & workflows
Trézór Bridge focuses on three core goals: minimize data exposure, maximize user consent, and provide a stable API surface for developers. That translates into features you can use and rely on every day.
Scoped permissions
When a website or app requests access, it must specify scopes — e.g., "view addresses" or "request signing". You see exactly what's requested in the App's prompt and can allow, deny, or limit scope. Scopes are fine-grained so you can grant the least privilege necessary for the task.
On-device verification for signing
Even after a session is authorized, no transaction can be signed without on-device confirmation. The Trezor device displays the full human-readable details (destination, amount, fees, and contract data where applicable). This is the single most important defense against remote tampering: malware on your computer cannot change what is shown on the device.
Session manager & audit logs
The App includes a session manager so you can view active connections, inspect granted scopes, revoke access, and see a compact audit trail of signing events. Use the session manager to quickly terminate sessions from unknown origins or to clean up long-lived app permissions you no longer use.
Ephemeral sessions for one-offs
If you're connecting to a new service for a single action, choose an ephemeral session: it expires automatically after the action completes or after a short time. This reduces long-term exposure if you try unfamiliar dApps.
Developer sandbox & examples
A developer sandbox demonstrates typical flows: connect, request addresses, and request a signature. The docs include examples for common stacks and recommend UI patterns for clear permission requests and robust error handling.
Security model & privacy
Security is the heart of the Bridge's design. It never touches private keys — those remain inside your Trezor device. The App only transmits protocol-level messages and signed transactions. Key privacy and integrity are preserved through:
- Local-only communications: the Bridge runs on your machine and does not persist session keys in cloud storage by default.
- Explicit user consent: every permission and signing request is surfaced to you with clear text before it proceeds.
- Minimal data transfer: the App transmits only what the dApp needs to operate (addresses, transaction bytes) — nothing more.
- Auditable logs: a concise local audit trail helps you review past actions and detect anomalies.
Best practices for users
- Grant the smallest set of scopes needed for a dApp to function.
- Always verify transaction details on the Trezor device screen before approving.
- Revoke persistent sessions you no longer use via the session manager.
- Prefer ephemeral sessions when experimenting with new dApps.
Guidance for developers
Integrating with Trézór Bridge gives dApps access to hardware-backed signing with minimal friction for users. The SDK and examples emphasize secure UX and least-privilege patterns.
Developer recommendations
- Request only the scopes you need — avoid "catch-all" permission requests.
- Surface clear intent and show transaction previews in your UI prior to asking the user to sign.
- Support ephemeral session flows for one-time interactions (wallet connect–like UX).
- Log request IDs and allow users to reference them in audit logs if they need help.
Troubleshooting & FAQ
My browser can't see the Bridge — what should I do?
Ensure the Trézór App is running on your desktop and that any OS firewall allows the local service to accept connections. Try restarting the App, the browser, and the Trezor device. Use a known-good cable and avoid USB hubs if possible.
Does the Bridge store my keys?
No. Private keys remain on the Trezor device. The Bridge only transfers messages and signed data; it does not persist private keys or recovery seeds.
Is the App open-source?
Parts of the App and the SDK are published for review. Check the official repositories and documentation for source and audit notes.
When to use ephemeral sessions vs persistent
Ephemeral sessions are ideal for one-off transfers, short-lived approvals, or when exploring new dApps. Persistent sessions suit trusted desktop wallets or tools you use frequently and want to keep connected for convenience. Always weigh convenience against long-term exposure and revoke permissions you no longer need.
Closing advice
Trézór Bridge modernizes hardware wallet integration for today's web and desktop ecosystem by balancing developer ergonomics with strong user-centric security. Keep your device's firmware updated, confirm everything on-device, use ephemeral sessions for experimentation, and prefer well-audited dApps. When in doubt, deny the request, revoke the session, and consult official support or docs.