Release v0.10.0
Arch Network v0.10.0 (2026-09-14)
Compare: v0.9.0...v0.10.0
Date range: 2026-09-07 → 2026-09-14
Stats: 118 files changed, 6816 insertions(+), 3100 deletions(-)
Top impact areas: o11y (22), e2e-tests (9), db_core (9), validator (8), sdk (8), roast (8), transaction_pool (7), program (7), examples (6), db_utils (6), ha (5), local_validator (4), tpu (3), structs (2), programs (2), execution (2), config-params (2), testing_suite (1), fuzz (1), common (1)
Highlights
Transaction pool reliability received major hardening with atomic proposal outcome recording, unified finalized/failed state handling, and payload purging for completed transactions. Admission checks now apply uniformly across all ingress paths, with validation for oversized transactions and canonical ROAST authentication enforcement.
A new observability system was introduced featuring QUIC-based event streaming, a dedicated o11y service with PostgreSQL backend, and a CLI tool for querying application events and metrics. Storage operations now include retry-on-failure logic for improved resilience.
RPC resource management was improved with bounded resource limits and recoverable block cleanup. Database layer enhancements include migration support and legacy compatibility shim removal following the immutable-UTXO cutover.
SDK and program runtime improvements include stub-based logging when outside VM context and enhanced API stability testing coverage.
Added
- QUIC streams based observability service with PostgreSQL backend for events and metrics
- o11y-cli tool for querying application events from observability service
- Retry logic for storage write operations on failure
- Stub logging infrastructure for operations outside VM context
- Configuration parameters for observability service endpoints
- Database migration support in db_core
- Atomic proposal outcome recording in transaction pool
- Unified finalized/failed transaction state handling
- Schema definitions for observability data in o11y_schema.sql
- QUIC stream client and server implementations for o11y
- Batch processing backend for PostgreSQL in o11y service
Changed
- Transaction pool now purges payload data for completed (finalized/failed) transactions
- RPC resources are now bounded with recoverable block cleanup mechanisms
- Admission checks now applied uniformly across all transaction ingress paths
- Transaction authentication now enforces canonical ROAST signatures (ROAST-01)
- Proposal outcomes reconciled atomically in transaction pool
- Transaction pool startup hardening with improved proposal ordering
- clear_pending recovery logic strengthened in transaction pool
- Block execution report handling updated for unified state model
- Database error types extended for migration and recovery scenarios
- Cargo.lock updates across multiple program workspaces
- System program and examples updated to latest SDK APIs
Fixed
- Oversized transactions are now rejected at admission
- Transaction pool proposal validation gaps addressed
- Transaction pool admission validation gaps contained
- Canonical transaction authentication enforced to prevent malleability
- Finalized transaction payloads now properly reclaimed
- Proposal ordering inconsistencies in transaction pool startup
- clear_pending recovery edge cases resolved
- Transaction ingress path validation inconsistencies eliminated
Performance and Observability
- QUIC-based event streaming infrastructure for low-latency observability data
- Application event observability with structured PostgreSQL storage
- Metrics collection infrastructure via o11y client interface
- Batch processing for efficient PostgreSQL writes in o11y service
- Storage write retry mechanism for improved reliability
- New o11y configuration parameters in validator config
RPC and API Changes
RPC resource bounding changes improve stability but should be transparent to clients. SDK types updated to reflect unified transaction state model (finalized/failed consolidation). No breaking RPC method signature changes.
Breaking Changes
Transaction state model unified: separate finalized/failed states consolidated. Clients relying on granular state distinctions must adapt to the unified completion model. Legacy immutable-UTXO compatibility shims removed.
Migration Guidance
Node operators: Update configuration to include observability service parameters if enabling o11y features. No database migration required for standard upgrades. SDK consumers: Review transaction state handling if code distinguishes between finalized/failed states; both now map to a unified completed state. The immutable-UTXO transition is complete; remove any compatibility workarounds.
Documentation
Updated db_core README with migration documentation. CI workflow updates in .github/workflows/ci.yml. README.md updated with current version information.
Contributors (v0.9.0 → v0.10.0)
Amine ElQaraoui, Marouane, Rahul Subramaniyam