Skip to content

Verification Utility

Verify Receipt Hash

Validate receipt integrity with hash checks, signature verification, and deterministic demo recompute.

Developer utility for independent, copy-paste verification workflows.

What does verification prove?

Every policy-governed execution produces a deterministic receipt. Verification confirms that a specific execution occurred under a declared policy, with an independently recomputable hash. Receipts are useful for bot operators, agent builders, and integrators who need inspectable, shareable proof of execution behavior.

What verification is useful for

  • Confirm a protected execution happened under a specific policy
  • Inspect execution receipts and recompute hashes independently
  • Share reproducible proof with teammates, auditors, or partners

Don't have a receipt yet? Run your first protected trade to generate one, or explore the builder resources.

Need the normative contract? See Receipt Specification v1.

What you're verifying

  • Receipt hash (SHA-256): deterministic fingerprint of the receipt payload.
  • Ed25519 signature: proof that the hash was signed by the configured TruCore receipt signing key.
  • Deterministic recompute (optional): available for supported demo receipt schemas only.

Verify signature

Verification Kit

Copy these values and commands to verify this receipt independently in your local environment.

receipt_hash

(paste receipt hash above)

Public key appears when signature support is configured.

Fetch signature to include signed proof in the kit.

Command, verify signature

Fetch signature first to generate a ready-to-run signature verification command.

Runs Ed25519 verification over the receipt hash bytes.

Script, verify signature

Fetch signature first to generate a verification script.

Save as verify-receipt-signature.mjs, then run: node verify-receipt-signature.mjs

Hash recompute command appears after you provide full receipt JSON and receive a supported version result.