ADAMANT Forging Pool v3.1.0 is a recommended update for pool operators.
This release fixes and hardens reward calculation and payout accounting paths, moves pool storage to MongoDB-backed collections, and adds LowDB-to-MongoDB migration tooling for older pool data. It introduces retry-safe per-voter reward progress tracking to prevent duplicate rewards after crashes or partial runs, normalizes stored pending rewards before payout accounting, and adds optional encrypted pool passphrase support. The new adm-pool operator CLI provides encrypt, unlock, lock, and status commands, along with a local owner-only control socket for runtime lock/unlock commands. A /api/health endpoint enables secret-free external monitoring. The dashboard now includes voter and transaction filtering, delegate/voter names, numeric sorting fixes, and improved links. Documentation has been updated for setup, configuration, migration, monitoring, and operator workflows. The runtime baseline is updated to Node.js 22.13.0+ and npm 10+.
This is a recommended upgrade because it includes fixes and safeguards for reward calculations and scheduled payouts. Before upgrading, operators should back up the existing pool config and reward history, review the MongoDB configuration in config.default.jsonc, review the migration guide in README.md, test the migration flow on a copy of existing data, and verify payout settings, donation settings, and maintenance wallet settings after migration. Encrypted passphrases are optional; existing plain passphrase configs remain supported. Operators can encrypt the delegate passphrase with:
npm run adm-pool encryptThen unlock a running pool with:
npm run adm-pool unlock