ADAMANT Forging Pool is a blockchain service that calculates and distributes delegate voter rewards on the ADAMANT network. It consists of a Node.js/Express backend that processes forged blocks, computes voter rewards, handles scheduled payouts, and maintains MongoDB storage for blocks, voters, and transactions. The system features a Svelte/Vite web dashboard for monitoring pool status and voter rewards, plus a control CLI (`adm-pool`) for managing encrypted passphrases. Key security features include operator-encrypted passphrases, input validation to prevent NoSQL injection, and secret-free health monitoring. The architecture follows a modular design with clear separation between API handling, business logic, data storage, and external integrations.
Rocket Pool is a decentralized Ethereum liquid staking protocol. The repository contains the complete smart contract system for the protocol, including staking contracts (minipools and megapools), the rETH liquid staking token, node operator onboarding, DAO governance, and a custom RocketStorage key-value storage layer. The codebase is built on Hardhat with comprehensive test coverage, deployment scripts for multiple chains, and a mix of Solidity 0.7.6 (legacy) and 0.8.30 (new) contracts. The architecture follows an upgradeable proxy pattern where contracts fetch the latest implementation address from RocketStorage via getContractAddress(name). The protocol supports two concurrent validator systems: the legacy RocketMinipoolDelegate (0.7.6) and the newer RocketMegapoolDelegate (0.8.30). The test suite is extensive, covering deployment, staking flows, DAO governance, and edge cases, but includes several test-only contracts and helpers explicitly marked not for production use. Notable strengths include production-grade Solidity practices (explicit version pragmas, constant definitions, event emission, role-based access control), event-driven logging for off-chain tracking, and a comprehensive test suite. Notable concerns include mixed Solidity versions, potential reentrancy in some external calls, test-only contracts mixed with production code, and complex settings validation logic that may be brittle.