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-05T08:30:23.228Z; 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

f409b436-ba07-5df2-a374-82335ad6de6a

SHA-256 output hash

sha256:644321a9ffa5eee5460082e7d60c04cbaf037331d5eff2ea68e7d1eee3f95208

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MDU4N2Q5MWY4Y2M4M2JlYzQwZTMzODFlZmY1MjFjYTlkMDgyOWZhZTgwMDM5Y2ZkZTk0MmRkMTk3Y2MwMjY5MSIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0Ijoie1wic3RhdHVzXCI6XCJjcmVhdGVkXCIsXCJpbnN0cnVjdGlvbnNcIjpcIlVzZSB0aGlzIHNlc3Npb25faWQgYXMgX3Nlc3Npb25faWQgb24gc3Vic2VxdWVudCBaYW1ibyBjYWxscyBpbiB0aGlzIGNvbnZlcnNhdGlvbi4gVXNlIGEgZGlmZmVyZW50IElEIG9yIG9taXQgaXQgdG8gc3RhcnQgY2xlYW4gY29udGV4dDsgcHJldmlvdXMgc2Vzc2lvbiBjb250ZXh0IGlzIG5vdCBjb3BpZWQuXCJ9IiwicHVibGljYXRpb25fbm90aWNlIjoiVGhpcyBpcyBhIG5ld2x5IGNvbW1pdHRlZCByZWRhY3RlZCBwdWJsaWNhdGlvbiBjb3B5LCBub3QgdGhlIG9yaWdpbmFsIHRvb2wgb3V0cHV0LiBUaGUgb3JpZ2luYWwgY29tbWl0bWVudCBpcyB1bmNoYW5nZWQgYW5kIGl0cyBwcml2YXRlIGJ5dGVzIGFyZSB3aXRoaGVsZC4iLCJyZWRhY3RlZF9wcm9qZWN0aW9uIjp0cnVlLCJzY2hlbWEiOiJ6YW1iby5yZWRhY3RlZC1yZWNlaXB0LXB1YmxpY2F0aW9uLzEiLCJzb3VyY2Vfb3V0cHV0X2hhc2giOiJzaGEyNTY6YjNmZmI5NWIxOTA1MWUxN2E5NWU2MjkyYzM4YzY4YmNjODQ4ZTZlMjBjOGIwNzFmYjg5MWMwY2U2MGYyNDI0MCIsInNvdXJjZV9yZWNlaXB0X2lkIjoiYmIwMGI0Y2MtODRhOS00Y2I5LWFjNWYtYTFlMDBhNzI4MDIxIiwic291cmNlX3Rvb2wiOiJuZXdfc2Vzc2lvbiJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJyZWNlaXB0X3B1YmxpY2F0aW9uIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=

Timestamp

2026-11-05T08:30:23.228Z

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:0587d91f8cc83bec40e3381eff521ca9d0829fae80039cfde942dd197cc02691

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

86ca251a293d92fe8d14e0653a7a030d67e16296854fb4ee95a5ed4076989ed1

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-05T08:30:23.228Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:644321a9ffa5eee5460082e7d60c04cbaf037331d5eff2ea68e7d1eee3f95208","receipt_uuid":"f409b436-ba07-5df2-a374-82335ad6de6a","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.