Skip to content
TruCore logoTruCore
Protected Trade Receipt

This trade was protected by TruCore

AI transactions evaluated, enforced, and recorded with verifiable receipts.

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 happened here

  • Transaction evaluated before execution
  • Risk rules enforced in real time
  • Outcome recorded as tamper-evident receipt

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

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

7ef382d4-b046-400d-8e5c-9bc2051738c7

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.

Share this receipt

Anyone can independently verify this transaction

Open OG PreviewTwitterTelegram

Proof links

verify url

https://www.trucore.xyz/verify?hash=7ef382d4-b046-400d-8e5c-9bc2051738c7&from=share

og preview url

https://www.trucore.xyz/api/og/receipt?hash=7ef382d4-b046-400d-8e5c-9bc2051738c7

Use these links to share independently verifiable proof.

export proof bundle
API ↗
{
  "version": 1,
  "type": "trucore_proof_packet",
  "status": "success",
  "proof": {
    "hash": "7ef382d4-b046-400d-8e5c-9bc2051738c7",
    "decision": "UNKNOWN",
    "verified": false
  },
  "links": {
    "verify_url": "https://www.trucore.xyz/verify?hash=7ef382d4-b046-400d-8e5c-9bc2051738c7&from=share",
    "og_preview_url": "https://www.trucore.xyz/api/og/receipt?hash=7ef382d4-b046-400d-8e5c-9bc2051738c7"
  },
  "meta": {
    "exported_at": "2026-06-14T23:10:38.573Z",
    "source": "trucore-site"
  }
}
share / distribute

Building an integration? View developer docs

Run your first protected trade

Get the same protection for your autonomous trading agents and bot operations.

Get started freeSee how it works

Used by autonomous trading agents and developers

Explore further

See how TruCore works and explore deeper integration options.

First protected tradeProtect an intent, get a receipt, verify it. Start here if you haven't yet.Your portalView your API keys, usage, and verify receipts from your own activity.Receipt specificationNormative contract, hash rules, version policy.For bot buildersIntegration paths, resources, and early access.