Release 3.0.0
[3.0.0] - 2026-06-05
Upgrading from 2.x? See
docs/MIGRATION-3.0.md
for a step-by-step migration guide covering the dapp_id changes below.
Changed (breaking)
- Default HD key derivation path changed from
m/44'/396'/0'/0/0tom/44'/1331'/0'/0/0. Crypto functions (tvm_client) and key/address generation (tvm_cli) that rely on the default path now derive different keys from the same seed phrase. To keep previous keys, pass the old path explicitly. tvm_client:ParamsOfGetAccount.addressrenamed toaccount_id; now strict 64-character hex (no0x, no workchain). Added requireddapp_idfield.tvm_client:ResultOfGetAccount.dapp_idis nowString(notOption); addedaccount_idfield.tvm_client:ParamsOfSendMessage.dst_dapp_id: Option<String>renamed todapp_id: String(empty allowed only for pre-1.0.0 servers).tvm_client:ResultOfSendMessagenow exposesaccount_idanddapp_id(always populated; derived from the request when the server doesn't return them).tvm_client:ParamsOfProcessMessage.dst_dapp_idrenamed todapp_id: String.tvm-clinow requires thedapp_id::account_idaddress form on all commands and against all nodes; legacy0:<hex>and bare-hex address inputs are no longer accepted.tvm-clideploy/deployxnow always require--dst-dapp-id(including--feemode); pass all zeros for a self-rooted dapp.tvm-cligenaddradditionally prints thedapp_id::account_id(dapp_accountin JSON) self-rooted form.
Added
tvm_client: SDK version-gates/v2/accountand/v2/messageswire formats based on GraphQLinfo.version. v>=1.0.0 sends newdapp_id/account_idfields; v<1.0.0 keeps legacyaddress/dst_dapp_id.tvm_client: newServerLink::server_version()andServerLink::supports_dapp_id()helpers.