midnight-verify:verify-by-source

Source code verification inspects primary repositories—compiler, ledger, node, and zk—to confirm or refute claims about Compact or Midnight. It routes investigations across the ecosystem and evaluates evidence directly from code, tests, and docs to synthesize accurate conclusions.

Yes, you can validate Midnight claims without compiling by reading source code directly. This process clones repositories when needed and evaluates evidence from code excerpts and tests to confirm architectural claims that cannot be tested by simply running code.

Check the ledger repository to verify transaction structure claims. The process routes investigations across the Midnight ecosystem to the best-fitting repository, selecting the compiler for language semantics, the node for on-chain execution, or the ledger for transaction structures.

Locate and quote exact source definitions to confirm claims about Compact compiler primitives. This source-code driven verification approach inspects compiler sources directly, prioritizing primary source evidence over generated docs to validate specific numerical or architectural claims.

Yes, source code verification prioritizes primary sources over generated documentation. When evaluating claims about Compact or Midnight, the process synthesizes findings with caution, ensuring that evidence from actual code, tests, and primary docs takes precedence over secondary materials.

Avoid source code verification when claims can be tested by compiling and running code. This approach is specifically designed for claims that cannot be validated through execution and require deep inspection of primary repository sources across the Midnight and Compact ecosystems.