Clear the active account without destroying the Beacon session.
This removes the active account reference from local storage but does
not clear other Beacon state such as the cached relay node
(beacon:matrix-selected-node) or peer data.
Use this for switching between accounts within an active session. For a full logout that clears all Beacon storage, use disconnect instead.
Disconnect the wallet and clear the active Beacon session.
This is the recommended way to end a user session (logout). It calls
client.disconnect() under the hood, which notifies wallet peers, clears
the active account, and tears down the active Beacon transports.
After calling this method, the BeaconWallet instance can be used to reconnect through a new permission request.
For switching accounts without a full logout, use clearActiveAccount instead.
Request the public key from the wallet
Request the public key hash from the wallet
Transform WalletFinalizeUnstakeParams into a format compliant with the underlying wallet
Transform WalletIncreasePaidStorageParams into a format compliant with the underlying wallet
Transform WalletRegisterGlobalConstantParams into a format compliant with the underlying wallet
Transform WalletTransferTicketParams into a format compliant with the underlying wallet
Optionalrequest: RequestPermissionInputRequest the wallet to send an operation batch
Request the wallet to sign a payload
Optionalwatermark: Uint8Array<ArrayBufferLike>
The underlying Beacon
DAppClientinstance.Exposed for advanced use cases such as subscribing to Beacon events. Calling methods directly on the client (e.g.,
client.clearActiveAccount()) bypasses Taquito's wallet lifecycle. For disconnecting, prefer BeaconWallet.disconnect instead.