Release v0.8.2

Release v0.8.2
Arch Network v0.8.2 (2026-08-19)
Compare: v0.8.1...v0.8.2

Date range: 2026-08-18 → 2026-08-19

Stats: 96 files changed, 2417 insertions(+), 1083 deletions(-)

Top impact areas: roast (30), e2e-tests (19), examples (9), db_utils (6), key_mng (5), db_core (5), common (4), validator (3), tpu (3), runtime (3), blockstore (3), bitcoin-internal (2), state-sync (1), fuzz (1), Cargo.toml (1), Cargo.lock (1)

Highlights

Error handling infrastructure was significantly enhanced with the introduction of call site context propagation across all major subsystems including roast, blockstore, db_core, key_mng, runtime, tpu, and validator. This provides more precise error diagnostics for debugging and monitoring production issues.

Finality and consensus improvements address edge cases in state synchronization with a new state-only finality sweep backstop mechanism in db_utils and canonicalization of Titan lookup errors in hash-committed status validation. Bitcoin block confirmation threshold values were updated to align with operational requirements.

Testing and dependency infrastructure was updated across all e2e-tests and example programs with synchronized Cargo.lock files, ensuring consistent dependency resolution across the test suite and example applications.

Added

• Call site context tracking in error codes via new err_context module in common crate
• State-only finality sweep backstop mechanism in db_utils finality handling
• Error context propagation infrastructure across roast, blockstore, db_core, key_mng, runtime, tpu, and validator subsystems

Changed

• Updated Bitcoin block confirmation values in configuration
• Canonicalized Titan lookup error handling in hash-committed status validation
• Refactored error types across multiple subsystems to include call site context
• Synchronized Cargo.lock files across all 19 e2e-test programs and 9 example programs
• Version bumped to 0.8.2 in common/src/version.rs and Cargo.toml

Fixed

• Canonicalized error reporting for Titan lookup failures in hash-committed status checks
• Added backstop to prevent state-only finality sweep edge cases from causing synchronization issues

Performance and Observability

• Enhanced error diagnostics with call site context propagation enabling more precise root cause analysis
• Improved error traceability across roast consensus, storage, and runtime subsystems

RPC and API Changes

No breaking RPC or API changes. Error return types now include additional context fields for enhanced debugging, but remain backward compatible in structure.

Breaking Changes

None known.

Migration Guidance

No action required for node operators or SDK consumers. The enhanced error context is automatically included in error responses and does not require configuration changes.

Documentation

No documentation changes in this release.

Contributors (v0.8.1 → v0.8.2)

Amine ElQaraoui, Deepanshu Hooda, Rahul Subramaniyam