v4.3.0
4.3.0 (2024-09-04)
Breaking Changes
WalletConnectCommunicationClient
constructor now expects a function as a parameter. This function must check whether the current tab is the leader. [1]- Since version 4.2.0, subscribing to the event
ACTIVE_ACCOUNT_SET
is mandatory. You can read more here.
Changelog
- Added broadcast-channel support for managing multiple tabs when connected to WalletConnect.
- Adjusted CSS
font-size
unit for better scaling. - Added support for all public key types in
session_update
. - Now possible to send both the account’s address and public key in
session_update
. [2] - WalletConnect now includes the SDK version in the
sessionProperties
ofEngineTypes.ConnectParams
duringSignClient.connect
. - Updated Tezos operation types.
Developer Notes
[1] This change prevents multiple WalletConnect signClient
from being created, avoiding “No matching keys” errors. If you need to get familiar with broadcast-channel, we have published an example here
[2] Sending both the account’s address and public key is optional. The order matters: in namespaces.accounts
, the address must come first (index 0), followed by the public key (index 1).