Repository navigation
Releases
@walletconnect/utils@2.26.0
Patch Changes
-
#7328
c247899Thanks @ganchoradkov! - FixhashEthereumMessageprefixing the JavaScript string length (UTF-16 code units) instead of the UTF-8 byte length required by EIP-191. Any SIWE/CACAO message containing a non-ASCII character (e.g. a localized or emoji statement, or a Unicode domain) hashed to a value that no compliant signer produces, soeip191andeip1271verification deterministically failed for every wallet type. Hashes of ASCII messages are unchanged; this restores the pre-2.18.0 behaviour (ethershashMessage). Consumers callinghashEthereumMessagedirectly now receive the standard EIP-191 hash for non-ASCII input. -
Updated dependencies [
22c6e93]:- @walletconnect/types@2.26.0
@walletconnect/universal-provider@2.26.0
@walletconnect/types@2.26.0
Minor Changes
- #7364
22c6e93Thanks @ignaciosantise! -eventClient.init()now accepts an optional{ sdk: { name, version } }so SDKs built on top of core (e.g. WalletKit) can report their own version. When provided, it's sent assdk_name/sdk_versionproperties on the eventsINITevent, alongside the existing coreuser_agent.
@walletconnect/signer-connection@2.26.0
@walletconnect/sign-client@2.26.0
@walletconnect/react-native-compat@2.26.0
@walletconnect/react-native-compat@2.26.0
@walletconnect/pos-client@1.0.13
@walletconnect/pay@1.1.1
Patch Changes
- Updated dependencies [
c247899]:- @walletconnect/utils@2.26.0
@walletconnect/ethereum-provider@2.26.0
Patch Changes
-
#7356
78c4e04Thanks @ganchoradkov! -EthereumProvider.initnow forwards theclientandcoreoptions toUniversalProvider.init. Previously they were accepted by the type but silently dropped, so a new Sign Client and Core were always created. Passing an existing@walletconnect/sign-clientor@walletconnect/coreinstance now reuses it, matchingUniversalProvider.init. -
Updated dependencies [
c247899,22c6e93]:- @walletconnect/utils@2.26.0
- @walletconnect/types@2.26.0
- @walletconnect/universal-provider@2.26.0
@walletconnect/core@2.26.0
Minor Changes
- #7364
22c6e93Thanks @ignaciosantise! -eventClient.init()now accepts an optional{ sdk: { name, version } }so SDKs built on top of core (e.g. WalletKit) can report their own version. When provided, it's sent assdk_name/sdk_versionproperties on the eventsINITevent, alongside the existing coreuser_agent.