Skip to content

Fix BitBox ETH support for Multi editions#1033

Merged
TaprootFreak merged 1 commit intodevelopfrom
fix/bitbox-eth-supported-workaround
Mar 30, 2026
Merged

Fix BitBox ETH support for Multi editions#1033
TaprootFreak merged 1 commit intodevelopfrom
fix/bitbox-eth-supported-workaround

Conversation

@TaprootFreak
Copy link
Copy Markdown
Collaborator

Summary

  • Work around ethSupported() WASM binding bug in bitbox-api v0.2.1 that returns false for BitBox02 Multi editions
  • Instead of pre-checking ethSupported(), attempt ETH address fetch directly and only fall back to BTC if the device rejects the request
  • If ethSupported() returns true but ETH still fails, the real error is propagated (not swallowed)

Root cause

bitbox-api v0.2.1 ethSupported() internally calls wasm.pairedbitbox_cardanoSupported instead of pairedbitbox_ethSupported. This bug persists through v0.12.0. Library update is blocked by ESM/Webpack incompatibility (see #1032).

Test plan

  • Connect BitBox02 Multi (Nova Multi) via Ethereum buy flow → should show ETH address (0x...)
  • Connect BitBox02 BTC-only via same flow → should fall back to BTC address
  • Verify error propagation: invalid blockchain or network errors are not swallowed

Relates to #1032

bitbox-api v0.2.1 has a WASM binding bug where ethSupported() calls
pairedbitbox_cardanoSupported instead of pairedbitbox_ethSupported,
returning false for BitBox02 Multi editions that do support ETH.

Instead of pre-checking ethSupported(), attempt ETH address fetch
directly and only fall back to BTC if the device actually rejects
the request.
@TaprootFreak TaprootFreak marked this pull request as ready for review March 30, 2026 12:47
@TaprootFreak TaprootFreak merged commit bea2405 into develop Mar 30, 2026
6 checks passed
@TaprootFreak TaprootFreak deleted the fix/bitbox-eth-supported-workaround branch March 30, 2026 12:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant