Version: 1.44.0

New

• Ability to call async functions via tc_request_sync.
• In rust API, the following functions become sync (slight breaking):
  abi::encode_internal_message, abi::attach_signature_to_message_body, abi::attach_signature,
  abi::decode_message, abi::decode_message_body, abi::decode_account_data,
  abi::update_initial_data, abi::encode_initial_data, abi::decode_initial_data,
  abi::decode_boc, abi::encode_boc, boc::decode_tvc, boc::parse_message, boc::parse_transaction,
  boc::parse_account, boc::parse_block, boc::parse_shardstate, boc::get_blockchain_config,
  boc::get_boc_hash, boc::get_code_from_tvc, boc::cache_get, boc::cache_set, boc::cache_unpin,
  boc::encode_boc, boc::get_code_salt, boc::set_code_salt, boc::decode_state_init, boc::encode_state_init,
  boc::encode_external_in_message, boc::get_compiler_version, processing::monitor_messages,
  processing::get_monitor_info, processing::cancel_monitor
• Code generator for modules.ts produces _sync wrapper for all API functions.

Version: 1.43.3

Fixed

• Memory leak in a spawned loop of the web socket link.

Version: 1.43.2

Fixed

• Non existing accounts are treated as missing since q-server return non existed if account is missing
• Next block awaiting timeout calculation on message with long expiration time

Version: 1.43.1

Fixed

• MonitoredMessage API representation simplified.

Version: 1.43.0

New

• network.network_retries_count config parameter is finally deprecated and not used in SDK.
  max_reconnect_timeout is used instead
• Message monitoring errors received by subscription are returned from
  processing.fetch_next_monitor_results function
• Message monitor buffers new messages for delayed start of the subscription. New subscription
  starts when 1 second has passed since the last addition or when 5 seconds has passed since last sending
• Message monitor uses more than one subscription.
• Version of ton_types upped to 2.0.0
• Fixed code for changed dependencies api
• Removed logic related to client-server clock sync
• boc.encode_tvc and boc.decode_tvc are renamed to boc.encode_state_init
  and boc.decode_state_init.
• boc.decode_tvc decodes TVC BOC according to the TVC spec.
• DeploySet.tvc supports new TVC file format (according to new TVC spec).
  Old tvc files (with serialized state init) are also supported.
• DeploySet.state_init allows to specify serialized state init.
• DeploySet.code allows to construct state init from provided serialized code.
• DeploySet's fields tvc, state_init and code are mutually exclusive (so you should
  provide value for one of these fields).
• ProcessingEvent::MessageExpired is sent to callback in case of retry in processing.process_message

Version: 1.42.1

[1.42.1] – 2023-03-23

Fixed

• Client was notified about every REMP status timeout. Now it is notified only once when fallback
  scenario is started

Version: 1.42.0

[1.42.0] – 2023-03-22

New

• Added message monitoring functions to the processing module: monitor_messages,
  fetch_next_monitor_results, get_monitor_info, cancel_monitor****.
• Added processing.send_messages function.
• Improved error resolving for deleted accounts
• net.first_remp_status_timeout config parameter default value set to 1 ms in order to start
  fallback scenario together with REMP statuses processing while REMP is not properly tuned yet.
• Network errors are returned on subscription creation if occured

Fixed

• ParamsOfSubscribe was not public.
• subscribe did not trim subscription query text. It is required for some graphql servers
  expecting that query text starts from operation text.

Version: 1.41.1

[1.41.1] – 2023-03-14

Fixed

• api_derive compilation errors

Version: 1.41.0

[1.41.0] – 2023-02-13

New

• CapSignatureWithId capability is supported.

  Network signature ID is used by VM in signature verifying instructions if capability
  CapSignatureWithId is enabled in blockchain configuration parameters.

  This parameter should be set to global_id field from any blockchain block if network can
  not be reached at the moment of message encoding and the message is aimed to be sent into
  network with CapSignatureWithId enabled. Otherwise signature ID is detected automatically
  inside message encoding functions.
  Overwrite priority: ExecutionOptions.signature_id -> ClientConfig.network.signature_id -> last network block

  • ClientConfig.network.signature_id optional parameter is added. Specify it in case of offline work for all message signing operations to use.
  • ExecutionOptions is extended with signature_id optional parameter. Specify locally for a particular run_tvm or run_executor call.
  • net.get_signature_id function returns global_id if CapSignatureWithId capability is enabled,

• message_id and message_dst fields are added to all ProcessingEvent variants

• Config parameter binding: { library: string, version: string }. Binding authors should define
  this parameter at context initialization.

• tonclient-binding-library and tonclient-binding-version GraphQL request headers.

• Error.data.binding_library and Error.data.binding_version error data fields.

Client breaking changes

• abi.get_signature_data function ouput parameter hash is renamed to unsigned for consistency with other crypto functions parameters

Possible breaking change on binding side

• Changed type of the dictionary parameter or mnemonic crypto functions and crypto config.
  Now it uses MnemonicDictionary enum type instead of number. MnemonicDictionary numeric
  constants are compatible with previous values.

Deprecated

• debot engine module is deprecated. Debot engine development has migrated to a separate repository (soon will be published). So, in order to reduce sdk binary size, we will remove debot engine module from sdk in the next releases.

Version: 1.40.0

[1.40.0] – 2023-01-11

New

• abi.get_signature_data function that returns signature from message and hash to verify the signature

Improvement

• local endpoints with port specified are expanded with http protocol instead of https (e.g.
  localhost:8033 in expanded to http://localhost:8033/graphql)