tempoxyz/tempo v1.7.1

Release v1.7.1

on GitHub

Tempo v1.7.1 adds support for migrating validators to minimal nodes, the better default for validators: lower disk requirements, faster rebuilds from snapshots. Migrating from archive v1 to minimal v2 reduces validator node size approximately as follows:

This is not a network upgrade.

New Features

Validators

• Supports validator migration to minimal snapshots. Validators should migrate to the minimal snapshot profile by default when they do not need archive-style historical RPC data.
• tempo download --minimal --force downloads the minimal snapshot component set and replaces existing snapshot data in the datadir while preserving node identity/network files such as discovery-secret and known-peers.json. Note the expected downtime on mainnet: 10mins, testnet: 60mins.

See the running a validator docs for more information on how to see if you’re running a minimal node and how to migrate, as well as the Snapshots UI for reference.

RPC nodes

• Trustless RPC: Moderato Testnet now supports certificate checks when running RPC nodes. This increases security assumptions by reducing trust in the upstream RPC and will become the default in a follow-up release. Trustless RPC requires consensus finalization certificates from the upstream RPC, guaranteeing that the data they receive is backed by a validator quorum. Opt in by using --follow.experimental.certify; see the tempo rpc node docs. Because trustless RPC nodes will have their certificate store prepopulated, this will allow better failover setups.

What's Changed

• Finalized block storage in the consensus layer is now automatically pruned. To make sure node software can roll back to a previous release, in this release blocks will be written to both the new prunable and the old legacy storage. To opt out of the legacy storage entirely, use --consensus.no-legacy-archive. This double-write will be removed in a future release. (#3870)

Full Changelog: v1.7.0...v1.7.1