Tari Release Notes – v5.1.0-pre.4

Breaking changes

• The introduction of the full burn-claim lifecycle results in previous burn proofs in the wallet being deleted. In addition, there are several breaking changes in the following:
  • Replacement of range_proof and CommitmentSignatureBase64 with Signature (compressed Schnorr) in messages like CreateBurnTransactionResponse.
  • Schema changes in the wallet database: the burnt_proofs table is replaced with a new burn_proofs schema, which is not backward-compatible.
  • Removal of older CLI and gRPC paths (BurnTari, BurnMinotari), and renaming BurntProof to BurnClaimProof.

Features

• Introduces full end-to-end support for burn-claim proofs from Layer 1 to Layer 2, enabling users to generate, store, and verify Merkle proofs for burned outputs. It replaces Ristretto-based ownership proofs with more efficient compressed Schnorr signatures, adds new wallet RPCs, database schemas, client/server APIs, and UI/CLI support. Additionally, it updates internal proof handling across the wallet, node, and transaction layers for improved performance and scalability.

• Removed the need to set a TCP address as a requirement for running a TCP node; the only requirement now is to set the base_node.p2p.transport.type in the configuration file to tcp

• Dynamic fee estimation is now applied across sends (including multisend, one-sided, and multisig), and memos/payment metadata reflect computed fees.
  Per-recipient optional recovery/encryption key support added for improved payment recovery handling.

Fixes

• Corrects an issue where the payment_id was not being included in outbound transactions of recovered wallets.
• Fixed the ledger app to use the latest version of the ledger_sdk