Verifiable receipt 18462df3 - receipt_publication 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-18T22:05:38.316Z; 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

18462df3-bdaf-5f19-aaa5-4a4c8983a0dc

SHA-256 output hash

sha256:242cae59405f52639d9e014d25b5d1c416a02129e0b5bc52ebfda4c63021fcd5

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6ZWMxMDRmZDY3NWIwNzlhOTljNzFiYTY4ODhiYjY2MjBhNTc3YWQ2OWVmNzg1NWY0OWUxN2Y0ZGNmNzFlMDk5NCIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0Ijoie1wic3RhdHVzXCI6XCJodW1hbl9jaGVja291dF9saW5rX3JlYWR5XCIsXCJjaGFyZ2VkXCI6ZmFsc2UsXCJwcmljZV91c2RcIjpcIjAuOTlcIixcImR1cmF0aW9uX2hvdXJzXCI6MjQsXCJjaGVja291dF91cmxcIjpcImh0dHBzOi8vemFtYm8uZGV2L2RheS1wYXNzLz9jaGF0X2NoZWNrb3V0PVtwcml2YXRlXSZzb3VyY2U9Y2hhdFwiLFwiZXhwaXJlc19hdFwiOlwiMjAyNi0xMC0xNVQyMjoyMTozMy4zNjNaXCIsXCJzZXNzaW9uX2JvdW5kXCI6dHJ1ZSxcIm1lc3NhZ2VcIjpcIlBheSAkMC45OSBieSBjYXJkIG9yIFBheVBhbC4gT3BlbiB0aGlzIGxpbmsgYW5kIGFwcHJvdmUgcGF5bWVudC4gTm90aGluZyBoYXMgYmVlbiBjaGFyZ2VkLlwiLFwibmV4dFwiOlwiSGF2ZSB0aGUgaHVtYW4gb3BlbiBjaGVja291dF91cmwsIHRoZW4gcG9sbCBkYXlfcGFzc19zdGF0dXMgd2l0aCBzdGF0dXNfdG9rZW4gdW50aWwgdGhpcyB3b3JrZmxvdyBhcHBlYXJzIGluIHNlYWxzW10uXCJ9IiwicHVibGljYXRpb25fbm90aWNlIjoiVGhpcyBpcyBhIG5ld2x5IGNvbW1pdHRlZCByZWRhY3RlZCBwdWJsaWNhdGlvbiBjb3B5LCBub3QgdGhlIG9yaWdpbmFsIHRvb2wgb3V0cHV0LiBUaGUgb3JpZ2luYWwgY29tbWl0bWVudCBpcyB1bmNoYW5nZWQgYW5kIGl0cyBwcml2YXRlIGJ5dGVzIGFyZSB3aXRoaGVsZC4iLCJyZWRhY3RlZF9wcm9qZWN0aW9uIjp0cnVlLCJzY2hlbWEiOiJ6YW1iby5yZWRhY3RlZC1yZWNlaXB0LXB1YmxpY2F0aW9uLzEiLCJzb3VyY2Vfb3V0cHV0X2hhc2giOiJzaGEyNTY6YzJhOWE3NDgwYTBhZDc3ZDc2NTQ2OTQ4Mjk4YzkyZDI4MTc4ZDQwMTNmODgzNjRhYTk2ZTlmNzA1N2FjYjFiMyIsInNvdXJjZV9yZWNlaXB0X2lkIjoiMWQ5NzRkNzUtYzU4Yy00MjUzLTk2N2UtMjUzYzE5ODQwYmRmIiwic291cmNlX3Rvb2wiOiJkYXlfcGFzc19jaGVja291dF9saW5rIn0sInJlY2VpcHRfc2NoZW1hX3ZlcnNpb24iOiIwLjQiLCJzaWRlX2VmZmVjdHMiOnsiZGVjbGFyYXRpb25faGFzaCI6InNoYTI1Njo0NWFhZDM4ZjNhYTk4MmI5YWFmZTkyZWNiNDE2ZWJlOTg3OTFlZGRiYWY4YWI2ZGYwYmQwODYwNWI3YzFiZmVlIiwiZGVjbGFyZWQiOlsibm9uZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6InJlY2VpcHRfcHVibGljYXRpb24iLCJzY29wZSI6InB1YmxpYyIsInZlcnNpb24iOiI0LjAuMCJ9fQ==

Timestamp

2026-10-18T22:05:38.316Z

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

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

d45d5294f5c9516af5c1c8b1088e3c49c092c83ff170fe1d755b22027ee01d21

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-18T22:05:38.316Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:242cae59405f52639d9e014d25b5d1c416a02129e0b5bc52ebfda4c63021fcd5","receipt_uuid":"18462df3-bdaf-5f19-aaa5-4a4c8983a0dc","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.