Evidence
Most networks ask you to trust a whitepaper. Nitrograph publishes the census, the policies, and the results, and ships checked-in verifiers that fail the build when reality drifts from the claim.
Independent audit
The Nitrograph Base v0.1.0 baseline completed an independent review.
- Classification: baseline accepted with required corrections.
- No CRITICAL or HIGH severity findings.
- Private agent-native development: approved.
- Public testnet: not approved yet: remediation of the required corrections and the network qualification program come first.
The audit is not a badge. The findings drive the current hardening workstream, and the remediation state is reflected in Status. The full report is available to partners on request.
Certification policies (re-runnable)
Two policy suites run against every change, and both include mutation controls: tests that deliberately introduce prohibited content and require the policy to reject it. The controls are themselves tested.
Build and supply-chain policy. The runtime is native-only and inventoried exactly: runtime dependencies, application JAR content, binary content, exact classpath, service providers, module requirements, native libraries, and a reconciled artifact inventory of the distribution.
Execution-boundary policy. No successful contract creation, contract call, VM execution, or executable local contract query exists. Eight execution-shaped rejection probes must be rejected deterministically; the boundary fails closed, provably.
Lifecycle certification. Live four-node runs cover genesis, native state creation, saved states, restart, a real stale-learner reconnect with transferred-state hash comparison, and post-reconnect processing, with evidence artifacts (environment data, configuration checksums, node logs, state-hash evidence, and result summaries) retained per run.
Mirror certification. A pinned, unmodified upstream mirror importer ingests the network's record and block streams, including corruption and missing-file controls, proving the external evidence boundary holds for independent consumers.
The executable-boundary census
| Boundary | Count |
|---|---|
| Successful contract creation sites | 0 |
| Successful contract call sites | 0 |
| Ethereum execution sites | 0 |
| Executable local contract-query sites | 0 |
| Intentional rejection probes | 8 |
| Unclassified executable sites | 0 |
Updated per release. A change that alters any zero fails CI.
Provenance
Nitrograph Base preserves its open-source lineage and Apache License 2.0 attribution. The accepted baseline is frozen at an immutable tag with a separate read-only reference copy; a committed, hash-verified retained-file manifest guards the source tree, and integrity verifiers reject changed, missing, or unexpected governed files.
What is deliberately absent
- No performance claims: published only when the qualification program measures them.
- No security guarantees beyond the certified scope: the agent-native protocol layers get their own threat models and reviews as they land.
- No "trust us": where a claim can be verified mechanically, the verifier is part of the repository and the build.