Skip to content

Release v0.8.5

Latest

Choose a tag to compare

@hoffmabc hoffmabc released this 25 Aug 13:50

Release v0.8.5
Arch Network v0.8.5 (2026-08-25)
Compare: v0.8.4...v0.8.5

Date range: 2026-08-22 → 2026-08-25

Stats: 61 files changed, 2055 insertions(+), 372 deletions(-)

Top impact areas: e2e-tests (19), examples (9), validator (7), o11y (7), roast (5), transaction_pool (3), local_validator (2), config-params (2), token-metadata (1), testing_suite (1), sdk (1), fuzz (1), common (1), Cargo.toml (1), Cargo.lock (1)

Highlights

The token metadata program now adopts prefunded PDA accounts instead of erroring out when accounts exist, improving resilience and reducing deployment friction. A new security check has been added to the token metadata processor to reject forged accounts, strengthening account validation.

Program deployment batches now use fresh latest-block-hash values for each batch rather than reusing older hashes, improving transaction reliability and reducing the likelihood of stale block hash errors.

Initial observability infrastructure has been introduced with PostgreSQL-backed telemetry schema and client implementation. The new o11y subsystem provides structured instrumentation across validator, roast coordinator, and transaction pool components.

Added

  • New o11y subsystem with PostgreSQL schema (o11y_schema.sql) for telemetry and observability data
  • PostgreSQL client implementation for observability data ingestion (o11y/src/client/pg_client.rs, pg_types.rs)
  • Configuration parameters for observability settings in validator default config (validator/default-config-params.toml)
  • Security check in token metadata processor to reject forged accounts
  • Support for prefunded PDA accounts in token metadata program

Changed

  • Program deployment batches now fetch and use fresh latest-block-hash for each batch instead of reusing stale values
  • Token metadata program behavior updated to adopt existing prefunded PDA accounts rather than returning errors
  • Observability client module refactored with new error types and PostgreSQL type definitions
  • Validator context updated to integrate observability client initialization
  • Roast coordinator components (block_maker, request, response) updated with observability integration points
  • Transaction pool hybrid implementation instrumented with observability hooks
  • Local validator library updated to support observability configuration
  • Version bumped to 0.8.5 in common/src/version.rs
  • Dependency updates across all e2e-tests, examples, and fuzz test Cargo.lock files

Fixed

  • Fixed potential stale block hash errors in program deployment by refreshing block hash per batch
  • Fixed token metadata program error when encountering prefunded PDA accounts

Performance and Observability

  • Added PostgreSQL-backed observability infrastructure for structured telemetry collection
  • Instrumented validator RPC methods with observability hooks
  • Added telemetry collection points in transaction pool operations
  • Integrated observability client into roast coordinator for consensus metrics

RPC and API Changes

No breaking RPC changes. The SDK async program deployment helper has been updated to fetch fresh block hashes per deployment batch, improving reliability without changing the public API surface.

Breaking Changes

None known.

Migration Guidance

Node operators who wish to enable the new observability features should configure PostgreSQL connection parameters in their validator configuration. Existing deployments will continue to function without observability enabled. No action is required for SDK consumers.

Documentation

Updated validator default configuration template with observability parameters.

Contributors (v0.8.4 → v0.8.5)

Amine ElQaraoui, Marouane, Rahul Subramaniyam