FAQ & Navigation

What is NovaProof? A verification surface proving execution boundaries mathematically using cryptographic receipts.

Read Time: 2 min.

Method: Zero-access verification audits.


Jump To Section

Licensing Inquiry
Verification - Reference - Audit

NovaProof

Trust should be verified before collaboration begins.

The Discovery

We frequently saw enterprises get bogged down in high-friction legal agreements (NDAs) and tedious compliance questionnaires just to evaluate a partner's software or data pipeline. Even after months of negotiation, the final security posture was still based on a fragile assumption: trusting a vendor's self-signed claims.

This led to a simple realization: trust should be empirical, not legal. An organization should be able to run a test transaction inside a partner's target environment and receive a cryptographic proof that the runtime boundaries are actively enforced—all without taking possession of or exposing any intellectual property.

By building a public verification surface, we created NovaProof. It shifts security verification from a paper audit to a live mathematical demonstration.

The Inversion

Aspect Traditional Audits NovaProof
Method Compliance questionnaires & SOC 2 PDFs Execution reference runs
Frequency Once a year (static) Continuous / at runtime (dynamic)
Certainty Subjective self-claims Cryptographically verifiable receipts

Verification Architecture

STEP 01
Verification ERI
PROOF SURFACE
Reference Running
STEP 03
Production Boundary

The New Capability

Because of this, you can now empirically verify the security posture of any third-party software, cloud endpoint, or AI model prior to sending a single byte of sensitive payload data.

Technical Specification

NovaProof ≡ Reference Surface ≡ Empirical Verification

Critical Aspects

Dimension Description Verification Method
Reference Surface Public-facing sandboxed enclave used to demonstrate runtime reachability bounds. Hardware-attested Proof Runs.
ERI Verification Running standard Execution Reference Implementations (ERIs) to assert rule outcomes. Assertion comparison of result receipts.
Receipt Auditing Verifying the mathematical integrity of state transition chains. Chain validation signatures.

Validation Metrics

  • Verification Overhead: < 50ms
  • Proof Completeness: 100% Cryptographic
  • Reference Equivalence: 100% match

Example Applications

  • Vendor Scoping: Assessing third-party databases before connecting customer pipelines.
  • API Gateways: Dynamically checking receipt signatures on incoming connections.
  • Platform Audits: Continually asserting enclave environment integrity via public keys.

Reference Implementation

// NovaProof Receipt Signature Verification
function verifyProofReceipt(receipt, referencePubKey) {
  const dataToVerify = receipt.txData + receipt.outcome;
  const isSignatureValid = verifyAsymmetricSignature(
    dataToVerify,
    receipt.signature,
    referencePubKey
  );

  return {
    verified: isSignatureValid,
    timestamp: receipt.timestamp,
    outcome: receipt.outcome // 'ALLOW' or 'DENY'
  };
}

Measurement Protocol

  1. Trigger a reference Proof Run transaction using a standard ERI.
  2. Intercept the resulting transaction receipt at execution.
  3. Extract the cryptographic signatures and environmental attestation reports.
  4. Validate signatures against the public NovaProof reference key.
  5. Verify the outcome matches the expected boundary policy.

Composition

As a Standalone Primitive: NovaProof offers an API endpoint for verifying receipt authenticity and attestation reports from remote enclaves.

As a Composed Architecture: NovaProof validates the receipts generated by Cyber-Safety layers, verifies the IDNA context signatures, and confirms the integrity of NovaVault-X objects.

Proof Surface

Verify the proof verification algorithms and public key lists.

GitHub Repository Proof Verifier