Core API

Behavior shared by every chain, in four groups. The connection is lazy — the transport (and the popup) is created on the first request method (info, getDeviceInfo, setLabel, an Account API method or sign()), so the lifecycle setters are cached and applied on connect.

Connection API

Method	Purpose
setTransport	Choose WebHID or Bluetooth. v2 new
setConnectionListener	Popup 'connected' / 'disconnected' events, plus the separate device axis in the second argument — including the device-screen approval wait ('awaiting-connect-approval') and the disconnect reason (deviceReason) — the second argument is v2 new
setSignProgressListener	Signing progress (step / total). v2 new
setTimeOutMs	Request timeout.
popupWindowClose	Close popup, release transport.

Device API

Method	Purpose
info	Bridge popup status probe.
getDeviceInfo	Device id, firmware, label.
setLabel	Set the device label.

Account API

Method	Purpose
getAddress	Address for a chainId + keyPath.
getAccountInfo	Registered account list.
syncAccount	Register / sync accounts.
getPublicKey	Account public key(s). v2 new
getXPUB	Extended public key.
selectAddress	Address picker dialog.

Sign API

A single entry point — sign({ method, chainId, payload }) — covers signTransaction / signMessage / signTypedData / signData / signAuthEntry.

• setTransport
• getAddress
• sign()