About the bridge
The bridge provides a stable local channel between the device and desktop utilities, handling device discovery and encrypted transport. Its purpose is to simplify secure interactions while minimizing the attack surface: private keys remain on the hardware and only signed responses are transmitted back to the host application.
Why use it
Using a local bridge gives consistent cross-platform behavior, smooth device detection, and better permissions control. It reduces friction for users and prevents software from attempting to access hardware directly in ways that could compromise security.
Step-by-step setup guide
- Install the official bridge software from your trusted source and run the installer for your platform.
- After installation, allow the bridge to run as a background helper so it can detect attached devices automatically.
- Connect the hardware key to a USB port; the bridge will enumerate it and make it available to local applications.
- Open your wallet application and follow its prompts to pair with the detected device; the device itself will require confirmation for sensitive actions.
- Keep the bridge updated — most releases include stability and security fixes that improve device compatibility.
Troubleshooting tips
- If a device is not detected, try reconnecting the cable and ensure the helper service is running in the background.
- Restarting the host application or system service often resolves transient USB permission issues.
- Use official releases only and verify checksums when available for stronger assurance.
Best practices
Treat the hardware key as the root of trust: keep its firmware current, protect recovery material offline, and pair only with trusted host software. Avoid exposing the helper on untrusted networks and prefer local use only.