Docs & Schema: Top Accounts, client WebSocket events, and consensus visibility

[dev-adamant-im]

We aligned adamant-docs and adamant-schema with the current ADAMANT node API surface: additive REST fields, Socket.IO client events, corrected query semantics, and operator recovery guidance. No consensus fork or wire-format break — changes are backward-compatible.

Live surfaces:

• Docs: https://docs.adamant.im
• OpenAPI: https://schema.adamant.im

Top Accounts API

GET /api/accounts/top is now part of the public contract. Ordering is deterministic: balance DESC, then address ASC. Supports limit / offset, optional isDelegate, response metadata (count), and limit=0 for count-only requests. The legacy topAccounts config switch is gone — the endpoint is registered on every node.

• Docs: Accounts — Top Accounts
• Schema: Adamant-im/adamant-schema#44
• Docs PR: Adamant-im/docs#29
• Node: Adamant-im/adamant#260

Client WebSocket: newBlock and balances/change

The client Socket.IO interface gained opt-in compact newBlock events and field-level balances/change payloads (balance, unconfirmedBalance, or both). Subscriptions are indexed (address, types, assetChatTypes, balances, blocks). Delivery remains best-effort and non-durable — reconnect, re-subscribe, and reconcile critical state via REST.

The OpenAPI package documents this under x-client-websocket with dedicated schemas under specification/websocket/.

• Docs: WebSocket
• Schema: Adamant-im/adamant-schema#48
• Docs PR: Adamant-im/docs#35
• Node: Adamant-im/adamant#264

Status schedules and delegate forged

Public status APIs now expose the effective consensus activation schedule and the full block-reward milestone schedule:

• consensusCodeName
• consensusSchedule.activationHeights
• milestoneSchedule (offset, distance, milestones)

Delegate list/get responses include lifetime forged as a base-10 integer string (base units). Next-forger projection uses the next block height at round boundaries. Schema also fixed producedlocks → producedblocks and completed query-parameter coverage for peers, queued/unconfirmed transactions, and delegate search/orderBy.

• Docs: Node and Blockchain, Delegates
• Schema: Adamant-im/adamant-schema#51
• Docs PR: Adamant-im/docs#37
• Node: Adamant-im/adamant#266

Blocks API alignment

GET /api/blocks query semantics are aligned with node behavior: numberOfTransactions=0 works correctly; orderBy, amount filters, and offset-after-ordering are documented accurately. Schema adds full parameter coverage and generatorPublicKey on BlockInfoDto. Incorrect timestampMs examples were removed from the docs.

• Docs: Blocks
• Schema: Adamant-im/adamant-schema#46
• Docs PR: Adamant-im/docs#33
• Node: Adamant-im/adamant#263

Operator recovery: mem-table checkpoints

Persisted rotating mem_* checkpoints (loading.memCheckpoints.enabled, on by default) are documented for crash recovery: SHA-256 verification, fail-closed restore, fallback to full deterministic rebuild, storage impact, and graceful shutdown (SIGINT/SIGTERM → wait for Cleaned up successfully). Checkpoints are a local recovery cache; canonical blocks remain the source of truth.

• Docs: Installation, Configuration
• Docs PR: Adamant-im/docs#31
• Node: Adamant-im/adamant#261

Release PRs

Repo	Release PR	Tracking issue
docs	Adamant-im/docs#39	#38
schema	Adamant-im/adamant-schema#53	#52

Node context: adamant@v0.10.2. Downstream consumers (especially adamant-api-jsclient) should regenerate types from the updated OpenAPI bundle.

[massivedev0]

Amazing update, thanks.