Tari v0.32.0 Released

The main change in v0.32.0 is the reworked configuration system. Most users won’t be aware of any changes, but now any spelling errors or invalid configuration settings will be picked up. Previously, any configuration settings would need to be mapped in code which meant that if a setting was never mapped, changing it in the config file would have no effect. More importantly, you’d have no indication of whether it was being used or if you’d even spelled it correctly.
If you are already running a Tari node, the easiest will be to delete the
folder and use the config file that is generated on startup. If you’d like to keep your settings, let us know on
Discord
and we’ll help you migrate it.
All Changes since v0.31.1
Features
allow network to be set by TARI_NETWORK env var (
add list assets command (
check achieved Monero difficulty before submitting to Tari basenode (
adds tor.forward_address setting (
add total hashrate chart (
Bug Fixes
add Environment cfg source and remove –create-id (
assign correct base dir to tor identity (
saf storage uses constructs correct msg hash (
sets file default for DHT db (
use correct cloudflare resolver default (
fix github integration tests (
ignore test that timeout in github action (
remove floating point math from mnemonic code (
launchpad build docker images (
fix config presets (
long running and non critical github action (
makes header consensus encoding infallible (
only count base nodes in peers count in base node status (
prevent seed peer address from being overwritten unless newer (
support safe non-interactive mode (
test_output_manager_sqlite_db(_encrypted) (
update daily test configuration (
do not prompt for password if given in config (
ensure block hash exists (
weird behaviour of dates in base node banned peers (