You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The local docker setup includes an opt-in Trezor User Env fixture for manual hardware-wallet checks. It starts the official Trezor emulator and Bridge, but it is not part of the default `docker compose up -d` stack.
110
+
111
+
Default emulator state:
112
+
113
+
- Model: `T2T1`
114
+
- Firmware: `2-main`
115
+
- Bridge: `node-bridge`
116
+
- Mnemonic: random 12-word BIP39 phrase generated on each `start`
117
+
- PIN: empty
118
+
- Passphrase protection: off
119
+
- Label: `Bitkit Test Trezor`
120
+
121
+
Start the emulator:
122
+
123
+
```bash
124
+
./scripts/trezor-emulator start
125
+
./scripts/trezor-emulator status
126
+
```
127
+
128
+
`start` prints the generated mnemonic and the first native regtest receive address (`m/84h/1h/0h/0/0`) so it can be funded during manual checks.
129
+
`start` refuses to wipe/reseed an already-running emulator. Use `stop` before starting a new one.
The Trezor User Env image is pinned in `docker/docker-compose.yml` so the emulator Bridge keeps the raw message format expected by current Bitkit builds.
Backend and Trezor are independent. `BACKEND=local` uses local Bitcoin/Electrum, while `BACKEND=regtest` uses remote staging regtest services. The Trezor emulator always provides only the device and Bridge. Fund or mine against the same backend the app was built for.
216
+
88
217
### 🧪 Running tests
89
218
90
219
**Important:** The `BACKEND` environment variable controls which infrastructure the tests use for blockchain operations (deposits, mining blocks):
0 commit comments