An export is consistent but not authentic

What you're seeing

You verify an export, on provantix.tech/verify, with the command-line verifier, or under Settings → Verify an export, and the result is not a clean pass:

  • The page says "Consistent, but not shown to come from Provantix" in amber, with a line saying why.
  • The command-line verifier exits with code 3 and prints "authenticity is NOT established".
  • Every hash, chain link and root check passes, but the check issued by Provantix does not.

What it means

Verification answers two separate questions. Is the export consistent? The hashes, chain links and daily roots recompute from the files. Did Provantix issue it? Provantix signs each export's manifest with a key whose public half it publishes, and the signature is checked against that key.

Both are needed because the first can be faked: everything it checks lives inside the bundle, so someone who edits a record can recompute every hash and root and the edited bundle is still consistent. Only the signature, which they cannot make, shows the export is the one Provantix produced.

The reason is one of five states:

State Why you see it What to do
unsigned The export was made before signing existed, or manifest.sig.json is missing from the bundle. Make a fresh export. If someone removed the file from a recent export, treat the bundle as untrusted.
unverified The verifier had no published keys to check against. In a browser this is the keys file failing to load; on the command line it is a missing --keys. Reload and retry, or download the keys and pass them: see below.
unknown key The signature names a key Provantix does not publish. Treat as untrusted. A bundle signed with someone else's key is not a Provantix export.
invalid signature The manifest differs from what was signed, or the signature is wrong. The export was changed after it was issued. Do not rely on it; make a new one and find out what changed.
malformed manifest.sig.json is not a valid signature file. Treat as untrusted and re-export.

What to do

  1. Read the state in the result. The amber line names it.

  2. If it says unsigned and the export is old, this is expected. Make a new export from the app; new exports are signed.

  3. To check on the command line, download the published keys and pass them in:

    curl -s https://app.provantix.tech/.well-known/provantix-export-keys.json -o provantix-export-keys.json
    node verifier/verify-export.mjs <export-folder> --keys provantix-export-keys.json   # from a clone of github.com/provantix-tech/agent-sdk
    

    Exit 0 means consistent and authentic. Exit 1 means it failed the integrity checks. Exit 3 means consistent but authenticity is not established. --integrity-only exits 0 on integrity alone; use it only when you understand it cannot show who issued the export.

  4. If it says invalid signature, do not hand the bundle to anyone as evidence. Make a new export, and look at the decision log for who exported and when.

What good looks like

A green result reading "Verified. The export is consistent and was issued by Provantix." and, on the command line, exit 0 with the line signed by Provantix key pek_….

What a pass does not prove

An authentic export shows Provantix issued exactly these records. It does not by itself show that your emitter said them. That is the separate emitter proof, present where the emitter seals its batches, and its result says whose key it rests on. See How verification works, the section What verification proves, and what it doesn't.