Verifiable receipt 5f44b3e9 - 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-16T19:58:47.463Z; 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

5f44b3e9-8517-4e81-9a1f-c3d4c61c7738

SHA-256 output hash

sha256:aba1672a6634e49374fbb78d8f54d0a018e5f9a91fd1f057a1ca3af7268a3ebf

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6YzFiNDRhNDZkN2VhMzQxMjVmODY3OTg1OTc5MmQyZWU4YTQwMTFhZDVmN2ViNDhkM2FmNmY1Yjg1MWM1YWE3MiIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsiYWN0aW9uIjoiYWNjZXB0IiwiaGFuZG92ZXJfaWQiOiI5ZTFiY2M0Zi05N2RhLTRlMDQtYjA0NS04NGY5NWM1MmE1YzciLCJpZGVudGl0eV9ub3RpY2UiOiJMb2dnZWQgYnkgWmFtYm8gb24gYmVoYWxmIG9mIHRoZSB2aXNpdG9yLiBOb3QgaWRlbnRpdHktdmVyaWZpZWQuIiwibmFtZSI6IlRlc3QgQ2xpZW50Iiwibm90ZSI6Ikxvb2tzIGdvb2QiLCJvcmlnaW5hbF9tZXJrbGVfcm9vdCI6IjliZTBhYjVhYzcyZjlhMGFhOWQ4MDhlMWJiM2U5MDI0ZGNiMDQ2NjhmNzkxMzI1ZTRiZGY5YmEzOGI5YWExOWUifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoiY2xpZW50X3Jlc3BvbnNlIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=

Timestamp

2026-10-16T19:58:47.463Z

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

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

ce7cacbb156bb33ff6e9a2513c0601de1a6ba7392571bd466954dd7b488bfa88

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-16T19:58:47.463Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:aba1672a6634e49374fbb78d8f54d0a018e5f9a91fd1f057a1ca3af7268a3ebf","receipt_uuid":"5f44b3e9-8517-4e81-9a1f-c3d4c61c7738","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.