Verifiable receipt d21c2850 - journal_log result | Zambo
Verifiable receipt for a journal_log call on Zambo: {"status":"logged","provenance_class":"LOGGED BY AGENT","entry":{"job_id":"test","entry_id":"27c00617-6dcb-4
Observed result
{"status":"logged","provenance_class":"LOGGED BY AGENT","entry":{"job_id":"test","entry_id":"27c00617-6dcb-458d-94ae-30acb429fdaa","sequence":1,"provenance_class":"LOGGED BY AGENT","tool_name":"probe","redacted_inputs_hash":null,"started_at":"2026-10-10T00:51:25.458Z","completed_at":"2026-10-10T00:51:25.458Z","duration_ms":0,"executor_identity":"zambo-receipt-bot","external_executor":null,"metadata":{},"prev_hash":null,"entry_hash":"sha256:50258c77e4ffd5d6847a1fb693ebfa4095a00821e89ba882b3f77e1c1be6e0b6","deleted":false},"attests":"Zambo attests that this record was received, redacted, timestamped, and chained.","does_not_attest":"Zambo did not run or observe the reported action.","verify_url":"https://zambo.dev/api/journal/test/verify"}
Check this receipt
This record shows the result and timestamp stored for the call. Recompute the SHA-256 commitment from the saved bytes in your browser; signatures and chain proofs are not checked.
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.
Whole job timeline
This append-only chain shows the entries available to Zambo. The labels describe what Zambo did and what it did not do.
-
LOGGED BY AGENT probe
An agent reported this action. Zambo did not run or observe it.
- Sequence
- 1
- Executor
- zambo-receipt-bot
- Completed
- Input hash
not supplied- Entry hash
sha256:50258c77e4ffd5d6847a1fb693ebfa4095a00821e89ba882b3f77e1c1be6e0b6
Chain status: valid. The chain has not been checked.
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.
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.
Keep the work moving
This receipt records a completed tool call. When the free allowance is not enough, choose the access path that fits the job.
Or re-run this exact call, using the same tool and arguments.
Share this receipt
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.
- 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-10T00:51:25.545Z; external immutability is not checked
Want a verifiable receipt for every job your bots do?
Committed provenance claim
LOGGED BY AGENT
The metadata claim is consistent with the verified receipt bytes; issuer is not authenticated.
- Receipt ID
d21c2850-ec9d-425d-acb6-8aa053fd8780- SHA-256 output hash
sha256:bbe367c4af3caea3837e0f205c920c31f0b048bc6ddaf2e3c8d87eaeb635c94c- Canonical bytes
eyJjYWxsZXIiOnsiYmFzaXMiOiJpcF91YV8zMGQiLCJpZCI6InNoYTI1NjpkY2Y4YzYyN2MyM2Q3NmNmMTQ2MDg4ZTc5ZWY5ZWNkMTczZWJmYTdhZWUxOGQyMDU5NGRmY2RhZmY5MTljN2E4IiwibGFiZWwiOiJ6YW1iby1yZWNlaXB0LWJvdCIsImxhYmVsX3NvdXJjZSI6ImNhbGxlcl9yZXBvcnRlZCIsInJvdGF0ZXNfYXQiOiIyMDI2LTExLTAzVDAwOjAwOjAwLjAwMFoiLCJ0eXBlIjoiYW5vbnltb3VzIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsiYXR0ZXN0cyI6IlphbWJvIGF0dGVzdHMgdGhhdCB0aGlzIHJlY29yZCB3YXMgcmVjZWl2ZWQsIHJlZGFjdGVkLCB0aW1lc3RhbXBlZCwgYW5kIGNoYWluZWQuIiwiZG9lc19ub3RfYXR0ZXN0IjoiWmFtYm8gZGlkIG5vdCBydW4gb3Igb2JzZXJ2ZSB0aGUgcmVwb3J0ZWQgYWN0aW9uLiIsImVudHJ5Ijp7ImNvbXBsZXRlZF9hdCI6IjIwMjYtMTAtMTBUMDA6NTE6MjUuNDU4WiIsImRlbGV0ZWQiOmZhbHNlLCJkdXJhdGlvbl9tcyI6MCwiZW50cnlfaGFzaCI6InNoYTI1Njo1MDI1OGM3N2U0ZmZkNWQ2ODQ3YTFmYjY5M2ViZmE0MDk1YTAwODIxZTg5YmE4ODJiM2Y3N2UxYzFiZTZlMGI2IiwiZW50cnlfaWQiOiIyN2MwMDYxNy02ZGNiLTQ1OGQtOTRhZS0zMGFjYjQyOWZkYWEiLCJleGVjdXRvcl9pZGVudGl0eSI6InphbWJvLXJlY2VpcHQtYm90IiwiZXh0ZXJuYWxfZXhlY3V0b3IiOm51bGwsImpvYl9pZCI6InRlc3QiLCJtZXRhZGF0YSI6e30sInByZXZfaGFzaCI6bnVsbCwicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCIsInJlZGFjdGVkX2lucHV0c19oYXNoIjpudWxsLCJzZXF1ZW5jZSI6MSwic3RhcnRlZF9hdCI6IjIwMjYtMTAtMTBUMDA6NTE6MjUuNDU4WiIsInRvb2xfbmFtZSI6InByb2JlIn0sInByb3ZlbmFuY2VfY2xhc3MiOiJMT0dHRUQgQlkgQUdFTlQiLCJzdGF0dXMiOiJsb2dnZWQiLCJ2ZXJpZnlfdXJsIjoiaHR0cHM6Ly96YW1iby5kZXYvYXBpL2pvdXJuYWwvdGVzdC92ZXJpZnkifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OmRmYjQ0MTJhYTQyOWQzYWM2MzdhMDU2NjhjNDM1YmNjOTBhMjUxMzYzZmNkZDQ5ZjdiODVhZTRhYjU1YjViYzkiLCJkZWNsYXJlZCI6WyJzdGF0ZV93cml0ZSJdLCJzY2hlbWFfdmVyc2lvbiI6InphbWJvLXNpZGUtZWZmZWN0cy8xIn0sInRvb2wiOnsibmFtZSI6ImpvdXJuYWxfbG9nIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4wLjAifX0=- Timestamp
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:dcf8c627c23d76cf146088e79ef9ecd173ebfa7aee18d20594dfcdaff919c7a8- Caller basis
ip_ua_30d- Caller rotates at
2026-11-03T00:00:00.000Z- Caller-reported label
- zambo-receipt-bot (caller_reported, not authenticated team ownership)
- 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
7fdf7f74b3427217f529e58cb3f6befafa24cd710608eb574ccc06539a5a87af- 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-10T00:51:25.545Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:bbe367c4af3caea3837e0f205c920c31f0b048bc6ddaf2e3c8d87eaeb635c94c","receipt_uuid":"d21c2850-ec9d-425d-acb6-8aa053fd8780","schema_version":"zambo-receipt-anchor/1"}
Anchor status "published": Published to all configured relay targets.
Check this hash yourself
Recompute the SHA-256 commitment in your browser. Open the API v2 JSON response to inspect the machine-readable checks. Signature and chain remain NOT CHECKED unless a real signature verifier or chain proof is supplied. There is no combined “verified” verdict. See the Nostr anchor event on a public viewer. The fingerprint is timestamped outside Zambo too.
Embed this receipt
Markdown
[](https://zambo.dev/run/d21c2850-ec9d-425d-acb6-8aa053fd8780)
HTML
<a href="https://zambo.dev/run/d21c2850-ec9d-425d-acb6-8aa053fd8780"><img src="https://zambo.dev/api/receipt/d21c2850-ec9d-425d-acb6-8aa053fd8780/badge.svg" alt="Verifiable Zambo receipt"></a>
Recent receipts
41,409 verifiable receipts minted
Run your own calls. Free, 20 free calls per metered tool each day, no account.