Consensus
Map block validation, proof-of-work checks, difficulty rules and chain-selection logic.
Source auditTransaction Validation
Compare transaction verification, input/output handling, standardness and policy rules.
Source auditNetworking
Review peer discovery, message handling, relay behavior and connection management.
Source auditWallet
Map key management, address handling, transaction creation and wallet database behavior.
Source auditMining
Compare PoW implementation, block assembly, nonce handling and difficulty calculations.
Source + testTesting & Maintenance
Record available unit tests, integration tests, releases, changes and reproducibility conditions.
Repository auditAudit Matrix
The matrix below defines what the research team should collect. “Better” is not assigned until code evidence and an explicit evaluation criterion exist.
How the Code Audit Works
Freeze Versions
Record exact repository commits or tagged releases before comparing files.
Map Components
Match equivalent modules and document where the implementations diverge.
Read the Logic
Inspect consensus-critical paths rather than judging projects from file counts alone.
Reproduce
Build, run tests and record the exact environment used for each finding.
Document
Publish code excerpts only as needed, with commit references and explanations.
Evaluate
Apply predefined criteria such as correctness, performance or maintainability.