Verifiable receipt 116f26e2 - client_response result | Zambo

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 this receipt?

This is a verifiable receipt for a journal entry. It confirms receipt, redaction, timestamping, and chaining. It does not attest to execution.

What is this?

Zambo's receipt store reports a journal entry from an agent or local hook. The SHA-256 commitment covers the receipt bytes. The provenance label is only a claim, not proof of issuer identity or that the reported action happened.

Verification checks

• SHA-256 commitment: Checked independently against the exact decoded bytes
• Provenance binding: PASS; The metadata claim is consistent with the verified receipt bytes; issuer is not authenticated.
• Metadata binding: PASS; metadata_hash matches the canonical metadata block.
• 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-10-20T17:21:54.939Z; external immutability is not checked

Committed provenance claim

LOGGED BY AGENT

The metadata claim is consistent with the verified receipt bytes; issuer is not authenticated.

Receipt ID

116f26e2-9f81-41f4-9195-78d687c3814f

SHA-256 output hash

sha256:4c563d58057a3ba1d9d09ffd114b4cc7319b5a32dc544270db2502bb9efe88a8

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NDE4ZDkwYzZjZTgwMjEzYjA5Yjc3Y2EwOWM4ODZjZjEzMjllYjNhODk0MjM3MGRjODNjZTU2MGU1ZWIzZTE1ZSIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsiYWN0aW9uIjoiZmxhZyIsImNhdGVnb3J5IjoiaW5jb21wbGV0ZSIsImRlY2lkZWRfYnkiOiJ0aGUgaG9sZGVyIG9mIHRoZSBjbGllbnQgbGluayIsImhhbmRvdmVyX2lkIjoiMWNjNzg4MmQtNzAyNy00ZmUwLWFmYjgtOWQ5MDE1MGNkYzhlIiwiaWRlbnRpdHlfbm90aWNlIjoiQ2xpZW50LWxpbmsgaG9sZGVyIHJlc3BvbnNlLiBSZXZpZXdlciBkZXRhaWxzIGFyZSBzZWxmLXJlcG9ydGVkLCBub3QgaWRlbnRpdHktdmVyaWZpZWQuIiwia2luZCI6ImNsaWVudF9kZWNpc2lvbiIsIm5vdGUiOiJRQSB2NSBmbGFnIHRlc3QsIHBsZWFzZSBpZ25vcmUiLCJvcmlnaW5hbF9tZXJrbGVfcm9vdCI6ImJiZDU5MjkyNzZhMWI0ZjM1MWUyYjI1MThiMWI3ZDM4NmFlNWVjZTNmMTliOWE2ZWUwZjBhZDUwZDExNjU0OGYifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoiY2xpZW50X3Jlc3BvbnNlIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=

Timestamp

2026-10-20T17:21:54.939Z

Bound call context

Receipt schema

0.4

Tool name

client_response

Tool version

4.0.0

Permission scope

public

Caller type

session

Caller ID

sha256:418d90c6ce80213b09b77ca09c886cf1329eb3a8942370dc83ce560e5eb3e15e

Declared side effects

none

Side-effects schema

zambo-side-effects/1

Declaration hash

sha256:45aad38f3aa982b9aafe92ecb416ebe98791eddbaf8ab6df0bd08605b7c1bfee

This records what the server-side tool contract declared at call time. It does not independently verify that a downstream side effect happened.

Bound upstream evidence

Status

no_upstream_bytes_captured

Evidence SHA-256

unavailable

Byte length

unavailable

Neutral Nostr anchor

Event ID

03f79333bafd71776c4c0670978a4fb73b946e8fd8a53fcd6b3fcb6a2b3497cc

Anchor status

partial

Public key

e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

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

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-10-20T17:21:54.939Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:4c563d58057a3ba1d9d09ffd114b4cc7319b5a32dc544270db2502bb9efe88a8","receipt_uuid":"116f26e2-9f81-41f4-9195-78d687c3814f","schema_version":"zambo-receipt-anchor/1"}

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

Check this hash yourself

Receipt commitment: commitment matched; issuer, signature and chain not checked. 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.