CRYPTO price, 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-03T23:26:30.454Z; 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

fe855492-0407-4419-b3b3-a193240fe3d4

SHA-256 output hash

sha256:83d351b6b38fc589807e74771855c6f7d4343a29aae7c08699eb5f06c19485a4

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6NWNkMzA3MTlmYjJlNzYzN2Y1NTZjMWViMTdlZWI5ZDQyZjg3YWRmZjU3MDE4MmNhMDkxNTBhMmMyNmMzMTI4YyIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0IjoiQlRDIMK3ICQ3Nyw4NDkuMDAgVVNEXG7ilrIgMS41MSUgKDI0aCkgwrcgTWFya2V0IGNhcDogJDE1NjQuMTBCXG5cbkxpdmUgcHJpY2Ugc25hcHNob3QgdmlhIENvaW5HZWNrbyDCtyBmZXRjaGVkIFR1ZSwgMDMgTm92IDIwMjYgMjM6MjY6MjcgR01UIMK3IGNhY2hlIGFnZSAwcyIsInJlZGFjdGVkX3Byb2plY3Rpb24iOnRydWUsInNvdXJjZV9jb21taXRtZW50X2NoZWNrZWQiOnRydWUsInNvdXJjZV9vdXRwdXRfaGFzaCI6InNoYTI1NjpmYjM4NDk1YmMzNTY2ODM2YzQ3NzEwZDg1NjNkZDg2NTUxNjRmN2JlZTE5NmM3YzY3N2I2OGFhMDM3ZTgxM2VkIiwic291cmNlX3JlY2VpcHRfaWQiOiI3ZTUxYjliNi1jZWM0LTQwMjMtOWQ3MC1jODFkNTc4YmFlNWUifSwicmVjZWlwdF9zY2hlbWFfdmVyc2lvbiI6IjAuNCIsInNpZGVfZWZmZWN0cyI6eyJkZWNsYXJhdGlvbl9oYXNoIjoic2hhMjU2OjQ1YWFkMzhmM2FhOTgyYjlhYWZlOTJlY2I0MTZlYmU5ODc5MWVkZGJhZjhhYjZkZjBiZDA4NjA1YjdjMWJmZWUiLCJkZWNsYXJlZCI6WyJub25lIl0sInNjaGVtYV92ZXJzaW9uIjoiemFtYm8tc2lkZS1lZmZlY3RzLzEifSwidG9vbCI6eyJuYW1lIjoibGl2ZV9wcmljZSIsInNjb3BlIjoicHVibGljIiwidmVyc2lvbiI6IjQuMC4wIn19

Timestamp

2026-11-03T23:26:30.454Z

Bound call context

Receipt schema

0.4

Tool name

live_price

Tool version

4.0.0

Permission scope

public

Caller type

session

Caller ID

sha256:5cd30719fb2e7637f556c1eb17eeb9d42f87adff570182ca09150a2c26c3128c

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

1cae982af2e7d2822fc8068122b5127f8872b2dd65abe6225d0e9a11e059c8b7

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-11-03T23:26:30.454Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:83d351b6b38fc589807e74771855c6f7d4343a29aae7c08699eb5f06c19485a4","receipt_uuid":"fe855492-0407-4419-b3b3-a193240fe3d4","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.