Trust Center

Verify our evidence ledger on your laptop

KURAL anchors every evidence record with a per-record Merkle root plus a chain hash linking to the previous record. The chain head gets RFC 3161 dual-anchored (DigiCert + FreeTSA) every 24 hours and witnessed by Sigstore Rekor. You don't have to trust us — you can verify any one of those claims with a 2 MB Go binary, offline, on the laptop you're reading this on.

60-second verify

# 1. Get the verifier (Linux/macOS — Windows .exe also available below)
curl -sL https://kural.tech/sample-pack/downloads/kural-verify-1.0.0-linux-amd64 -o kural-verify
chmod +x kural-verify

# 2. Get a real specimen pack + unzip
curl -sL https://kural.tech/sample-pack/downloads/specimen.zip -o specimen.zip
unzip specimen.zip && cd specimen

# 3. Verify — no network, no api.kural.tech call
./kural-verify \
  --proof   proof.json \
  --value-file value.json \
  --expected-root $(cat chain-context.json | python3 -c "import sys,json;print(json.load(sys.stdin)['merkle_root'])")

# Expected: CHAIN HEAD MATCH

Downloads

All releases are reproducibly built. Run sha256sum -c SHA256SUMS to verify the binary you downloaded matches the one we built. Source on GitHub: cli/kural-verify.

OSArchitectureDownload
Linuxamd64kural-verify-1.0.0-linux-amd64
Linuxarm64kural-verify-1.0.0-linux-arm64
macOSIntel (amd64)kural-verify-1.0.0-darwin-amd64
macOSApple Silicon (arm64)kural-verify-1.0.0-darwin-arm64
Windowsamd64kural-verify-1.0.0-windows-amd64.exe
Specimen pack (real evidence + proof + chain context)specimen.zip
Integrity manifestSHA256SUMS

What the verifier proves

  • Inclusion — the labelled field was part of the evidence record at the time of anchoring, and the value you have is byte-identical to what we anchored.
  • Tamper-evidence — if any field changes after anchoring, the Merkle root changes; if the chain order is broken, every subsequent chain hash changes.
  • No KURAL dependency — the verifier never talks to api.kural.tech, never reads our database, never relies on our runtime being honest. Pull the WiFi plug and run it.

Who you actually trust

For an evidence proof to lie, FIVE independent parties would have to be colluding:

  • SHA-256 — the NIST/FIPS-approved cryptographic hash function. If it's broken, the world's TLS, Bitcoin, git, and basically everything else also is.
  • The JSON spec — canonical-leaf encoding follows JSON.stringify rules; the verifier reproduces those byte-for-byte.
  • FreeTSA.org — EU-based RFC 3161 trusted-timestamp authority. Independent of KURAL, independent of any operator.
  • DigiCert — US-based RFC 3161 TSA. Independent of FreeTSA. Dual-anchor by design.
  • Sigstore Rekor (Phase 2) — append-only public transparency log operated by the Linux Foundation. Daily chain head logged with a public UUID you can pull via rekor-cli get --uuid=<id>.

KURAL is one of those five. If we tampered with a record, we'd need to also persuade DigiCert and FreeTSA to backdate a cryptographic timestamp, and convince the Linux Foundation to rewrite Rekor history. Good luck.

Related

  • /trust/posture — live platform heartbeat (worker tick, evidence-ledger anchoring, RFC 3161 counts, regulator-source scans)
  • /trust/connectors — per-vendor readiness matrix (which connectors are live vs sandbox vs fixture)
  • /trust/security — architecture + encryption posture + hosting
  • /legal/subprocessors — DPA Schedule 2 with locations and safeguards

If you find a way to make this verifier print CHAIN HEAD MATCH for a value that wasn't actually anchored, email security@kural.tech — there's a 5-figure bounty waiting.