A checksum bundled with its own download is circular. A receipt confirms execution only. Nullark gives each dependency an independent trust check.

Dependency map

Artifact root of trust

Trust starts with the expected pin in bundled runtime configuration, outside the fetched manifest, setup record, WASM, and zkey set. approvedBy and approvedAt are display metadata only. Cache identity includes that expected pin. A new pin forces fresh verification. See Authenticate proving artifacts for the byte caps and validation order.

Transaction trust path

Before treating a withdrawal as settled, the client checks:
  1. Recovered note and commitment
  2. Accepted root and local Merkle witness
  3. Current fee and intended public destination
  4. Nine positional public inputs
  5. Proof against the bound verifier relation
  6. Pool, selector, value, deadline, and submission route
  7. Receipt, pool event, and recorded nullifier
If one of these values changes, rebuild every dependent proof or transaction value. UI refresh speed leaves stale proofs stale.

If the frontend itself is compromised

Artifact authentication rejects malicious same-origin file replacement while the trusted frontend bundle and its bundled pin remain intact. Compromise of both frontend logic and pin moves trust to reproducible builds, reviewed release provenance, protected deployment credentials, origin security, and independent artifact verification. approvedBy, approvedAt, a green UI state, and a fast MegaETH receipt stay outside that trust root.