Verifiable receipt 031eea78 - journal_log 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-20T21:20:57.497Z; 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

031eea78-b0c7-4eb8-83dc-3a2cc4f41c33

SHA-256 output hash

sha256:13b8771ac09784e37fa0ed873684961ecf84e56479cbd41d3909912b882a5542

Canonical bytes

eyJjYWxsZXIiOnsiYmFzaXMiOiJpcF91YV8zMGQiLCJpZCI6InNoYTI1Njo3ZDVkZWQzZTA4Y2JjOTRhNWRiYmYwYmVmMDdkMGIxMGMzYjcwY2NlYzM3MWE3ZTUxMmZmNGY2YTYzM2RhMTc1Iiwicm90YXRlc19hdCI6IjIwMjYtMTEtMDNUMDA6MDA6MDAuMDAwWiIsInR5cGUiOiJhbm9ueW1vdXMifSwiaXNzdWVyX2NsYWltcyI6eyJwcm92ZW5hbmNlX2NsYXNzIjoiTE9HR0VEIEJZIEFHRU5UIn0sIm91dHB1dCI6eyJhdHRlc3RzIjoiWmFtYm8gYXR0ZXN0cyB0aGF0IHRoaXMgcmVjb3JkIHdhcyByZWNlaXZlZCwgcmVkYWN0ZWQsIHRpbWVzdGFtcGVkLCBhbmQgY2hhaW5lZC4iLCJkb2VzX25vdF9hdHRlc3QiOiJaYW1ibyBkaWQgbm90IHJ1biBvciBvYnNlcnZlIHRoZSByZXBvcnRlZCBhY3Rpb24uIiwiZW50cnkiOnsiY29tcGxldGVkX2F0IjoiMjAyNi0xMC0yMFQyMToyMDo1Ny40MDZaIiwiZGVsZXRlZCI6ZmFsc2UsImR1cmF0aW9uX21zIjowLCJlbnRyeV9oYXNoIjoic2hhMjU2OjcwYWFmNjVkMDgzNWJmNzEwNzg0OTQ1ZWRkZjE4OTQ0YWExYjY3ZTBjMjExZGVkZjg1Y2I2ODhmNzZjMjk4MzAiLCJlbnRyeV9pZCI6IjViZWFmMWMyLTBjMTAtNGI3ZC05M2FhLWUzMGU5NTk2NTlkMiIsImV4ZWN1dG9yX2lkZW50aXR5IjoicmFtYm8iLCJleHRlcm5hbF9leGVjdXRvciI6bnVsbCwibWV0YWRhdGEiOnt9LCJwcmV2X2hhc2giOiJzaGEyNTY6YWMzZTNhN2E4OGQwMGFkZDNjYTEzZWQzN2Y0YmI0M2E4OTczN2U3ZTFiNzQ5NjgzNjE4ODVjMzVjYjNmMTg0MyIsInByb3ZlbmFuY2VfY2xhc3MiOiJMT0dHRUQgQlkgQUdFTlQiLCJyZWRhY3RlZF9pbnB1dHNfaGFzaCI6bnVsbCwic2VxdWVuY2UiOjIsInN0YXJ0ZWRfYXQiOiIyMDI2LTEwLTIwVDIxOjIwOjU3LjQwNloiLCJ0b29sX25hbWUiOiJqb3VybmFsX2xvZyJ9LCJwcm92ZW5hbmNlX2NsYXNzIjoiTE9HR0VEIEJZIEFHRU5UIiwic3RhdHVzIjoibG9nZ2VkIiwidmVyaWZ5X3VybCI6Imh0dHBzOi8vemFtYm8uZGV2L2FwaS9qb3VybmFsL1twcml2YXRlXS92ZXJpZnkifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OmRmYjQ0MTJhYTQyOWQzYWM2MzdhMDU2NjhjNDM1YmNjOTBhMjUxMzYzZmNkZDQ5ZjdiODVhZTRhYjU1YjViYzkiLCJkZWNsYXJlZCI6WyJzdGF0ZV93cml0ZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6ImpvdXJuYWxfbG9nIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=

Timestamp

2026-10-20T21:20:57.497Z

Bound call context

Receipt schema

0.4

Tool name

journal_log

Tool version

4.0.0

Permission scope

public

Caller type

anonymous

Caller ID

sha256:7d5ded3e08cbc94a5dbbf0bef07d0b10c3b70ccec371a7e512ff4f6a633da175

Caller basis

ip_ua_30d

Caller rotates at

2026-11-03T00:00:00.000Z

Declared side effects

state_write

Side-effects schema

zambo-side-effects/1

Declaration hash

sha256:dfb4412aa429d3ac637a05668c435bcc90a251363fcdd49f7b85ae4ab55b5bc9

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

76f07e204bed070215cc3606bf6496c0d8a2d76758bcf73e4bcd5974f359ea14

Anchor status

published

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-20T21:20:57.497Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:13b8771ac09784e37fa0ed873684961ecf84e56479cbd41d3909912b882a5542","receipt_uuid":"031eea78-b0c7-4eb8-83dc-3a2cc4f41c33","schema_version":"zambo-receipt-anchor/1"}

Anchor status "published": Published to all configured relay targets.

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.