LTC price, saved and checkable

Provenance for every timeline entry

• EXECUTED BY ZAMBOZambo ran the tool call itself.
• OBSERVED VIA GATEWAYA Zambo gateway observed request and response bytes from the named external executor. Zambo did not run that external action.
• LOGGED BY AGENTAn agent or local hook reported the action. Zambo attests that the record is unchanged since logging, not that the action happened as described.

Private agent reasoning, built-in client actions, and direct calls to unrelated MCP servers are not included unless an agent or gateway reports them.

What is an execution receipt?

An execution receipt is a public record of a reported AI agent tool call. Its byte commitment and provenance claim can be checked independently; neither alone authenticates the issuer. Read the canonical definition of an AI agent execution receipt.

What is this?

Zambo's receipt store reports a tool call and records its result. The SHA-256 commitment covers the exact canonical bytes. The provenance label is bound to v0.4 receipt bytes when that check passes, but no pinned signature or trusted issuer key is checked. An anchor can timestamp a fingerprint; it does not authenticate the issuer.

Verification checks

• SHA-256 commitment: Checked independently against the exact decoded bytes
• Provenance binding: FAIL; The receipt schema version is missing or unsupported; provenance binding was not accepted.
• Metadata binding: LEGACY; legacy receipt, metadata is not cryptographically bound
• Issuer authentication: NOT CHECKED; no pinned signing key or trusted issuer was supplied
• Signature: NOT CHECKED; no Ed25519 signature or pinned key is supplied
• Chain: NOT CHECKED; no append-only chain proof is validated
• Stored timestamp: 2026-09-16T15:26:51.536Z; external immutability is not checked

Committed provenance claim

EXECUTED BY ZAMBO

The receipt schema version is missing or unsupported; provenance binding was not accepted.

Receipt ID

b7a46403-fba0-4e58-b856-c858a1c73d1b

SHA-256 output hash

sha256:df0a6df8d6cfecf637ac5cd0c87ac8db6c00cbaeff8adae7224c72292d7f54d8

Canonical bytes

eyJ0ZXh0IjoiTFRDIMK3ICQ1MC4zNCBVU0RcbuKWvCAzLjA2JSAoMjRoKSDCtyBNYXJrZXQgY2FwOiAkMy45MUJcblxuTGl2ZSBwcmljZSB2aWEgQ29pbkdlY2tvIMK3IFdlZCwgMTYgU2VwIDIwMjYgMTU6MjY6NTEgR01UIn0=

Timestamp

2026-09-16T15:26:51.536Z

Bound call context

Receipt schema

0.2

v0.2 receipt; call-context metadata was not recorded.

Bound upstream evidence

Status

captured

Evidence SHA-256

sha256:0f1e885fa596c072bca5cacdb4529c6b51f6e4372d240bc4eb655a3c863267ea

Byte length

98

Fetch exact evidence bytes

Neutral Nostr anchor

Event ID

ef1d87ab3ef59f30e31a06c1175ec13fee34b0e7f44118f5553d8c5e702fbc45

Anchor status

partial

Public key

e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

Relay hints: wss://relay.damus.io · wss://nos.lol · wss://relay.primal.net

Anchor status "partial": Published to some configured relay targets; publication was not confirmed by every configured relay.

Check this hash yourself

Receipt commitment: legacy_receipt. This checks the saved bytes, not whether the answer was correct. Recompute the SHA-256 commitment in your browser. Open the API v2 JSON response to inspect the machine-readable checks. See the Nostr anchor event on a public viewer. The fingerprint is timestamped outside Zambo too.