Migrating from Connector v1

Two things change for your app code, and one thing changes for your users.

	v1	v2
Sign call	21 per-coin functions (getEthereumSignedTransaction, …)	single sign({ method, chainId, payload })
Network id	coinType enum (dcent.coinType.ETHEREUM)	chainId (CAIP-2/19, 'eip155:1/slip44:60')
Key path	key / path args	payload.keyPath
Response	V1Response	same V1Response — but signed_tx → signature
Connection	Bridge app install + USB only	browser-direct (WebHID / BLE) + setTransport
Device / lifecycle	getDeviceInfo / setConnectionListener / …	same names (+ new setTransport). setConnectionListener keeps its v1 first argument but gained a second one and fires more often — that second argument also reports the device-screen approval wait ('awaiting-connect-approval') and why a connection dropped (deviceReason). See its page.

tip

For users: no more Bridge download, and Bluetooth now works. For your code: Device/Account APIs stay nearly identical; only the Sign API consolidates into sign(), and you read signature instead of signed_tx.

Checklist

• Replace getXxxSignedTransaction(...) → sign({ method:'signTransaction', chainId, payload })

• Map coinType → chainId (table)

• Rebuild positional EVM args into a transaction object

• Change response parsing: signed_tx → signature (details)

• Add setTransport('hid'|'ble') (details)

• Sign API mapping

• coinType → chainId

• Response changes