Receipt publication · 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 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-11-07T15:57:03.138Z; 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

c39c9250-f4a0-5e3c-a81f-09330857c4e2

SHA-256 output hash

sha256:bdd7cbe5e6b923ada83917cfe71d3bd2faf7339e7f1cc241060d2c84a2d84c9f

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NGU5Mzk0OGE3NmJjNDM1NDFiNWYwYzE0ODc5MmI3ZjVlMjY5NTJlMDFmMWViYzg4YTZlNmI0MjNmZDZiMjMwZiIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0Ijoie1wic3RhdHVzXCI6XCJlbXB0eVwiLFwidHJhaWxfc3RhdHVzXCI6XCJlbXB0eVwiLFwib2JzZXJ2ZWRfc3RlcHNcIjpbXSxcInN0b3JlZF9mYWN0c1wiOltdLFwiaW5zdHJ1Y3Rpb25cIjpcIlRoaXMgaXMgdGhlIG9ic2VydmVkIHRyYWlsIHN0YXRlLiBDb21wYXJlIGl0IHdpdGggdGhlIHJlcXVlc3RlZCBvdXRjb21lOyBhIHN1Y2Nlc3NmdWwgdG9vbCBjYWxsIGlzIG9uZSBjb21wbGV0ZWQgc3RlcCwgbm90IHByb29mIHRoYXQgdGhlIHdob2xlIHRhc2sgaXMgY29tcGxldGUuXCJ9IiwicHVibGljYXRpb25fbm90aWNlIjoiVGhpcyBpcyBhIG5ld2x5IGNvbW1pdHRlZCByZWRhY3RlZCBwdWJsaWNhdGlvbiBjb3B5LCBub3QgdGhlIG9yaWdpbmFsIHRvb2wgb3V0cHV0LiBUaGUgb3JpZ2luYWwgY29tbWl0bWVudCBpcyB1bmNoYW5nZWQgYW5kIGl0cyBwcml2YXRlIGJ5dGVzIGFyZSB3aXRoaGVsZC4iLCJyZWRhY3RlZF9wcm9qZWN0aW9uIjp0cnVlLCJzY2hlbWEiOiJ6YW1iby5yZWRhY3RlZC1yZWNlaXB0LXB1YmxpY2F0aW9uLzEiLCJzb3VyY2Vfb3V0cHV0X2hhc2giOiJzaGEyNTY6ZTZhMTJmMjJjZGQzZjA4Y2U0MTMzYTliZDc3YjEwZDJlNzhmYTQwYWI5ZjBkZTYzMDYzZDNiYzllYmRiZGJjNCIsInNvdXJjZV9yZWNlaXB0X2lkIjoiNzNhZTEzMTQtMDYxOC00Y2FiLTllZmMtZmJmZmU4NzAwMTlhIiwic291cmNlX3Rvb2wiOiJ6YW1ib191bml2ZXJzYWwifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoicmVjZWlwdF9wdWJsaWNhdGlvbiIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19

Timestamp

2026-11-07T15:57:03.138Z

Bound call context

Receipt schema

0.4

Tool name

receipt_publication

Tool version

4.0.0

Permission scope

public

Caller type

session

Caller ID

sha256:4e93948a76bc43541b5f0c148792b7f5e26952e01f1ebc88a6e6b423fd6b230f

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

empty

Evidence SHA-256

unavailable

Byte length

unavailable

Neutral Nostr anchor

Event ID

4af9da2ea069864bdb557f3d1a5488c6633221f2d02b39871522a95190ffa358

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-11-07T15:57:03.138Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:bdd7cbe5e6b923ada83917cfe71d3bd2faf7339e7f1cc241060d2c84a2d84c9f","receipt_uuid":"c39c9250-f4a0-5e3c-a81f-09330857c4e2","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.