Releases: Creit-Tech/Stellar-Wallets-Kit
Releases · Creit-Tech/Stellar-Wallets-Kit
Release list
v2.5.0
v2.4.0
2.4.0 (2026-06-24)
Change
- Remove the library @stellar/stellar-base and install @stellar/stellar-sdk (the base version has been deprecated by Stellar)
v2.3.0
2.3.0 (2026-06-05)
Add
- Adds support to sign both messages and authorization entries using WalletConnect (
following https://docs.freighter.app/mobile-walletconnect/signing)
Fix
- It upgrades the Trezor libraries to the latest ALPHA releases. This is because when a website is using modern
bundling (ESM only), the process breaks since the@trezor/connect-plugin-stellarpackage is looking for ESM code
that isn't available in old@trezor/connect-webversions.
v2.2.0
2.2.0 (2026-05-08)
Add
- Adds Fordefi module
- Adds Cactus Link module
Changes
- Update WalletConnect Freighter's ID
v2.1.0
2.1.0 (2026-03-30)
add
- Include PR 84 - adds
signAndSubmitTransactionmethod - Add new method
fetchAddress
v2.0.1
2.0.1 (2026-03-11)
Changes
- Update the recently included Bitget module
- Include PRs 85 and 86
v2.0.0
2.0.0 (2026-02-11)
Changes
- Full refactor of the whole repository (with breaking changes)
- Migrate into a full Deno repository with NPM builds for compatibility
- Separate the UI, the state, and the SDK
- The UI (modal, buttons, etc) is now using Preact with HTM instead of Lit
- The SDK (the class StellarWalletsKit) is now a regular Deno library
- The state part of the SDK is being used by both the UI and the SDK
- The UI now uses a series of CSS variables that can be defined by developers to personalize the complete UI (the SDK
makes this process easier) - The SDK internal state is now using the small preact/signals library instead of RxJS (aiming to reduce the kit's size)
- The SDK now exports the internal state so developers can update it directly if they need to (tho, still not
recommended) - We included 3 simple examples using vite-preact, vite-react, and create-react-app so developers can see how to use the
library - The components used in the library can now be created separately if needed (but like the internal state, not
recommended) - The
openModalmethod was removed, and we now haveauthModal. This new method works as a regular Promise, and it
returns the address after the user has picked their selected wallet - A new
profilepage is added to the kit's modal, so in the future, we will allow having multiple accounts and wallets
connected, so users can switch between accounts directly from the website instead of needing to check their wallets. - Include a new logic for events updates from the kit, developers can `subscribe ' to updates from the kit, like changes
in the selected address, network, module, or disconnections. - The kit now separates the logic between getting the address and fetching the address. This means that if the user
hasn't interacted with theAuthModalbefore, it will throw an error. This will prevent issues with modules that have
different authorization logic (for example, Freighter) - The kit now keeps more information in the localstorage, for example, it will remember the last Wallet Connect topic it
used, so when using Wallet Connect, the user doesn't need to connect again and again. - Freighter and Lobstr are now default wallets in the wallet connect modal, this way users will see them first instead
of regular EVM wallets. - Fully remove both
submitandsubmitUrlparameters - And many more.
v1.9.5
1.9.5 (2025-09-05)
Add
- Update the supported wallets everytime the modal is opened instead of just when the kit instance is created
v1.9.4
1.9.4 (2025-09-05)
Change
- Upgrade Freighter's module so it handles the two different ways Freighter answer to the signMessage method.
v1.9.3
1.9.3 (2025-09-03)
Change
- Upgrade Freighter API's library to latest
Fix
- Update the types in kit's class so it includes the new
skipRequestAccessparameter