Tari Release Notes – v5.0.0-pre.0

Compatibility

Version 5.0.0-pre.0 introduces configuration-breaking changes. It is not backward-compatible with wallets or base nodes that still rely on legacy peer or gRPC transport configuration. This release builds on the migration to HTTP-based wallet query services introduced in the 4.10 pre-release series.

Wallets running older configurations that specify custom_base_node must update their configuration files. Legacy settings will now cause initialization failures.

Breaking Changes

• Legacy custom_base_node settings removed:
  All legacy methods for specifying a custom base node have been deprecated and removed. This includes:

  • CLI flags: -p "wallet.custom_base_node=...", wallet.custom_base_node_peer, wallet.custom_base_node_grpc
  • Configuration keys: [wallet.custom_base_node], wallet.custom_base_node_peer, etc.

  Wallets must now use the HTTP-based configuration introduced in earlier versions. If your wallet config includes any of the deprecated keys or flags, you must remove them or generate a fresh configuration.

Features

• Clean wallet configuration system:
  Legacy support for peer-based base node connections has been fully removed, streamlining the configuration model and reducing errors related to unsupported connection types. Users are required to use HTTP-based endpoints for wallet-to-base-node communication.

Bugs Fixed

• System DNS improvements:
  DNS resolution has been enhanced with support for EDNS0, TCP fallback, and faster timeout handling. These changes improve connectivity on constrained or misconfigured networks.

• Block duplication prevention:
  Resolved an issue that could lead to the same block being inserted multiple times during scanning. This fix improves scan performance and ensures data consistency in the wallet database.

Deployment

To safely upgrade to v5.0.0-pre.0:

1. Back up your data — including the Console Wallet and Base Node data directories.
2. Stop all running services — Console Wallet, Base Node, and any FFI integrations.
3. Install the latest binaries for both the Base Node and Console Wallet.
4. Update your configuration files:
   • Remove all instances of wallet.custom_base_node and any related peer-based settings.
   • Ensure your configuration uses the new HTTP-based approach introduced in prior versions.
5. Restart all services after configuration cleanup.
6. Verify sync and query operations to confirm successful migration.