mirror of
https://github.com/luxfi/bridge.git
synced 2026-09-24 00:26:46 +00:00
zeekay
15e43615f1
The dependency was pinned "^0.1.0", which under semver can never reach 0.2.x. So the bridge — a surface listed as a working consumer of the shared connector — was carrying the bug 0.2.0 fixed. Measured in the installed tree: 0.1.0's dist/connectors.js opens with SEVEN STATIC IMPORTS, so every page load eagerly pulled sats-connect, @tonconnect/sdk, @crossmarkio/sdk and @polkadot/util-crypto whether or not anyone touched those chains. That is the eager-import shape that blanked the exchange SPA. 0.2.1's connectors.js has zero: a chain's wallet library arrives when that chain is asked for. getConnector became async across that boundary, so resolveConnector is async and its one caller awaits. Both call sites were already inside async functions, which is why this is three lines rather than a refactor. Cardano now maps to a connector instead of null. The comment beside it said connect was unavailable — true when written, and 0.2.1 ships ./cardano/connect (CIP-30) with ./cardano/verify (CIP-8 COSE_Sign1). Same day as the ADA custody address, from the other side: the register can now name a Cardano deposit address, and a holder can now sign in with the wallet that holds it. EVM and Lux still return null and go through wagmi deliberately. @luxwallet/connect has no transaction surface at all — no sendTransaction, no chain switching, verified by grep — so it is a connect-and-identity package, not a wagmi replacement. The comments say that now instead of implying a gap.