ADAMANT blockchain node v0.10.2 is a reliability, recovery, and API capability release for node operators, delegates, explorers, messengers, and service developers. It helps nodes recover from stalled synchronization and interrupted shutdowns, adds richer REST and Socket.IO data access, corrects delegate API regressions, improves large-database queries, and refreshes dependencies and operator guidance. Upgrading is recommended for improved reliability, recovery time, security maintenance, and API capabilities, but it is not mandatory for network compatibility. This release introduces no consensus fork and does not change block or transaction serialization, signatures, delegate ordering, rewards, fees, activation heights, slot timing, or deterministic replay.
The API updates include a new top accounts API with deterministic ordering, pagination, isDelegate filtering, response metadata, and count-only requests. Delegate rank correctness is restored, and the delegate voters API is fixed to prevent falling through to all accounts while adding address-list filtering. Consensus visibility is improved by exposing the effective consensus activation schedule and the complete block reward milestone schedule through status APIs. Delegate forged amounts are added to responses, next-forger projection is stabilized at round boundaries, and blocks filtering correctly supports queries with zero transactions.
The client WebSocket API adds opt-in compact newBlock events and balances/change events for balance, unconfirmedBalance, or both. Block, transaction, and balance subscriptions are now indexed to prevent scanning unrelated clients. Affected account reads are batched around block apply/rollback, and publication failures are isolated from consensus-state mutation. Delivery remains best-effort and non-durable, so clients should restore subscriptions after reconnecting and reconcile critical state through REST.
Protocol and consensus rules remain unchanged, though the effective activation schedule and active consensus codename are now observable through public status APIs. The next-forger fix only corrects a previously incorrect public API projection at round boundaries. No consensus rules, activation heights, transaction or block bytes, IDs, signatures, rewards, fees, round settlement, or replay behavior change in this release.
Reliability and recovery improvements include a sync watchdog that detects synchronization runs making no block-height progress for five minutes, safely aborting the stalled run and allowing automatic recovery. PostgreSQL rejections are now propagated through block verification and loading instead of silently parking callback chains. Persisted mem-table checkpoints with three rotating, SHA-256-verified slots are added for derived state. Recovery is fail-closed, restoring only checkpoints that pass all checks and falling back to a full deterministic rebuild if verification fails. Canonical blocks and deterministic replay remain the source of truth.
Security updates include dependency updates within current major versions and the removal of an unused direct npm runtime dependency. A narrow compatible grunt to js-yaml override is added, reducing the audited dependency graph to zero moderate, high, or critical findings. No signature, mnemonic, transaction validation, peer handshake, or cryptographic protocol behavior changes are introduced.
Networking, database, and performance improvements feature a partial balance index for deterministic top-account queries. The blocks generator hash index is replaced with a composite B-tree index to avoid full-table scans for unknown generators. Indexed Socket.IO subscriptions and batched final-state reads reduce unnecessary client scans and account queries, and rotating checkpoint storage enables faster recovery from inconsistent derived state.
For node operations and tooling, persisted memory-state checkpoints are enabled by default, while preserving the full-rebuild fallback for invalid or stale checkpoints. Graceful shutdown is clarified, requiring a wait for active processing to drain and a “Cleaned up successfully” message before restarting. The native pg-native and libpq Node ABI rebuild path is documented, and the Node.js requirement remains 22.13.0 or newer.
Developer experience improvements expand test coverage for synchronization recovery, checkpoints, accounts, delegates, blocks, status APIs, and Socket.IO flows. The README is reorganized, and companion documentation and OpenAPI changes are aligned for the updated APIs.
Operators upgrading to this release should use Node.js 22.13.0 or newer and back up the database. Stop the node gracefully and wait for the “Cleaned up successfully” message before deploying v0.10.2. The first startup will require additional time and disk space to finish all migrations, create checkpoint storage, and build new indexes. After startup, verify node status, synchronization progress, live block processing, and any REST or Socket.IO capabilities used by your services.
Breaking changes
There are no protocol, consensus, wire-format, or API contract-breaking changes in v0.10.2. New REST fields and Socket.IO subscriptions are additive and backward-compatible. The legacy topAccounts configuration switch is removed, and the GET /api/accounts/top endpoint is now registered consistently on every node. The release adds forward-only database migrations, meaning the first startup after upgrading may need additional time and disk space to create checkpoint storage and account/block indexes.