Use official SDKs and follow the vendor's integration guidelines. Keep user privacy in mind: only request addresses and metadata essential to the flow.
Bridge is intentionally lightweight, but issues can still occur — most commonly due to OS permissions, conflicts with other USB services, or outdated software. Below are typical problems and fixes.
| Problem | Fix |
|---|---|
| Browser cannot detect Bridge | Ensure Bridge is running (check system tray), restart the browser, and disable extensions that block local host access. |
| Device not detected | Try a different USB cable/port, avoid USB hubs, check OS drivers (Windows), and ensure device firmware is up to date. |
| Connection times out | Check firewall settings and ensure Bridge is allowed to listen on localhost. |
| App shows cryptographic warning | Do not proceed. Verify Bridge and Suite versions, and contact official support if you suspect tampering. |
If you encounter warnings about corrupted firmware, authentication failures that you cannot resolve, or anything that looks like tampering, stop and contact official vendor support. Provide device model, firmware version, Bridge version, and exact error messages — never share your recovery seed or private keys with support.
No. Private keys remain on your hardware device at all times. Bridge only relays messages between the dApp and device. Signing operations occur on-device and return only signed payloads.
By design Bridge is intended for local host access only. Do not expose Bridge endpoints to remote networks or the internet — doing so compromises the security model.
For many browser-based dApps, yes — Bridge (or an equivalent native connector) is required because browsers limit direct access to attached hardware. Some dApps may offer alternative integration methods (e.g., browser extensions or WalletConnect protocols) that do not require Bridge.
Refuse and disconnect immediately. No legitimate dApp or the official Bridge should ever ask you to provide your recovery seed or raw private key. Report suspicious behavior to the dApp and consult official support channels.
Bridge — a local service that enables communication between the browser and a hardware wallet. Hardware wallet — a physical device that stores private keys and performs signing operations securely. Passphrase — an optional secret added to your seed to create hidden wallets. Signing — the act of cryptographically authorizing a transaction or message; must be confirmed on-device.