Verifiable receipt d6fa16c5 - 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-17T13:00:41.673Z; 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

d6fa16c5-a21d-4de6-8411-27ac17afd98d

SHA-256 output hash

sha256:da8e0e8131e55849f457a6f733be60bfe8d5773069b89d9ede69ed435e6f1014

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6YWViYTk2YjQzYjA0NzVlMTk4MDJkZWI4MGJjYzU4OTRiNjQ4Y2E3MDRhMzBlZmM2YWMzMGY3OGNlNTMwMWI5NSIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsiYWN0aW9uIjoiYWNjZXB0IiwiZGVjaWRlZF9ieSI6IkFjbWUgUUEgYWdlbnQiLCJoYW5kb3Zlcl9pZCI6ImQ3NWI0ZWZlLWFiN2YtNGIwZS04MWVlLTYyMjBmODZlMGJmMSIsImlkZW50aXR5X25vdGljZSI6IkNsaWVudC1saW5rIGhvbGRlciByZXNwb25zZS4gUmV2aWV3ZXIgZGV0YWlscyBhcmUgc2VsZi1yZXBvcnRlZCwgbm90IGlkZW50aXR5LXZlcmlmaWVkLiIsImtpbmQiOiJjbGllbnRfZGVjaXNpb24iLCJvcmlnaW5hbF9tZXJrbGVfcm9vdCI6ImU0Mjk4Y2NiYTNkZWFiNGJjYmRjYjIzZDBiZDQxM2EwYmVhZDFkZjM1NDk2ZTg1YjEzNmE2N2NiMjlhMDc3YjgifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoiY2xpZW50X3Jlc3BvbnNlIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=

Timestamp

2026-10-17T13:00:41.673Z

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:aeba96b43b0475e19802deb80bcc5894b648ca704a30efc6ac30f78ce5301b95

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

374ef7d40dc1f53ee73acd081caec059bf06506f586578bef7240ed6386f076f

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-17T13:00:41.673Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:da8e0e8131e55849f457a6f733be60bfe8d5773069b89d9ede69ed435e6f1014","receipt_uuid":"d6fa16c5-a21d-4de6-8411-27ac17afd98d","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

API v2 status: verified. This status summarizes the v2 commitment and provenance checks; it does not prove 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.