v14.1.0

v14.1.0

Added

• Implemented TransactionBuilder.addSacTransferOperation to remove the need for simulation for SAC (Stellar Asset Contract) transfers by creating the appropriate auth entries and footprint (#861).

Fixed

• TransactionBuilder.build now adds this.sorobanData.resourceFee() to baseFee when provided (#861).
• The generated XDR type declarations for unions with integer discriminants now use constructors instead of named static methods (stellar/dts-xdr#9) (#874).

Contributors

• @wpalmeri made their first contribution in #831
• @janewang made their first contribution in #835
• @leighmcculloch, @quietbits, @Ryang-21

Full Changelog: v14.0.4...v14.1.0

v14.0.4

v14.0.4

Fixed

• Fixes a bug in Address which prevented it from decoding claimable balances (#825).
• Fixes bugs in Soroban.formatTokenAmount that would cause a lack of leading or trailing zeroes at the decimal point in some cases (#821, #823).

Contributors

• @JakeUrban made their first contribution in #825
• @Shaptic

Full Changelog: v14.0.3...v14.0.4

v14.0.3

v14.0.3

Fixed

• Add conversions for timepoint and duration scval types (#819)

New Contributors

• @mootz12 made their first contribution in #819

Full Changelog: v14.0.2...v14.0.3

v14.0.2

v14.0.2

Fixed

• Lowered the maximum bid for fee-bumped Soroban transactions by not doubling the resource fee (#817).

Contributors

• @Shaptic

Full Changelog: v14.0.1...v14.0.2

v14.0.1

v14.0.1

Fixed

• Added missing Asset.toString() TypeScript definition (#1218).

v14.0.0

v14.0.0: Protocol 23

Breaking Changes

• This package now requires >= Node 20.
• XDR definitions have been updated to align with Protocol 23 (#800).
• Removed the custom Buffer.subarray polyfill introduced in v11.0.1 as a workaround for React Native's Hermes engine. Please use @exodus/patch-broken-hermes-typed-arrays as an alternative, if needed (#795).

Added

• The sodium-native and tweetnacl dependencies have been replaced with @noble/curves (#802).
• Support for claimable balances and liquidity pools in StrKey (#799).
• Support for claimable balances, liquidity pools, and muxed accounts in Address (#801).
• Added the ability for nativeToScVal to convert arrays with differing types to smart contract values (#803). For example,

nativeToScVal([1, "x", "y"], { type: [ "i128", "symbol" ] })

returns a Vec<i128, symbol, string>.

Fixed

• Fix browser compatibility with proper module resolution and UMD configuration (#798).
• Remove MuxedAccount.parseBaseAddress from TypeScript definitions (#797).

Contributors

@overcat @Shaptic

Full Changelog: v13.1.0...v14.0.0

v14.0.0-rc.2: Protocol 23 Release Candidate 2

v14.0.0-rc.2: Protocol 23, Release Candidate 2

Please refer to v14.0.0-rc.1 for more release notes in this major version update.

Fixed

• Correctly encode claimable balances and muxed accounts by @Shaptic in #808

Full Changelog: v13.1.0...v14.0.0-rc.2

v14.0.0-rc.1: Protocol 23 Release Candidate

v14.0.0-rc.1: Protocol 23, Release Candidate 1

Breaking Changes

• This package now requires >= Node 20.
• XDR definitions have been updated to align with Protocol 23 (#800).
• Removed the custom Buffer.subarray polyfill introduced in #733 in v11.0.1 as a workaround for React Native's Hermes engine. Please use @exodus/patch-broken-hermes-typed-arrays as an alternative, if needed (#795).

Added

• The sodium-native and tweetnacl dependencies have been replaced with @noble/curves (#802).
• Support for claimable balances and liquidity pools in StrKey (#799).
• Support for claimable balances, liquidity pools, and muxed accounts in Address (#801).
• Added the ability for nativeToScVal to convert arrays with differing types to smart contract values, e.g., nativeToScVal([1, "x", "y"], { type: [ "i128", "symbol" ]}) will give you a Vec<i128, symbol, string> (#803).

Fixed

• Fix browser compatibility with proper module resolution and UMD configuration (#798).
• Remove MuxedAccount.parseBaseAddress from TypeScript definitions (#797).

Full Changelog: v13.1.0...v14.0.0-rc.1

v13.1.0

v13.1.0

Added

• nativeToScVal now supports encoding Keypairs as addresses (#794).
• Within authorizeEntry, the SigningCallback callback function should now return an object containing both the signature and the identity of the signer. In multi-signature situations, it isn't necessarily the case that the address within the authorization entry is the one that actually signs that entry. Thus, the callback now takes the following form, where the original Promise<BufferLike> option is preserved for backwards compatibility and should be considered deprecated (#783):

export type SigningCallback = (
  preimage: xdr.HashIdPreimage
) => Promise<
  BufferLike |
  { signature: BufferLike, publicKey: string }
>;

Fixed

• scValToNative will decode addresses more efficiently and reliably (#794).

v13.0.1

v13.0.1

Fixed

• Add support for buildInvocationTree to parse V2 of creation calls by @Shaptic in #784
• Add TypeScript definitions for new invocation field by @Shaptic in #785